Re: [Bacula-users] Strange "ERROR" on successful backup
In the message dated: Thu, 29 Mar 2007 11:09:39 BST, The pithy ruminations from Alan Brown on were: => On Wed, 28 Mar 2007, Erich Prinz wrote: => => > 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. => => It would be nice if there was a way of telling AV software not to inspect => files being opened by Bacula Well...there is a Windows API for opening files specifically for backups. Some virus-protection software (Symantec [Norton] Anti-Virus) allows you to exclude all files opened for backup purposes, regardless of the application opening the file. The Bacula documentation states that Bacula backs up Windows systems using the Windows API calls, so virus protection software should be able to easily exclude Bacula. http://www.bacula.org/dev-manual/Windows_Version_Bacula.html Mark => => AB => The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. - 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
Re: [Bacula-users] Strange "ERROR" on successful backup
Hi, On 3/29/2007 1:28 PM, Brian Debelius wrote: > For what its worth, I use Nod32 (www.eset.com), I have not had a problem > with it. Its fast, and has a small footprint. Download a trial, and > see what happens. Right, nice to remind me :-) I also have tried NOD32 and found no more errors with Bacula. Compared to what I previously used as an Anti-Virus software, NOD32 is faster, uses less memory, and is at least as reliable. I'll change what I recommend and use... Arno > brian- > > > Alan Brown wrote: >> On Wed, 28 Mar 2007, Erich Prinz wrote: >> >> >>> 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. >>> >> It would be nice if there was a way of telling AV software not to inspect >> files being opened by Bacula >> >> AB >> >> >> - >> 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 -- IT-Service Lehmann[EMAIL PROTECTED] Arno Lehmann http://www.its-lehmann.de - 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
Re: [Bacula-users] Strange "ERROR" on successful backup
On Thu, 29 Mar 2007, Alan Brown wrote: >> The others have tested by disabling AV then running a test job. > > It would be nice if there was a way of telling AV software not to inspect > files being opened by Bacula Update: F-secure helpdesk inform me that if an executable is exempted from f-secure real-time inspection, then it also exempts files which opened by that executable are also exempted from real-time inspection. I haven't tested this (yet), but if it's true then it's a far better solution than disabling all real-time scanning for the duration of a backup. # Still waiting for answers from Sophos # No idea about other packages # This probably needs to be documented as it's likely to end up as a FAQ - 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
Re: [Bacula-users] Strange "ERROR" on successful backup
For what its worth, I use Nod32 (www.eset.com), I have not had a problem with it. Its fast, and has a small footprint. Download a trial, and see what happens. brian- Alan Brown wrote: > On Wed, 28 Mar 2007, Erich Prinz wrote: > > >> 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. >> > > It would be nice if there was a way of telling AV software not to inspect > files being opened by Bacula > > AB > > > - > 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
Re: [Bacula-users] Strange "ERROR" on successful backup
On Wed, 28 Mar 2007, Erich Prinz wrote: > 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. It would be nice if there was a way of telling AV software not to inspect files being opened by Bacula AB - 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
Re: [Bacula-users] Strange "ERROR" on successful backup
Good call, I have not tried that yet. I'll give that a shot then post back to the list. Jason Erich Prinz wrote: > > 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 detail
Re: [Bacula-users] Strange "ERROR" on successful backup
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 >
Re: [Bacula-users] Strange "ERROR" on successful backup
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 doc
Re: [Bacula-users] Strange "ERROR" on successful backup
[EMAIL PROTECTED] schrieb: > 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. I can see the attached bacula-sd.trace file, so at least it reached the list. Ralf - 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
Re: [Bacula-users] Strange "ERROR" on successful backup
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.techsa
Re: [Bacula-users] Strange "ERROR" on successful backup
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 pan
Re: [Bacula-users] Strange "ERROR" on successful backup
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. 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 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 bacula-sd: ../compat/compat.cpp:194 Enter wchar_win32_path bacula-sd: ../compat/compat.cpp:378 Leave wchar_win32_path=\ bacula-sd: ../compat/compat.cpp:107 Enter convert_unix_to_win32_path bacula-sd: ../compat/compat.cpp:158 path=\\?\bacula-sd.conf bacula-sd: ../compat/compat.cpp:167 Leave cvt_u_to_win32_path path=\\?\bacula-sd.conf bacula-sd: ../compat/compat.cpp:194 Enter wchar_win32_path bacula-sd: ../compat/compat.cpp:208 Leave wchar_win32_path no change bacula-sd: ../compat/compat.cpp:729 GetFileAttributes(\\?\bacula-sd.conf): The system cannot find the file specified. bacula-sd: ../../stored/stored_conf.c:675 Inserting director res: dctn-dir bacula-sd: ../../stored/stored_conf.c:675 Inserting director res: dctn-mon bacula-sd: ../../stored/stored_conf.c:675 Inserting device res: DLT-Drive bacula-sd: ../compat/compat.cpp:194 Enter wchar_win32_path bacula-sd: ../compat/compat.cpp:378 Leave wchar_win32_path=\ dctn-sd: ../../lib/jcr.c:129 read_last_jobs seek to 192 dctn-sd: ../../lib/jcr.c:136 Read num_items=2 dctn-sd: ../../stored/stored.c:476 calling init_dev D:\bacula-tmp dctn-sd: ../compat/compat.cpp:194 Enter wchar_win32_path dctn-sd: ../../lib/bnet_server.c:98 Addresses host[ipv4:0.0.0.0:9103] dctn-sd: ../compat/compat.cpp:378 Leave wchar_win32_path=\ dctn-sd: ../../stored/dev.c:254 init_dev: tape=0 dev_name
Re: [Bacula-users] Strange "ERROR" on successful backup
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
Re: [Bacula-users] Strange "ERROR" on successful backup
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 - 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
Re: [Bacula-users] Strange "ERROR" on successful backup
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. > > jason > > Kern Sibbald wrote: > > On Monday 26 March 2007 21:20, Jason King wrote: > > > >> You mean in the console? > >> > > > > No. > > > > > >> I set my debug level to 100 and nothing > >> different has come through to my console. Where can I get the debug > >> information? > >> > > > > Unless you redirect the output, it will appear in the shell from which you > > started the SD. I.e. stdout. Note, many rpm and distro scripts send stdout > > to /dev/null. The "bacula start" script does not do that. > > > > Also, if you have a non-developer version (i.e. many distros and rpms), then > > when Bacula daemonizes it closes stdout. To avoid that as I mentioned, you > > need to *start* it with at least -d1 on the command line, you can then later > > change the debug level with the setdebug command. > > > > Also, note that I am saying to set the debug level in the SD. Each daemon has > > its own debug level. > > > > I'll leave it to the list to help you get this working if you still have > > problems ... > > > > > >> Kern Sibbald wrote: > >> > >>> On Monday 26 March 2007 19:53, Jason King wrote: > >>> > >>> > I'm sorry, I said that wrong. I tried to say the email I got showed the > director sees an errored backup...but the file daemon puts a successful > backup in its own history logs. I'll try using debugging to see if that > gives me what I need. > > > >>> > >>> > Where can I find the debug output? > > > >>> On the shell window for Unix/Linux machines, and in bacula.trace for > >>> > > Windows > > > >>> machine. > >>> > >>> > >>> > Kern Sibbald wrote: > > > > On Monday 26 March 2007 18:10, Jason King wrote: > > > > > > > >> Also, the email I got showed the director does see a successful > >> backup... > >> > >> > >> > > That seems unlikely because the output you showed below indicates that > > > > the > > > > > > > >>> job > >>> > >>> > > failed. > > > > > > > > > > > >> but like I said, the file daemon says the backup WAS successful > >> when I do a "status client" from the console of the director. > >> > >> > >> > > For the backup to be successful, all three components (DIR, FD, and SD) > > > > > >>> must > >>> > >>> > > report success. In this case, the Dir did not get a success from the > > > > SD. > > > > Why is the mystery you need to resolve. > > > > You might set debug to -d100 in the SD via the setdebug command before > > > > > >>> running > >>> > >>> > > the job. If the SD is built with DEBUG off, you will need to start it > > > > > >>> with > >>> > >>> > > atleast -d1 for the setdebug command to work. A -d100 should show you > > > > > >>> where > >>> > >>> > > things went wrong, if not, up the debug level. > > > > > > > > > >> Jason > >> > >> Kern Sibbald wrote: > >> > >> > >> > >>> Your email title is a bit misleading as this was not successful > >>> > > backup. > > > >>> It looks like the SD might have died ... i.e. probably crashed. > >>> > >>> > >>> > >>> On Monday 26 March 2007 17:10, Jason King wrote: > >>> > >>> > >>> > >>> > According to my bacula database, my backup of one of my servers ended > > > >>> in > >>> > >>> > an error but when I do a status on the servers file daemon, it shows > > > a > > > successful backup, here is the email I received: > > 26-Mar 0
Re: [Bacula-users] Strange "ERROR" on successful backup
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. jason Kern Sibbald wrote: > On Monday 26 March 2007 21:20, Jason King wrote: > >> You mean in the console? >> > > No. > > >> I set my debug level to 100 and nothing >> different has come through to my console. Where can I get the debug >> information? >> > > Unless you redirect the output, it will appear in the shell from which you > started the SD. I.e. stdout. Note, many rpm and distro scripts send stdout > to /dev/null. The "bacula start" script does not do that. > > Also, if you have a non-developer version (i.e. many distros and rpms), then > when Bacula daemonizes it closes stdout. To avoid that as I mentioned, you > need to *start* it with at least -d1 on the command line, you can then later > change the debug level with the setdebug command. > > Also, note that I am saying to set the debug level in the SD. Each daemon > has > its own debug level. > > I'll leave it to the list to help you get this working if you still have > problems ... > > >> Kern Sibbald wrote: >> >>> On Monday 26 March 2007 19:53, Jason King wrote: >>> >>> I'm sorry, I said that wrong. I tried to say the email I got showed the director sees an errored backup...but the file daemon puts a successful backup in its own history logs. I'll try using debugging to see if that gives me what I need. >>> >>> Where can I find the debug output? >>> On the shell window for Unix/Linux machines, and in bacula.trace for >>> > Windows > >>> machine. >>> >>> >>> Kern Sibbald wrote: > On Monday 26 March 2007 18:10, Jason King wrote: > > > >> Also, the email I got showed the director does see a successful >> backup... >> >> >> > That seems unlikely because the output you showed below indicates that > > the > > > >>> job >>> >>> > failed. > > > > > >> but like I said, the file daemon says the backup WAS successful >> when I do a "status client" from the console of the director. >> >> >> > For the backup to be successful, all three components (DIR, FD, and SD) > > >>> must >>> >>> > report success. In this case, the Dir did not get a success from the > > SD. > > Why is the mystery you need to resolve. > > You might set debug to -d100 in the SD via the setdebug command before > > >>> running >>> >>> > the job. If the SD is built with DEBUG off, you will need to start it > > >>> with >>> >>> > atleast -d1 for the setdebug command to work. A -d100 should show you > > >>> where >>> >>> > things went wrong, if not, up the debug level. > > > > >> Jason >> >> Kern Sibbald wrote: >> >> >> >>> Your email title is a bit misleading as this was not successful >>> > backup. > >>> It looks like the SD might have died ... i.e. probably crashed. >>> >>> >>> >>> On Monday 26 March 2007 17:10, Jason King wrote: >>> >>> >>> >>> According to my bacula database, my backup of one of my servers ended >>> in >>> >>> an error but when I do a status on the servers file daemon, it shows > a > successful backup, here is the email I received: 26-Mar 09:01 maint-dir: Start Backup JobId 353, > Job=dctn.2007-03-26_09.01.49 > > > 26-Mar 09:01 dctn-sd: Wrote label to prelabeled Volume "GovDeals-01" > on > >>> device "DLT-Drive" (Tape0) >>> >>> >>> >>> 26-Mar 09:01 dctn-sd: Spooling data ... 26-Mar 09:02 dctn-fd: Generate VSS snapshots. Driver="VSS Win 2003", >>> Drive(s)="D" >>> >>> >>> >>> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "System Writer",
Re: [Bacula-users] Strange "ERROR" on successful backup
On Monday 26 March 2007 21:20, Jason King wrote: > You mean in the console? No. > I set my debug level to 100 and nothing > different has come through to my console. Where can I get the debug > information? Unless you redirect the output, it will appear in the shell from which you started the SD. I.e. stdout. Note, many rpm and distro scripts send stdout to /dev/null. The "bacula start" script does not do that. Also, if you have a non-developer version (i.e. many distros and rpms), then when Bacula daemonizes it closes stdout. To avoid that as I mentioned, you need to *start* it with at least -d1 on the command line, you can then later change the debug level with the setdebug command. Also, note that I am saying to set the debug level in the SD. Each daemon has its own debug level. I'll leave it to the list to help you get this working if you still have problems ... > > Kern Sibbald wrote: > > On Monday 26 March 2007 19:53, Jason King wrote: > > > >> I'm sorry, I said that wrong. I tried to say the email I got showed the > >> director sees an errored backup...but the file daemon puts a successful > >> backup in its own history logs. I'll try using debugging to see if that > >> gives me what I need. > >> > > > > > >> Where can I find the debug output? > >> > > > > On the shell window for Unix/Linux machines, and in bacula.trace for Windows > > machine. > > > > > >> Kern Sibbald wrote: > >> > >>> On Monday 26 March 2007 18:10, Jason King wrote: > >>> > >>> > Also, the email I got showed the director does see a successful > backup... > > > >>> That seems unlikely because the output you showed below indicates that the > >>> > > job > > > >>> failed. > >>> > >>> > >>> > >>> > but like I said, the file daemon says the backup WAS successful > when I do a "status client" from the console of the director. > > > >>> For the backup to be successful, all three components (DIR, FD, and SD) > >>> > > must > > > >>> report success. In this case, the Dir did not get a success from the SD. > >>> > >>> Why is the mystery you need to resolve. > >>> > >>> You might set debug to -d100 in the SD via the setdebug command before > >>> > > running > > > >>> the job. If the SD is built with DEBUG off, you will need to start it > >>> > > with > > > >>> atleast -d1 for the setdebug command to work. A -d100 should show you > >>> > > where > > > >>> things went wrong, if not, up the debug level. > >>> > >>> > >>> > Jason > > Kern Sibbald wrote: > > > > Your email title is a bit misleading as this was not successful backup. > > > > It looks like the SD might have died ... i.e. probably crashed. > > > > > > > > On Monday 26 March 2007 17:10, Jason King wrote: > > > > > > > >> According to my bacula database, my backup of one of my servers ended > >> > > in > > > >> an error but when I do a status on the servers file daemon, it shows a > >> successful backup, here is the email I received: > >> > >> 26-Mar 09:01 maint-dir: Start Backup JobId 353, > >> > >> > >>> Job=dctn.2007-03-26_09.01.49 > >>> > >>> > >> 26-Mar 09:01 dctn-sd: Wrote label to prelabeled Volume "GovDeals-01" on > >> > >> > >> > > device "DLT-Drive" (Tape0) > > > > > > > >> 26-Mar 09:01 dctn-sd: Spooling data ... > >> 26-Mar 09:02 dctn-fd: Generate VSS snapshots. Driver="VSS Win 2003", > >> > >> > >> > > Drive(s)="D" > > > > > > > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "System Writer", > >> > >> > >>> State: > >>> > >>> > >> > >> > >> > > 0x1 (VSS_WS_STABLE) > > > > > > > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "MSDEWriter", State: > >> > >> > >>> 0x1 > >>> > >>> > >> > >> > >> > > (VSS_WS_STABLE) > > > > > > > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "WINS Jet Writer", > >> > >> > >>> State: > >>> > >>> > >> > >> > >> > > 0x1 (VSS_WS_STABLE) > > > > > > > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "COM+ REGDB Writer", > >> > >> > >> > > State: 0x1 (VSS_WS_STABLE) > > > > > > > >> 26-Mar 09:39 dctn-fd: VSS Writ
Re: [Bacula-users] Strange "ERROR" on successful backup
You mean in the console? I set my debug level to 100 and nothing different has come through to my console. Where can I get the debug information? Kern Sibbald wrote: > On Monday 26 March 2007 19:53, Jason King wrote: > >> I'm sorry, I said that wrong. I tried to say the email I got showed the >> director sees an errored backup...but the file daemon puts a successful >> backup in its own history logs. I'll try using debugging to see if that >> gives me what I need. >> > > >> Where can I find the debug output? >> > > On the shell window for Unix/Linux machines, and in bacula.trace for Windows > machine. > > >> Kern Sibbald wrote: >> >>> On Monday 26 March 2007 18:10, Jason King wrote: >>> >>> Also, the email I got showed the director does see a successful backup... >>> That seems unlikely because the output you showed below indicates that the >>> > job > >>> failed. >>> >>> >>> >>> but like I said, the file daemon says the backup WAS successful when I do a "status client" from the console of the director. >>> For the backup to be successful, all three components (DIR, FD, and SD) >>> > must > >>> report success. In this case, the Dir did not get a success from the SD. >>> >>> Why is the mystery you need to resolve. >>> >>> You might set debug to -d100 in the SD via the setdebug command before >>> > running > >>> the job. If the SD is built with DEBUG off, you will need to start it >>> > with > >>> atleast -d1 for the setdebug command to work. A -d100 should show you >>> > where > >>> things went wrong, if not, up the debug level. >>> >>> >>> Jason Kern Sibbald wrote: > Your email title is a bit misleading as this was not successful backup. > > It looks like the SD might have died ... i.e. probably crashed. > > > > On Monday 26 March 2007 17:10, Jason King wrote: > > > >> According to my bacula database, my backup of one of my servers ended >> > in > >> an error but when I do a status on the servers file daemon, it shows a >> successful backup, here is the email I received: >> >> 26-Mar 09:01 maint-dir: Start Backup JobId 353, >> >> >>> Job=dctn.2007-03-26_09.01.49 >>> >>> >> 26-Mar 09:01 dctn-sd: Wrote label to prelabeled Volume "GovDeals-01" on >> >> >> > device "DLT-Drive" (Tape0) > > > >> 26-Mar 09:01 dctn-sd: Spooling data ... >> 26-Mar 09:02 dctn-fd: Generate VSS snapshots. Driver="VSS Win 2003", >> >> >> > Drive(s)="D" > > > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "System Writer", >> >> >>> State: >>> >>> >> >> >> > 0x1 (VSS_WS_STABLE) > > > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "MSDEWriter", State: >> >> >>> 0x1 >>> >>> >> >> >> > (VSS_WS_STABLE) > > > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "WINS Jet Writer", >> >> >>> State: >>> >>> >> >> >> > 0x1 (VSS_WS_STABLE) > > > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "COM+ REGDB Writer", >> >> >> > State: 0x1 (VSS_WS_STABLE) > > > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Dhcp Jet Writer", >> >> >>> State: >>> >>> >> >> >> > 0x1 (VSS_WS_STABLE) > > > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Certificate >> >> >>> Authority", >>> >>> >> >> >> > State: 0x1 (VSS_WS_STABLE) > > > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "DFS Replication >> >> >>> service >>> >>> >> >> >> > writer", State: 0x1 (VSS_WS_STABLE) > > > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "FRS Writer", State: >> >> >>> 0x1 >>> >>> >> >> >> > (VSS_WS_STABLE) > > > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Registry Wr
Re: [Bacula-users] Strange "ERROR" on successful backup
On Monday 26 March 2007 19:53, Jason King wrote: > I'm sorry, I said that wrong. I tried to say the email I got showed the > director sees an errored backup...but the file daemon puts a successful > backup in its own history logs. I'll try using debugging to see if that > gives me what I need. > Where can I find the debug output? On the shell window for Unix/Linux machines, and in bacula.trace for Windows machine. > > Kern Sibbald wrote: > > On Monday 26 March 2007 18:10, Jason King wrote: > > > >> Also, the email I got showed the director does see a successful > >> backup... > >> > > > > That seems unlikely because the output you showed below indicates that the job > > failed. > > > > > > > >> but like I said, the file daemon says the backup WAS successful > >> when I do a "status client" from the console of the director. > >> > > > > For the backup to be successful, all three components (DIR, FD, and SD) must > > report success. In this case, the Dir did not get a success from the SD. > > > > Why is the mystery you need to resolve. > > > > You might set debug to -d100 in the SD via the setdebug command before running > > the job. If the SD is built with DEBUG off, you will need to start it with > > atleast -d1 for the setdebug command to work. A -d100 should show you where > > things went wrong, if not, up the debug level. > > > > > >> Jason > >> > >> Kern Sibbald wrote: > >> > >>> Your email title is a bit misleading as this was not successful backup. > >>> > >>> It looks like the SD might have died ... i.e. probably crashed. > >>> > >>> > >>> > >>> On Monday 26 March 2007 17:10, Jason King wrote: > >>> > >>> > According to my bacula database, my backup of one of my servers ended in > an error but when I do a status on the servers file daemon, it shows a > successful backup, here is the email I received: > > 26-Mar 09:01 maint-dir: Start Backup JobId 353, > > > Job=dctn.2007-03-26_09.01.49 > > > 26-Mar 09:01 dctn-sd: Wrote label to prelabeled Volume "GovDeals-01" on > > > >>> device "DLT-Drive" (Tape0) > >>> > >>> > 26-Mar 09:01 dctn-sd: Spooling data ... > 26-Mar 09:02 dctn-fd: Generate VSS snapshots. Driver="VSS Win 2003", > > > >>> Drive(s)="D" > >>> > >>> > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "System Writer", > > > State: > > > > > >>> 0x1 (VSS_WS_STABLE) > >>> > >>> > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "MSDEWriter", State: > > > 0x1 > > > > > >>> (VSS_WS_STABLE) > >>> > >>> > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "WINS Jet Writer", > > > State: > > > > > >>> 0x1 (VSS_WS_STABLE) > >>> > >>> > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "COM+ REGDB Writer", > > > >>> State: 0x1 (VSS_WS_STABLE) > >>> > >>> > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Dhcp Jet Writer", > > > State: > > > > > >>> 0x1 (VSS_WS_STABLE) > >>> > >>> > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Certificate > > > Authority", > > > > > >>> State: 0x1 (VSS_WS_STABLE) > >>> > >>> > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "DFS Replication > > > service > > > > > >>> writer", State: 0x1 (VSS_WS_STABLE) > >>> > >>> > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "FRS Writer", State: > > > 0x1 > > > > > >>> (VSS_WS_STABLE) > >>> > >>> > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Registry Writer", > > > State: > > > > > >>> 0x1 (VSS_WS_STABLE) > >>> > >>> > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Event Log Writer", > > > >>> State: 0x1 (VSS_WS_STABLE) > >>> > >>> > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "NTDS", State: 0x1 > > > >>> (VSS_WS_STABLE) > >>> > >>> > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "WMI Writer", State: > > > 0x1 > > > > > >>> (VSS_WS_STABLE) > >>> > >>> > 26-Mar 09:39 maint-dir: dctn.2007-03-26_09.01.49 Error: Bacula 2.0.1 > > > >>> (12Jan07): 26-Mar-2007 09:39:59 > >>> > >>> > JobId: 353 > Job:dctn.2007-03-26_09.01.49 > Backup Level: Full > Client: "dctn-fd" 2.0.3 (06Mar07) > > > >>> Linux,Cross-compile,Win32 > >>>
Re: [Bacula-users] Strange "ERROR" on successful backup
No, I didn't know there was such a thing. Jaime Ventura wrote: > Hello Jason, > Are you using the MAIL ON SUCCESS feature? > >Jaime > > Jason King wrote: >> I'm sorry, I said that wrong. I tried to say the email I got showed >> the director sees an errored backup...but the file daemon puts a >> successful backup in its own history logs. I'll try using debugging >> to see if that gives me what I need. Where can I find the debug output? >> >> Kern Sibbald wrote: >> >>> On Monday 26 March 2007 18:10, Jason King wrote: >>> Also, the email I got showed the director does see a successful backup... >>> That seems unlikely because the output you showed below indicates >>> that the job failed. >>> >>> >>> but like I said, the file daemon says the backup WAS successful when I do a "status client" from the console of the director. >>> For the backup to be successful, all three components (DIR, FD, and >>> SD) must report success. In this case, the Dir did not get a >>> success from the SD. >>> Why is the mystery you need to resolve. >>> You might set debug to -d100 in the SD via the setdebug command >>> before running the job. If the SD is built with DEBUG off, you will >>> need to start it with atleast -d1 for the setdebug command to work. >>> A -d100 should show you where things went wrong, if not, up the >>> debug level. >>> >>> Jason Kern Sibbald wrote: > Your email title is a bit misleading as this was not successful > backup. > > It looks like the SD might have died ... i.e. probably crashed. > > > > On Monday 26 March 2007 17:10, Jason King wrote: > >> According to my bacula database, my backup of one of my servers >> ended in an error but when I do a status on the servers file >> daemon, it shows a successful backup, here is the email I received: >> >> 26-Mar 09:01 maint-dir: Start Backup JobId 353, >>> Job=dctn.2007-03-26_09.01.49 >>> >> 26-Mar 09:01 dctn-sd: Wrote label to prelabeled Volume >> "GovDeals-01" on > device "DLT-Drive" (Tape0) > >> 26-Mar 09:01 dctn-sd: Spooling data ... >> 26-Mar 09:02 dctn-fd: Generate VSS snapshots. Driver="VSS Win >> 2003", > Drive(s)="D" > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "System >> Writer", >>> State: >> > 0x1 (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "MSDEWriter", >> State: >>> 0x1 >> > (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "WINS Jet >> Writer", >>> State: >> > 0x1 (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "COM+ REGDB >> Writer", > State: 0x1 (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Dhcp Jet >> Writer", >>> State: >> > 0x1 (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Certificate >> >>> Authority", >> > State: 0x1 (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "DFS >> Replication >>> service >> > writer", State: 0x1 (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "FRS Writer", >> State: >>> 0x1 >> > (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Registry >> Writer", >>> State: >> > 0x1 (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Event Log >> Writer", > State: 0x1 (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "NTDS", State: >> 0x1 > (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "WMI Writer", >> State: >>> 0x1 >> > (VSS_WS_STABLE) > >> 26-Mar 09:39 maint-dir: dctn.2007-03-26_09.01.49 Error: Bacula >> 2.0.1 > (12Jan07): 26-Mar-2007 09:39:59 > >> JobId: 353 >> Job:dctn.2007-03-26_09.01.49 >> Bac
Re: [Bacula-users] Strange "ERROR" on successful backup
Hello Jason, Are you using the MAIL ON SUCCESS feature? Jaime Jason King wrote: > I'm sorry, I said that wrong. I tried to say the email I got showed the > director sees an errored backup...but the file daemon puts a successful > backup in its own history logs. I'll try using debugging to see if that > gives me what I need. Where can I find the debug output? > > Kern Sibbald wrote: > >> On Monday 26 March 2007 18:10, Jason King wrote: >> >> >>> Also, the email I got showed the director does see a successful >>> backup... >>> >>> >> That seems unlikely because the output you showed below indicates that the >> job >> failed. >> >> >> >> >>> but like I said, the file daemon says the backup WAS successful >>> when I do a "status client" from the console of the director. >>> >>> >> For the backup to be successful, all three components (DIR, FD, and SD) must >> report success. In this case, the Dir did not get a success from the SD. >> >> Why is the mystery you need to resolve. >> >> You might set debug to -d100 in the SD via the setdebug command before >> running >> the job. If the SD is built with DEBUG off, you will need to start it with >> atleast -d1 for the setdebug command to work. A -d100 should show you where >> things went wrong, if not, up the debug level. >> >> >> >>> Jason >>> >>> Kern Sibbald wrote: >>> >>> Your email title is a bit misleading as this was not successful backup. It looks like the SD might have died ... i.e. probably crashed. On Monday 26 March 2007 17:10, Jason King wrote: > According to my bacula database, my backup of one of my servers ended in > an error but when I do a status on the servers file daemon, it shows a > successful backup, here is the email I received: > > 26-Mar 09:01 maint-dir: Start Backup JobId 353, > > >> Job=dctn.2007-03-26_09.01.49 >> >> > 26-Mar 09:01 dctn-sd: Wrote label to prelabeled Volume "GovDeals-01" on > > > device "DLT-Drive" (Tape0) > 26-Mar 09:01 dctn-sd: Spooling data ... > 26-Mar 09:02 dctn-fd: Generate VSS snapshots. Driver="VSS Win 2003", > > > Drive(s)="D" > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "System Writer", > > >> State: >> >> > > > 0x1 (VSS_WS_STABLE) > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "MSDEWriter", State: > > >> 0x1 >> >> > > > (VSS_WS_STABLE) > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "WINS Jet Writer", > > >> State: >> >> > > > 0x1 (VSS_WS_STABLE) > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "COM+ REGDB Writer", > > > State: 0x1 (VSS_WS_STABLE) > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Dhcp Jet Writer", > > >> State: >> >> > > > 0x1 (VSS_WS_STABLE) > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Certificate > > >> Authority", >> >> > > > State: 0x1 (VSS_WS_STABLE) > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "DFS Replication > > >> service >> >> > > > writer", State: 0x1 (VSS_WS_STABLE) > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "FRS Writer", State: > > >> 0x1 >> >> > > > (VSS_WS_STABLE) > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Registry Writer", > > >> State: >> >> > > > 0x1 (VSS_WS_STABLE) > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Event Log Writer", > > > State: 0x1 (VSS_WS_STABLE) > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "NTDS", State: 0x1 > > > (VSS_WS_STABLE) > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "WMI Writer", State: > > >> 0x
Re: [Bacula-users] Strange "ERROR" on successful backup
I'm sorry, I said that wrong. I tried to say the email I got showed the director sees an errored backup...but the file daemon puts a successful backup in its own history logs. I'll try using debugging to see if that gives me what I need. Where can I find the debug output? Kern Sibbald wrote: > On Monday 26 March 2007 18:10, Jason King wrote: > >> Also, the email I got showed the director does see a successful >> backup... >> > > That seems unlikely because the output you showed below indicates that the > job > failed. > > > >> but like I said, the file daemon says the backup WAS successful >> when I do a "status client" from the console of the director. >> > > For the backup to be successful, all three components (DIR, FD, and SD) must > report success. In this case, the Dir did not get a success from the SD. > > Why is the mystery you need to resolve. > > You might set debug to -d100 in the SD via the setdebug command before > running > the job. If the SD is built with DEBUG off, you will need to start it with > atleast -d1 for the setdebug command to work. A -d100 should show you where > things went wrong, if not, up the debug level. > > >> Jason >> >> Kern Sibbald wrote: >> >>> Your email title is a bit misleading as this was not successful backup. >>> >>> It looks like the SD might have died ... i.e. probably crashed. >>> >>> >>> >>> On Monday 26 March 2007 17:10, Jason King wrote: >>> >>> According to my bacula database, my backup of one of my servers ended in an error but when I do a status on the servers file daemon, it shows a successful backup, here is the email I received: 26-Mar 09:01 maint-dir: Start Backup JobId 353, > Job=dctn.2007-03-26_09.01.49 > 26-Mar 09:01 dctn-sd: Wrote label to prelabeled Volume "GovDeals-01" on >>> device "DLT-Drive" (Tape0) >>> >>> 26-Mar 09:01 dctn-sd: Spooling data ... 26-Mar 09:02 dctn-fd: Generate VSS snapshots. Driver="VSS Win 2003", >>> Drive(s)="D" >>> >>> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "System Writer", > State: > >>> 0x1 (VSS_WS_STABLE) >>> >>> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "MSDEWriter", State: > 0x1 > >>> (VSS_WS_STABLE) >>> >>> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "WINS Jet Writer", > State: > >>> 0x1 (VSS_WS_STABLE) >>> >>> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "COM+ REGDB Writer", >>> State: 0x1 (VSS_WS_STABLE) >>> >>> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Dhcp Jet Writer", > State: > >>> 0x1 (VSS_WS_STABLE) >>> >>> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Certificate > Authority", > >>> State: 0x1 (VSS_WS_STABLE) >>> >>> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "DFS Replication > service > >>> writer", State: 0x1 (VSS_WS_STABLE) >>> >>> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "FRS Writer", State: > 0x1 > >>> (VSS_WS_STABLE) >>> >>> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Registry Writer", > State: > >>> 0x1 (VSS_WS_STABLE) >>> >>> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Event Log Writer", >>> State: 0x1 (VSS_WS_STABLE) >>> >>> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "NTDS", State: 0x1 >>> (VSS_WS_STABLE) >>> >>> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "WMI Writer", State: > 0x1 > >>> (VSS_WS_STABLE) >>> >>> 26-Mar 09:39 maint-dir: dctn.2007-03-26_09.01.49 Error: Bacula 2.0.1 >>> (12Jan07): 26-Mar-2007 09:39:59 >>> >>> JobId: 353 Job:dctn.2007-03-26_09.01.49 Backup Level: Full Client: "dctn-fd" 2.0.3 (06Mar07) >>> Linux,Cross-compile,Win32 >>> >>> FileSet:"DCTNSet" 2007-03-20 23:32:54 Pool: "GovDeals" (From Job resource) Storage:"DLT-Tape" (From Job resource) Scheduled time: 26-Mar-2007 09:01:47 Start time: 26-Mar-2007 09:01:57 End time: 26-Mar-2007 09:39:59 Elapsed time: 38 mins 2 secs Priority: 10 FD Files Written: 20,621 SD Files Written:
Re: [Bacula-users] Strange "ERROR" on successful backup
On Monday 26 March 2007 18:10, Jason King wrote: > Also, the email I got showed the director does see a successful > backup... That seems unlikely because the output you showed below indicates that the job failed. > but like I said, the file daemon says the backup WAS successful > when I do a "status client" from the console of the director. For the backup to be successful, all three components (DIR, FD, and SD) must report success. In this case, the Dir did not get a success from the SD. Why is the mystery you need to resolve. You might set debug to -d100 in the SD via the setdebug command before running the job. If the SD is built with DEBUG off, you will need to start it with atleast -d1 for the setdebug command to work. A -d100 should show you where things went wrong, if not, up the debug level. > > Jason > > Kern Sibbald wrote: > > Your email title is a bit misleading as this was not successful backup. > > > > It looks like the SD might have died ... i.e. probably crashed. > > > > > > > > On Monday 26 March 2007 17:10, Jason King wrote: > > > >> According to my bacula database, my backup of one of my servers ended in > >> an error but when I do a status on the servers file daemon, it shows a > >> successful backup, here is the email I received: > >> > >> 26-Mar 09:01 maint-dir: Start Backup JobId 353, Job=dctn.2007-03-26_09.01.49 > >> 26-Mar 09:01 dctn-sd: Wrote label to prelabeled Volume "GovDeals-01" on > >> > > device "DLT-Drive" (Tape0) > > > >> 26-Mar 09:01 dctn-sd: Spooling data ... > >> 26-Mar 09:02 dctn-fd: Generate VSS snapshots. Driver="VSS Win 2003", > >> > > Drive(s)="D" > > > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "System Writer", State: > >> > > 0x1 (VSS_WS_STABLE) > > > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "MSDEWriter", State: 0x1 > >> > > (VSS_WS_STABLE) > > > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "WINS Jet Writer", State: > >> > > 0x1 (VSS_WS_STABLE) > > > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "COM+ REGDB Writer", > >> > > State: 0x1 (VSS_WS_STABLE) > > > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Dhcp Jet Writer", State: > >> > > 0x1 (VSS_WS_STABLE) > > > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Certificate Authority", > >> > > State: 0x1 (VSS_WS_STABLE) > > > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "DFS Replication service > >> > > writer", State: 0x1 (VSS_WS_STABLE) > > > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "FRS Writer", State: 0x1 > >> > > (VSS_WS_STABLE) > > > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Registry Writer", State: > >> > > 0x1 (VSS_WS_STABLE) > > > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Event Log Writer", > >> > > State: 0x1 (VSS_WS_STABLE) > > > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "NTDS", State: 0x1 > >> > > (VSS_WS_STABLE) > > > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "WMI Writer", State: 0x1 > >> > > (VSS_WS_STABLE) > > > >> 26-Mar 09:39 maint-dir: dctn.2007-03-26_09.01.49 Error: Bacula 2.0.1 > >> > > (12Jan07): 26-Mar-2007 09:39:59 > > > >> JobId: 353 > >> Job:dctn.2007-03-26_09.01.49 > >> Backup Level: Full > >> Client: "dctn-fd" 2.0.3 (06Mar07) > >> > > Linux,Cross-compile,Win32 > > > >> FileSet:"DCTNSet" 2007-03-20 23:32:54 > >> Pool: "GovDeals" (From Job resource) > >> Storage:"DLT-Tape" (From Job resource) > >> Scheduled time: 26-Mar-2007 09:01:47 > >> Start time: 26-Mar-2007 09:01:57 > >> End time: 26-Mar-2007 09:39:59 > >> Elapsed time: 38 mins 2 secs > >> Priority: 10 > >> FD Files Written: 20,621 > >> SD Files Written: 0 > >> FD Bytes Written: 9,756,487,879 (9.756 GB) > >> SD Bytes Written: 0 (0 B) > >> Rate: 4275.4 KB/s > >> Software Compression: None > >> VSS:yes > >> Encryption: no > >> Volume name(s): > >> Volume Session Id: 2 > >> Volume Session Time:1174687096 > >> Last Volume Bytes: 64,512 (64.51 KB) > >> Non-fatal FD errors:0 > >> SD Errors: 0 > >> FD termination status: OK > >> SD termination status: Error > >> Termination:*** Backup Error *** > >> > >> The error messages are not descriptive. At the top, the message just > >> says "error". Then at the bottom it says "SD termination status: Error. > >> I don't know what any of that means. What does this all mean? This > >> backup job uses spooling BTW. > >> > >> Jason > >> > >> - > >> Take Surveys. Earn Cash. Infl
Re: [Bacula-users] Strange "ERROR" on successful backup
Also, the email I got showed the director does see a successful backup...but like I said, the file daemon says the backup WAS successful when I do a "status client" from the console of the director. Jason Kern Sibbald wrote: > Your email title is a bit misleading as this was not successful backup. > > It looks like the SD might have died ... i.e. probably crashed. > > > > On Monday 26 March 2007 17:10, Jason King wrote: > >> According to my bacula database, my backup of one of my servers ended in >> an error but when I do a status on the servers file daemon, it shows a >> successful backup, here is the email I received: >> >> 26-Mar 09:01 maint-dir: Start Backup JobId 353, Job=dctn.2007-03-26_09.01.49 >> 26-Mar 09:01 dctn-sd: Wrote label to prelabeled Volume "GovDeals-01" on >> > device "DLT-Drive" (Tape0) > >> 26-Mar 09:01 dctn-sd: Spooling data ... >> 26-Mar 09:02 dctn-fd: Generate VSS snapshots. Driver="VSS Win 2003", >> > Drive(s)="D" > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "System Writer", State: >> > 0x1 (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "MSDEWriter", State: 0x1 >> > (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "WINS Jet Writer", State: >> > 0x1 (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "COM+ REGDB Writer", >> > State: 0x1 (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Dhcp Jet Writer", State: >> > 0x1 (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Certificate Authority", >> > State: 0x1 (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "DFS Replication service >> > writer", State: 0x1 (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "FRS Writer", State: 0x1 >> > (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Registry Writer", State: >> > 0x1 (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Event Log Writer", >> > State: 0x1 (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "NTDS", State: 0x1 >> > (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "WMI Writer", State: 0x1 >> > (VSS_WS_STABLE) > >> 26-Mar 09:39 maint-dir: dctn.2007-03-26_09.01.49 Error: Bacula 2.0.1 >> > (12Jan07): 26-Mar-2007 09:39:59 > >> JobId: 353 >> Job:dctn.2007-03-26_09.01.49 >> Backup Level: Full >> Client: "dctn-fd" 2.0.3 (06Mar07) >> > Linux,Cross-compile,Win32 > >> FileSet:"DCTNSet" 2007-03-20 23:32:54 >> Pool: "GovDeals" (From Job resource) >> Storage:"DLT-Tape" (From Job resource) >> Scheduled time: 26-Mar-2007 09:01:47 >> Start time: 26-Mar-2007 09:01:57 >> End time: 26-Mar-2007 09:39:59 >> Elapsed time: 38 mins 2 secs >> Priority: 10 >> FD Files Written: 20,621 >> SD Files Written: 0 >> FD Bytes Written: 9,756,487,879 (9.756 GB) >> SD Bytes Written: 0 (0 B) >> Rate: 4275.4 KB/s >> Software Compression: None >> VSS:yes >> Encryption: no >> Volume name(s): >> Volume Session Id: 2 >> Volume Session Time:1174687096 >> Last Volume Bytes: 64,512 (64.51 KB) >> Non-fatal FD errors:0 >> SD Errors: 0 >> FD termination status: OK >> SD termination status: Error >> Termination:*** Backup Error *** >> >> The error messages are not descriptive. At the top, the message just >> says "error". Then at the bottom it says "SD termination status: Error. >> I don't know what any of that means. What does this all mean? This >> backup job uses spooling BTW. >> >> Jason >> >> - >> 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
Re: [Bacula-users] Strange "ERROR" on successful backup
No, it did not die or crash. The SD is still running. I can check it with the director and it's still running just fine. Jason Kern Sibbald wrote: > Your email title is a bit misleading as this was not successful backup. > > It looks like the SD might have died ... i.e. probably crashed. > > > > On Monday 26 March 2007 17:10, Jason King wrote: > >> According to my bacula database, my backup of one of my servers ended in >> an error but when I do a status on the servers file daemon, it shows a >> successful backup, here is the email I received: >> >> 26-Mar 09:01 maint-dir: Start Backup JobId 353, Job=dctn.2007-03-26_09.01.49 >> 26-Mar 09:01 dctn-sd: Wrote label to prelabeled Volume "GovDeals-01" on >> > device "DLT-Drive" (Tape0) > >> 26-Mar 09:01 dctn-sd: Spooling data ... >> 26-Mar 09:02 dctn-fd: Generate VSS snapshots. Driver="VSS Win 2003", >> > Drive(s)="D" > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "System Writer", State: >> > 0x1 (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "MSDEWriter", State: 0x1 >> > (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "WINS Jet Writer", State: >> > 0x1 (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "COM+ REGDB Writer", >> > State: 0x1 (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Dhcp Jet Writer", State: >> > 0x1 (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Certificate Authority", >> > State: 0x1 (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "DFS Replication service >> > writer", State: 0x1 (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "FRS Writer", State: 0x1 >> > (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Registry Writer", State: >> > 0x1 (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Event Log Writer", >> > State: 0x1 (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "NTDS", State: 0x1 >> > (VSS_WS_STABLE) > >> 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "WMI Writer", State: 0x1 >> > (VSS_WS_STABLE) > >> 26-Mar 09:39 maint-dir: dctn.2007-03-26_09.01.49 Error: Bacula 2.0.1 >> > (12Jan07): 26-Mar-2007 09:39:59 > >> JobId: 353 >> Job:dctn.2007-03-26_09.01.49 >> Backup Level: Full >> Client: "dctn-fd" 2.0.3 (06Mar07) >> > Linux,Cross-compile,Win32 > >> FileSet:"DCTNSet" 2007-03-20 23:32:54 >> Pool: "GovDeals" (From Job resource) >> Storage:"DLT-Tape" (From Job resource) >> Scheduled time: 26-Mar-2007 09:01:47 >> Start time: 26-Mar-2007 09:01:57 >> End time: 26-Mar-2007 09:39:59 >> Elapsed time: 38 mins 2 secs >> Priority: 10 >> FD Files Written: 20,621 >> SD Files Written: 0 >> FD Bytes Written: 9,756,487,879 (9.756 GB) >> SD Bytes Written: 0 (0 B) >> Rate: 4275.4 KB/s >> Software Compression: None >> VSS:yes >> Encryption: no >> Volume name(s): >> Volume Session Id: 2 >> Volume Session Time:1174687096 >> Last Volume Bytes: 64,512 (64.51 KB) >> Non-fatal FD errors:0 >> SD Errors: 0 >> FD termination status: OK >> SD termination status: Error >> Termination:*** Backup Error *** >> >> The error messages are not descriptive. At the top, the message just >> says "error". Then at the bottom it says "SD termination status: Error. >> I don't know what any of that means. What does this all mean? This >> backup job uses spooling BTW. >> >> Jason >> >> - >> 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
Re: [Bacula-users] Strange "ERROR" on successful backup
Your email title is a bit misleading as this was not successful backup. It looks like the SD might have died ... i.e. probably crashed. On Monday 26 March 2007 17:10, Jason King wrote: > According to my bacula database, my backup of one of my servers ended in > an error but when I do a status on the servers file daemon, it shows a > successful backup, here is the email I received: > > 26-Mar 09:01 maint-dir: Start Backup JobId 353, Job=dctn.2007-03-26_09.01.49 > 26-Mar 09:01 dctn-sd: Wrote label to prelabeled Volume "GovDeals-01" on device "DLT-Drive" (Tape0) > 26-Mar 09:01 dctn-sd: Spooling data ... > 26-Mar 09:02 dctn-fd: Generate VSS snapshots. Driver="VSS Win 2003", Drive(s)="D" > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "System Writer", State: 0x1 (VSS_WS_STABLE) > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "MSDEWriter", State: 0x1 (VSS_WS_STABLE) > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "WINS Jet Writer", State: 0x1 (VSS_WS_STABLE) > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "COM+ REGDB Writer", State: 0x1 (VSS_WS_STABLE) > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Dhcp Jet Writer", State: 0x1 (VSS_WS_STABLE) > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Certificate Authority", State: 0x1 (VSS_WS_STABLE) > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "DFS Replication service writer", State: 0x1 (VSS_WS_STABLE) > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "FRS Writer", State: 0x1 (VSS_WS_STABLE) > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Registry Writer", State: 0x1 (VSS_WS_STABLE) > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "Event Log Writer", State: 0x1 (VSS_WS_STABLE) > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "NTDS", State: 0x1 (VSS_WS_STABLE) > 26-Mar 09:39 dctn-fd: VSS Writer (BackupComplete): "WMI Writer", State: 0x1 (VSS_WS_STABLE) > 26-Mar 09:39 maint-dir: dctn.2007-03-26_09.01.49 Error: Bacula 2.0.1 (12Jan07): 26-Mar-2007 09:39:59 > JobId: 353 > Job:dctn.2007-03-26_09.01.49 > Backup Level: Full > Client: "dctn-fd" 2.0.3 (06Mar07) Linux,Cross-compile,Win32 > FileSet:"DCTNSet" 2007-03-20 23:32:54 > Pool: "GovDeals" (From Job resource) > Storage:"DLT-Tape" (From Job resource) > Scheduled time: 26-Mar-2007 09:01:47 > Start time: 26-Mar-2007 09:01:57 > End time: 26-Mar-2007 09:39:59 > Elapsed time: 38 mins 2 secs > Priority: 10 > FD Files Written: 20,621 > SD Files Written: 0 > FD Bytes Written: 9,756,487,879 (9.756 GB) > SD Bytes Written: 0 (0 B) > Rate: 4275.4 KB/s > Software Compression: None > VSS:yes > Encryption: no > Volume name(s): > Volume Session Id: 2 > Volume Session Time:1174687096 > Last Volume Bytes: 64,512 (64.51 KB) > Non-fatal FD errors:0 > SD Errors: 0 > FD termination status: OK > SD termination status: Error > Termination:*** Backup Error *** > > The error messages are not descriptive. At the top, the message just > says "error". Then at the bottom it says "SD termination status: Error. > I don't know what any of that means. What does this all mean? This > backup job uses spooling BTW. > > Jason > > - > 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
