Others have experienced issues relating to antivirus scan engines interfering with successful backups. Perhaps it is interfering with the communications between the daemons (different machines from what I gather.)
The others have tested by disabling AV then running a test job. Erich On Mar 28, 2007, at 8:55 AM, Jason King wrote: > Anyone else in the list have any idea what might be causing the > problem > I'm having? I'm totally at a loss for what to do other than setup a > local director on that server. The backup works fine if the > director is > loaded locally. > > [EMAIL PROTECTED] wrote: >> I already read about that and the "Heartbeat Interval" has already >> been >> setup and changed to 90 seconds. I have Heartbeat setup on both >> the SD and >> the FD of this server. I actually had to setup the Heartbeat to >> handle a >> different problem with the backup. The Heartbeat solved that >> problem but >> then caused/showed this problem. I did attach the trace file. I'm >> not sure >> why you didn't see it. >> >> >>> On Monday 26 March 2007 23:55, Jason King wrote: >>> >>>> Ok, I've got the debug output of the storage daemon now: >>>> >>>> I have the system setup to spool the data to the drive then >>>> write to the >>>> media. Everything looks fine until after the system starts to >>>> despool >>>> everything to tape. Here are the debug messages from despool on: >>>> >>>> >>>> dctn-sd: ../../stored/spool.c:220 Despooling data >>>> dctn-sd: ../../stored/askdir.c:395 >dird: Jmsg >>>> Job=dctn.2007-03-26_15.37.12 type=6 level=1174944136 dctn-sd: >>>> Job write >>>> elapsed time = 00:44:54, Transfer rate = 3.623 M bytes/second >>>> dctn-sd: ../../stored/askdir.c:332 Update cat VolFiles=2 >>>> dctn-sd: ../../stored/askdir.c:351 >dird: dctn-sd: >>>> ../../stored/askdir.c:357 Didn't get vol info vol=GovDeals-01: >>>> ERR=Network error on bnet_recv in req_vol_info. >>>> >>> This indicates that the comm connection from the SD to the Dir >>> was lost. >>> There was no error messages from the SD because they were >>> directed to the >>> Director. The details of the error were lost because the message >>> could >>> not >>> be delivered. You could write all the messages to a log file, but I >>> suspect >>> that it will simply show that the comm line dropped, but who >>> knows it >>> might >>> turn up something interesting. >>> >>> The solution is to fix the comm line problems. Possibly turning on a >>> Heartbeat >>> Interval could help. >>> >>> >>>> dctn-sd: ../../stored/block.c:748 dir_update_volume_info terminate >>>> writing -- ERROR >>>> dctn-sd: ../../stored/block.c:771 Leave terminate_writing_volume -- >>>> ERROR >>>> dctn-sd: ../../stored/spool.c:140 Bad return from despool >>>> WroteVol=0 >>>> dctn-sd: ../compat/compat.cpp:194 Enter wchar_win32_path >>>> >>>> There is more but it's all the finishing up stuff like removing >>>> spool >>>> file and releasing the tape drive. So there you have the debug. >>>> Looks >>>> like the storage daemon isn't able to get the volume information >>>> from >>>> the tape or something. There is another entry higher up in the >>>> log that >>>> shows a similar volume error: >>>> >>>> dctn-sd: ../../stored/label.c:155 Requested Volume "GovDeals-01" on >>>> "DLT-Drive" (Tape0) is not a Bacula labeled Volume, because: >>>> ERR=../../stored/block.c:1006 Read zero bytes at 0:0 on device >>>> "DLT-Drive" (Tape0). >>>> dctn-sd: ../../stored/label.c:179 No volume label - bailing out >>>> >>> This is enough out of context so that I cannot be sure without >>> looking at >>> the >>> whole trace file, which I didn't do (it wasn't attached and I >>> don't have >>> the >>> time anyway). However I can say that this is is normal when >>> labeling a >>> blank >>> tape. >>> >>> >>>> But that isn't true because I labeled the tape just before I ran >>>> the >>>> job. Crap I don't know what the problem with this thing is. Does >>>> this >>>> information help? I have attached the entire debug trace file >>>> for anyone >>>> that can help to view. >>>> >>>> Thanks, >>>> Jason >>>> >>>> >>>> Kern Sibbald wrote: >>>> >>>>> On Monday 26 March 2007 21:54, Brian Debelius wrote: >>>>> >>>>> >>>>>> Kern Sibbald wrote: >>>>>> >>>>>> >>>>>>> On Monday 26 March 2007 21:38, Jason King wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>>> The problem I have is that this particular SD is running on >>>>>>>> Windows >>>>>>>> >>>> so >>>> >>>>>>>> there is no STOUT. Where do I look from there? I can set the -d >>>>>>>> >>>> option >>>> >>>>>>>> within the services options but I just don't know where to >>>>>>>> look for >>>>>>>> >>>> the >>>> >>>>>>>> debug information. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> Well for Windows, you will need to get help from someone else >>>>>>> the >>>>>>> >>> details >>> >>>>> are >>>>> >>>>> >>>>>>> slightly different. >>>>>>> >>>>>>> However, it seems to me that I already mentioned in a >>>>>>> previous email >>>>>>> >>> that >>> >>>>> the >>>>> >>>>> >>>>>>> output is put into bacula.trace (actually, I think it is >>>>>>> >>> bacula-sd.trace). >>> >>>>>>> That file is probably created in the directory the SD >>>>>>> executable is >>>>>>> >>>>>>> >>>>> located. >>>>> >>>>> >>>>>>> Robert has previously given instructions on how to do this >>>>>>> (probably >>>>>>> >>>>>>> >>>>> several >>>>> >>>>> >>>>>>> times) on the email list, and it is also documented in the >>>>>>> manual >>>>>>> >>>> for >>>> >>> the >>> >>>>> FD. >>>>> >>>>> >>>>>>> >>>>>> Mine for what ever reason get created in c:\windows\system32 >>>>>> >>>>>> >>>>> Oh! That's precisely why I said "for Windows you will need to get >>>>> >>>> help >>>> >>> from >>> >>>>> someone else; the details are slightly different". >>>>> >>>>> Thanks. Eventhough Win32 is not my favorite platform, I am >>>>> determined >>>>> >>>> to >>>> >>> learn >>> >>>>> these things :-) >>>>> >>>>> >>>>> ------------------------------------------------------------------ >>>>> ------- >>>>> Take Surveys. Earn Cash. Influence the Future of IT >>>>> Join SourceForge.net's Techsay panel and you'll get the chance to >>>>> >>>> share >>>> >>> your >>> >>>>> opinions on IT & business topics through brief surveys-and earn >>>>> cash >>>>> http://www.techsay.com/default.php? >>>>> page=join.php&p=sourceforge&CID=DEVDEV >>>>> _______________________________________________ >>>>> Bacula-users mailing list >>>>> Bacula-users@lists.sourceforge.net >>>>> https://lists.sourceforge.net/lists/listinfo/bacula-users >>>>> >>>>> >> >> >> >> --------------------------------------------------------------------- >> ---- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to >> share your >> opinions on IT & business topics through brief surveys-and earn cash >> http://www.techsay.com/default.php? >> page=join.php&p=sourceforge&CID=DEVDEV >> _______________________________________________ >> Bacula-users mailing list >> Bacula-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/bacula-users >> > > ---------------------------------------------------------------------- > --- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php? > page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Bacula-users mailing list > Bacula-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bacula-users > ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
