Is there a procedure for shutting bacula down cleanly?  In the last two
months, I've had to shut down the bacula server twice, once for a
scheduled power outage, and once due to a kernel upgrade.

Both times I've ended up with "damaged" tape volumes, no longer able to
append.

"Bad response to Append Data command.  Wanted 3000 OK data, got 3903
Error append data"

Now one additional issue is that when the server is rebooted, the
changer device seems to change.  I've now written a UDEV rule that I
hope will resolve this.  In any case, I'm *pretty* sure that this is an
unrelated problem, but I could be wrong.

In any case, each time I've had to reboot the server, bacula gives me
major grief.  Is there a procedure I can set up to shut bacula down
cleanly so it will be happy when the machine comes back up?


-- 
Steve Garcia
sgarcia AT bak.rr DOT com
Ignorance killed the cat; Curiosity was framed.

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users