[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bacula-devel] Auto upgrade clients.

Kern Sibbald <kern@xxxxxxxxxxx> writes:

> However, it is something that is becoming critical -- I saw one user
> report that he is backing up 10,000 server machines with Bacula -- can
> you imagine the problems of upgrading the File daemons on those
> machines!

Upgrading them is not Bacula's job.  Software maintenance (installing,
configuring, upgrading and patching) is a whole separate kettle of fish,
and there are good tools out there to help you do it.  If those ten
thousand machines aren't under some such scheme, there are much bigger
problems to fix before worrying about upgrading Bacula -- and if they
are, the sysadmins in charge should not allow the backup admin to
upgrade his file daemons using some other mechanism.

Besides, expanding Bacula to handle this quite complex task, and dealing
with all the problems that are sure to arise from this, is going to
steal attention and resources from the important work: maintaining and
improving its real function.

Self documenting code isn't. User application constraints don't. --Ed Prochak

This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
Bacula-devel mailing list

This mailing list archive is a service of Copilotco.