On Nov 4, 2011, at 5:41 PM, Dan Langille wrote:

> On Nov 4, 2011, at 10:34 AM, Ben Walton wrote:
> 
>> 
>> Hi All,
>> 
>> I am currently running two distinct bacula setups.  The director of
>> the original setup is a client of the the new, but that is the only
>> link between the two right now.  Both director nodes also run the only
>> storage node for their particular set of clients.
> 
> FYI, I think this message was held up by moderation and has already been 
> answered.

My apologies.  I am entirely wrong.  I had the wrong month in my head…. Sorry.

> 
>> 
>> I'm considering collapsing these two setups such that I have two
>> storage nodes and only one director.
>> 
>> While that's easy enough to do in a slash and burn style, I'd like to
>> maintain the current set of volumes and job information if possible.
>> Is there an easy/sane way to do this?
>> 
>> I think it would look something like:
>> 
>> 0. Stop dir1.
>> 1. Add clients from dir1 to dir2, perform required client config for
>>  each client.
>> 2. Add storage config to dir2 to reference storage daemon on dir1.
>> 3. Use bscan to import existing volumes from dir1 into catalog of
>>  dir2.
>> 
>> Am I nuts?  Has anyone done something similar?
> 
> -- 
> Dan Langille - http://langille.org
> 

-- 
Dan Langille - http://langille.org


------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users