>>>>> On Thu, 11 Oct 2012 19:30:02 -0400, Phil Stracchino said:
> 
> I'm migrating my Bacula director and DB to a new server with much more
> CPU horsepower, leaving the storage daemons where they are.  Right now,
> both directors are running and working.  But.......
> 
> The obvious safe move here is to stop the OLD Director for tonight and
> let the new one carry the job and see how it does.  But I'm curious.
> Does anyone know what will happen (maximum concurrent jobs limits being
> stipulated to be Not An Issue) if two Directors attempt to run the same
> Jobs on the same Clients to the same Storage using the same Catalog at
> the same time?
> 
> (The DB servers are replicating master-master, but to make life safer I
> can point the old Director at the new DB server anyway.)
> 
> 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.

I think it risks corrupting the DB.  The Director expects to have exclusive
write access to the DB, but it doesn't do anything to enforce that.

__Martin

------------------------------------------------------------------------------
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