Re: [Bacula-users] Changing file-daemon hosts while keeping existing jobs, filesets without doing FULL backup

[Martin S. <ma...@li...>]

>>>>> On Tue, 31 Mar 2009 09:55:10 -0700 (PDT), Keith Gunderson said:
> 
> Hi There,
> 
> I've been unsubscribed to bacula-users for a number of months...  no issues is good, right?  But my apologies if this has been asked a lot.  I didn't find the answer by searching.
> 
> We're running bacula 2.2.8 on Debian.  I'd like to replace our main fileserver without having to do a full backup of the jobs immediately after the switch.
> 
> We have about 25 TB of data on some FC disk arrays.  Our filesystems are xfs and we use LVM for some nice flexibilty.  We'll unplug our old server from the FC switch and plug our new server in.  Mount the filesystems and go from there.
> 
> What is my best bet for getting incrementals to work the next evening?
> 
> 1) Alter the client table.  (I.e. add a new client entry, immediately stop bacula, manually change the two client entries in database table so that the new server has the old servers clientID.)
> 2) Alter the jobs table (i.e. alter the clientID entry for every job row so that the new servers clientID is listed where the old server used to be.)
> 3) Buy new tapes dude, you're screwed.  If so, why?

Either 1 or 2 should work.

Alternatively, if the old fileserver (client) is not being used anymore, you
can probably just change the Client Address= line in the Director's config.
This has the advantage of allowing old tapes to be reloaded into the database
with bscan (since the client's name is written into the job).

__Martin