I am curently backing up ~400 Windows clients every night. I have 4 (soon to be five) 800 GB arrays to which the volumes are being written. Everything is running quite well with one exception. Two of the four storage servers display the following message five or six times a night:
drss03a: append.c:310 NULL Volume name. This shouldn't happen!!! drss01a: append.c:310 NULL Volume name. This shouldn't happen!!! I would like some advice on troubleshooting these errors. I've been running 2.1.6 since March. Running a trace on the storage daemon does not seem to yield any useful information. This is especially difficult since the console message nor the trace have time stamps. Please advise. Thanks, Brian Kelly
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
_______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users
