Greetings,
I've noticed an odd behavior in bacula and I am not sure if it is a
documented bug or not.
I have my label format, in my pool definitions, set as Label Format =
"Full-${JobName}" so that each backup that runs gets a unique name such as
Full-superdb.2009-03-11_15.46.47.03.
What I am noticing is that if I have a client configured in bacula but the
director cannot contact a remote client the "stuck" label is used on the
next job that runs. For example I have a client in the director that is
named ldh0500.p1. When we did some IP changes the director was unable to
connect the ldh0500.p1 to run it's scheduled backup. When the next job ran,
for client wdh0500.p1, the volume generated was tagged as
Full-ldh0500.p1.2009-03-09_23.05.00.57. This went on for a few nights before
we were able to correct it and get jobs running and labeling properly again.
We noticed it again when a new client was added to the director but not
properly setup on the remote. Again, when bacula was unable to reach this
new client the next job that ran was labeled with the missed clients job
name.
So, it this a know bug or have I missed something in the configuration
(besides the human error of adding clients in the director before the remote
is setup).
-Adam
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
