Bacula-users

Re: [Bacula-users] Living dangerously with Bacula Directors

2012-10-12 06:41:39
Subject: Re: [Bacula-users] Living dangerously with Bacula Directors
From: Sven Tegethoff <tegethoff AT udobaer DOT de>
To: bacula-users AT lists.sourceforge DOT net
Date: Fri, 12 Oct 2012 12:12:25 +0200
On 12.10.2012 01:30, Phil Stracchino wrote:
> I'm not planning to actually try this, but I'm curious to know whether
> anyone has ever tried a corner case like this one, and if so, what happened.
>

Having two directors use a common set of file and storage-daemons is not 
a problem as long as the directors have different names, use different 
databases, and different sets of media. If both directors are requesting 
a resource, one of them will wait until the resource is free again, and 
they will never attempt to write onto the same medium.

Letting two copies of the same director configuration run on different 
hosts will blow up spectacularly. Using the same database for both will 
corrupt your catalog, because director A will be "unaware" of database 
updates that director B did while it wasn't looking, leading to an 
inconsistent state that you most likely won't be able to recover from :) 
There will also be error messages and crashes because of duplicate keys, 
and both directors no longer knowing what state their in.

Even if you ran a second copy of the director under a different name and 
an independant copy of your database, you will still run into problems. 
Since you effectively have the same media listed in two catalogs, both 
directors will end up overwriting each other's media in non-predictable 
ways.

So in short: You should REALLY avoid this case :) When switching from 
the old director to the new one, shut down the old one, and to be sure 
to reconfigure it in a way it can't accidently be restarted. (Happened 
to me once, not with bacula, but a similar migration scenario - someone 
else who didn't know about a migration going on saw a server going down 
in Nagios and thought he'd do us a favour by restarting it. Big Mistake :) )

Best Regards,

Sven


------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users

<Prev in Thread] Current Thread [Next in Thread>