Re: [Veritas-bu] retrying Error on job keeps going status 13
The new machine took the original machines name and IP. The only network activity is master server/ media server chatter. No backup data goes across the network. This media server only backs itself up. It takes long enough to do that, it has 11 300gb drives with over 15 million little files per drive. I was able to do backups if VSS was disabled. Not a real solution. It appears it was a windows install issue. There were two files that did not have the right date or time for the files at the service pack and patch level running on the server. Found the error using vshadow.exe -wm2 vhadow.txt on this machine and on a working media server. Found the problem showing path = \ on the bad media server ch3ecked the good media server found the file should have been where the \ was and replaced those files. Theyt were syste protected files so reboots were in order. After replacing the two files I am now able to backup the server using VSS for open files and getting volume shadow components. Thanks all who replied. Doug Preston -Original Message- From: WEAVER, Simon (external) [mailto:simon.wea...@astrium.eads.net] Sent: Tuesday, April 13, 2010 1:16 AM To: Preston, Douglas; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 Hi Doug Becuase you get this message socket read failed, An existing connection was forcibly closed by the remote host, I am sort of 60% sure its network / file related. I take it, there are no firewalls in place between the server and the clients and no MAC lockdowns at all? You stated its a new Server, so thought I would just ask. Also, can the backup be done using NTBackup as a test (ie: try doing a netbackup test of a C: Drive of a client machine and then try using NTBackup on the same client). Simon -Original Message- From: WEAVER, Simon (external) Sent: Tuesday, April 13, 2010 9:14 AM To: 'Preston, Douglas'; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 Doug Have you tried to do a backup, without Open File Backups being enabled (as a test of course). Simon -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Preston, Douglas Sent: Monday, April 12, 2010 4:36 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] retrying Error on job keeps going status 13 This was a scsi backplane on a dell server. It controlled my O/S drives. We replaced server with an IBM server and had to reinstall O/S, Installed two new Fiber cards fro san and tape library connections, Re did all zoning and updated all drives and O/S updates to the very latest of all drivers and patches as of 19:00 hours yesterday. I have a case open with support and they had me try the patch from http://support.microsoft.com/kb/940349 I rebooted the server after applying the patch This patch did not fix issue. Doug Preston -Original Message- From: Shekel Tal [mailto:tal.she...@uk.fujitsu.com] Sent: Monday, April 12, 2010 6:51 AM To: Preston, Douglas; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 What hardware did you change? Error 13/4 can be a real pain but they are often related to network issues or reading data off a file system. As this is happening to all your jobs it sounds network related Have you checked some of your system/NetBackup legacy logs? Also run a all log entries report on one of the job ids to check for more details regarding the error message Regards, Tal -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Preston, Douglas Sent: 12 April 2010 14:32 To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] retrying Error on job keeps going status 13 I had to replace the hardware on one of my media svers and now all my jobs on that media server end in status 13 Server O/S Windows 2003 Netbackup 6.5.3 Library Quantum (Adic) I2000 14 LTO2 drives Any ideas would surely be appreciated. Master server Job log 4/6/2010 10:01:33 AM - requesting resource scacidoc05-hcart2-robot-tld-0 4/6/2010 10:01:33 AM - requesting resource svcacibu1.NBU_CLIENT.MAXJOBS.scacidoc05 4/6/2010 10:01:33 AM - requesting resource svcacibu1.NBU_POLICY.MAXJOBS.1-doc05-test 4/6/2010 10:01:33 AM - granted resource svcacibu1.NBU_CLIENT.MAXJOBS.scacidoc05 4/6/2010 10:01:33 AM - granted resource svcacibu1.NBU_POLICY.MAXJOBS.1-doc05-test 4/6/2010 10:01:33 AM - granted resource 000385 4/6/2010 10:01:33 AM - granted resource IBMULTRIUM-TD213 4/6/2010 10:01:33 AM - granted resource scacidoc05-hcart2-robot-tld-0 4/6/2010 10:01:33 AM - estimated 0 kbytes needed 4/6/2010 10:01:35 AM - started process bpbrm (5340) 4/6/2010 10:01:44 AM - connecting 4/6/2010 10:01:44 AM - connected; connect time: 00:00:00 4/6/2010 10:01:45 AM - mounting
Re: [Veritas-bu] retrying Error on job keeps going status 13
Yes Steve Anderson at Symantec support found this for me, He helped me spot the issue and gave me the resolution to try. http://seer.entsupport.symantec.com/docs/315898.htm Doug Preston -Original Message- From: WEAVER, Simon (external) [mailto:simon.wea...@astrium.eads.net] Sent: Tuesday, April 13, 2010 7:34 AM To: Preston, Douglas; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 Doug Was this identified by Symantec? Was there a Technote about this? Handy to know this. Simon -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Preston, Douglas Sent: Tuesday, April 13, 2010 3:09 PM To: WEAVER, Simon (external); VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] retrying Error on job keeps going status 13 The new machine took the original machines name and IP. The only network activity is master server/ media server chatter. No backup data goes across the network. This media server only backs itself up. It takes long enough to do that, it has 11 300gb drives with over 15 million little files per drive. I was able to do backups if VSS was disabled. Not a real solution. It appears it was a windows install issue. There were two files that did not have the right date or time for the files at the service pack and patch level running on the server. Found the error using vshadow.exe -wm2 vhadow.txt on this machine and on a working media server. Found the problem showing path = \ on the bad media server ch3ecked the good media server found the file should have been where the \ was and replaced those files. Theyt were syste protected files so reboots were in order. After replacing the two files I am now able to backup the server using VSS for open files and getting volume shadow components. Thanks all who replied. Doug Preston -Original Message- From: WEAVER, Simon (external) [mailto:simon.wea...@astrium.eads.net] Sent: Tuesday, April 13, 2010 1:16 AM To: Preston, Douglas; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 Hi Doug Becuase you get this message socket read failed, An existing connection was forcibly closed by the remote host, I am sort of 60% sure its network / file related. I take it, there are no firewalls in place between the server and the clients and no MAC lockdowns at all? You stated its a new Server, so thought I would just ask. Also, can the backup be done using NTBackup as a test (ie: try doing a netbackup test of a C: Drive of a client machine and then try using NTBackup on the same client). Simon -Original Message- From: WEAVER, Simon (external) Sent: Tuesday, April 13, 2010 9:14 AM To: 'Preston, Douglas'; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 Doug Have you tried to do a backup, without Open File Backups being enabled (as a test of course). Simon -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Preston, Douglas Sent: Monday, April 12, 2010 4:36 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] retrying Error on job keeps going status 13 This was a scsi backplane on a dell server. It controlled my O/S drives. We replaced server with an IBM server and had to reinstall O/S, Installed two new Fiber cards fro san and tape library connections, Re did all zoning and updated all drives and O/S updates to the very latest of all drivers and patches as of 19:00 hours yesterday. I have a case open with support and they had me try the patch from http://support.microsoft.com/kb/940349 I rebooted the server after applying the patch This patch did not fix issue. Doug Preston -Original Message- From: Shekel Tal [mailto:tal.she...@uk.fujitsu.com] Sent: Monday, April 12, 2010 6:51 AM To: Preston, Douglas; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 What hardware did you change? Error 13/4 can be a real pain but they are often related to network issues or reading data off a file system. As this is happening to all your jobs it sounds network related Have you checked some of your system/NetBackup legacy logs? Also run a all log entries report on one of the job ids to check for more details regarding the error message Regards, Tal -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Preston, Douglas Sent: 12 April 2010 14:32 To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] retrying Error on job keeps going status 13 I had to replace the hardware on one of my media svers and now all my jobs on that media server end in status 13 Server O/S Windows 2003 Netbackup 6.5.3 Library Quantum (Adic) I2000 14 LTO2 drives
Re: [Veritas-bu] retrying Error on job keeps going status 13
The errors in NBU did not reflect this issue. The errors you see in the Technote are from the output of vshadow.exe -wm2 With debug logging and all logging turned on as high as they get there was no mention of anything that would indicate the issue that this technote refers to. But doing a search on their support site with this bpbkar to provide an Application Pop Up Error takes me in a roundabout way to the technote. Doug Preston -Original Message- From: WEAVER, Simon (external) [mailto:simon.wea...@astrium.eads.net] Sent: Tuesday, April 13, 2010 7:48 AM To: Preston, Douglas; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 Doug Was you getting these error messages in your logs? Simon -Original Message- From: Preston, Douglas [mailto:dlpres...@lereta.com] Sent: Tuesday, April 13, 2010 3:39 PM To: WEAVER, Simon (external); VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 Yes Steve Anderson at Symantec support found this for me, He helped me spot the issue and gave me the resolution to try. http://seer.entsupport.symantec.com/docs/315898.htm Doug Preston -Original Message- From: WEAVER, Simon (external) [mailto:simon.wea...@astrium.eads.net] Sent: Tuesday, April 13, 2010 7:34 AM To: Preston, Douglas; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 Doug Was this identified by Symantec? Was there a Technote about this? Handy to know this. Simon -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Preston, Douglas Sent: Tuesday, April 13, 2010 3:09 PM To: WEAVER, Simon (external); VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] retrying Error on job keeps going status 13 The new machine took the original machines name and IP. The only network activity is master server/ media server chatter. No backup data goes across the network. This media server only backs itself up. It takes long enough to do that, it has 11 300gb drives with over 15 million little files per drive. I was able to do backups if VSS was disabled. Not a real solution. It appears it was a windows install issue. There were two files that did not have the right date or time for the files at the service pack and patch level running on the server. Found the error using vshadow.exe -wm2 vhadow.txt on this machine and on a working media server. Found the problem showing path = \ on the bad media server ch3ecked the good media server found the file should have been where the \ was and replaced those files. Theyt were syste protected files so reboots were in order. After replacing the two files I am now able to backup the server using VSS for open files and getting volume shadow components. Thanks all who replied. Doug Preston -Original Message- From: WEAVER, Simon (external) [mailto:simon.wea...@astrium.eads.net] Sent: Tuesday, April 13, 2010 1:16 AM To: Preston, Douglas; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 Hi Doug Becuase you get this message socket read failed, An existing connection was forcibly closed by the remote host, I am sort of 60% sure its network / file related. I take it, there are no firewalls in place between the server and the clients and no MAC lockdowns at all? You stated its a new Server, so thought I would just ask. Also, can the backup be done using NTBackup as a test (ie: try doing a netbackup test of a C: Drive of a client machine and then try using NTBackup on the same client). Simon -Original Message- From: WEAVER, Simon (external) Sent: Tuesday, April 13, 2010 9:14 AM To: 'Preston, Douglas'; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 Doug Have you tried to do a backup, without Open File Backups being enabled (as a test of course). Simon -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Preston, Douglas Sent: Monday, April 12, 2010 4:36 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] retrying Error on job keeps going status 13 This was a scsi backplane on a dell server. It controlled my O/S drives. We replaced server with an IBM server and had to reinstall O/S, Installed two new Fiber cards fro san and tape library connections, Re did all zoning and updated all drives and O/S updates to the very latest of all drivers and patches as of 19:00 hours yesterday. I have a case open with support and they had me try the patch from http://support.microsoft.com/kb/940349 I rebooted the server after applying the patch This patch did not fix issue. Doug Preston -Original Message- From: Shekel Tal [mailto:tal.she...@uk.fujitsu.com] Sent: Monday
[Veritas-bu] retrying Error on job keeps going status 13
I had to replace the hardware on one of my media svers and now all my jobs on that media server end in status 13 Server O/S Windows 2003 Netbackup 6.5.3 Library Quantum (Adic) I2000 14 LTO2 drives Any ideas would surely be appreciated. Master server Job log 4/6/2010 10:01:33 AM - requesting resource scacidoc05-hcart2-robot-tld-0 4/6/2010 10:01:33 AM - requesting resource svcacibu1.NBU_CLIENT.MAXJOBS.scacidoc05 4/6/2010 10:01:33 AM - requesting resource svcacibu1.NBU_POLICY.MAXJOBS.1-doc05-test 4/6/2010 10:01:33 AM - granted resource svcacibu1.NBU_CLIENT.MAXJOBS.scacidoc05 4/6/2010 10:01:33 AM - granted resource svcacibu1.NBU_POLICY.MAXJOBS.1-doc05-test 4/6/2010 10:01:33 AM - granted resource 000385 4/6/2010 10:01:33 AM - granted resource IBMULTRIUM-TD213 4/6/2010 10:01:33 AM - granted resource scacidoc05-hcart2-robot-tld-0 4/6/2010 10:01:33 AM - estimated 0 kbytes needed 4/6/2010 10:01:35 AM - started process bpbrm (5340) 4/6/2010 10:01:44 AM - connecting 4/6/2010 10:01:44 AM - connected; connect time: 00:00:00 4/6/2010 10:01:45 AM - mounting 000385 4/6/2010 10:02:06 AM - mounted; mount time: 00:00:21 4/6/2010 10:02:07 AM - positioning 000385 to file 1396 4/6/2010 10:02:15 AM - Error bpbrm(pid=3740) could not write KEEPALIVE to COMM_SOCK 4/6/2010 10:02:43 AM - Error bpbrm(pid=3740) socket read failed, An existing connection was forcibly closed by the remote host. (10054) 4/6/2010 10:02:34 AM - positioned 000385; position time: 00:00:27 4/6/2010 10:02:34 AM - begin writing 4/6/2010 10:02:44 AM - Error bpbrm(pid=3740) could not send server status message 4/6/2010 10:02:55 AM - end writing; write time: 00:00:21 file read failed(13) Media server bpbkar log 10:50:39.706 AM: [5496.4724] 4 ov_log::OVInit: INF - Starting log file: F:\Program Files\Veritas\NetBackup\logs\BPBKAR\040610.LOG 10:50:39.706 AM: [5496.4724] 4 ov_log::OVInit: GENERAL Log Level: 2 10:50:39.706 AM: [5496.4724] 4 ov_log::OVInit: TCP Log Level: 3 10:50:39.706 AM: [5496.4724] 4 ov_log::OVInit: INF - the log mutex: 1776 BPBKAR NetBackup Backup/Archive 6.5GA [Oct 30 2008] Copyright 1993 - 2007 VERITAS Software Corporation All Rights Reserved. 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - WINSOCK.DLL Information: 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - Version: 2.0 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - Highest supported version: 2.2 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - Description: WinSock 2.0 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - System Status: Running 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - Max Sockets: 0 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - _pgmptr = 'F:\Program Files\Veritas\NetBackup\bin\bpbkar32.exe' 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - lpCmdLine = '-r 2678400 -ru root -dt 0 -to 300 -clnt scacidoc05 -class 1-doc05-test -sched Cumulative-Inc -st CINC -bpstart_to 300 -bpend_to 300 -read_to 300 -blks_per_buffer 127 -stream_count 4 -stream_number 4 -jobgrpid 962086 -use_otm -use_ofb -b scacidoc05_1270576234 -kl 400 -shm -fso -ct 13 ' 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - INI: drive=F, dir=\Program Files\Veritas\NetBackup 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - LOG: drive=F, dir=\Program Files\Veritas\NetBackup\logs 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - EXE: drive=F, dir=\Program Files\Veritas\NetBackup\bin 10:50:39.722 AM: [5496.4724] 2 date_debug: DAT - timezone: Pacific Standard Time, offset=28800, dst: Pacific Daylight Time 10:50:39.722 AM: [5496.4724] 2 date_debug: DAT - current time: 1270576239, 4/6/2010 10:50:39 AM 10:50:39.722 AM: [5496.4724] 2 date_debug: DAT - 01/01/94 UCT: 757382400, 12/31/1993 5:00:00 PM 10:50:39.722 AM: [5496.4724] 2 date_debug: DAT - 07/01/94 UCT: 773020800, 6/30/1994 5:00:00 PM 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - standard input handle = 548 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - standard output handle = 1848 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - standard error handle = 1856 10:50:39.722 AM: [5496.4724] 2 dtcp_setsocksize: TCP - setsockopt success on SO_RCVBUF: (socket: 548) (size: 33792) 10:50:39.722 AM: [5496.4724] 2 dtcp_setsocksize: TCP - setsockopt success on SO_SNDBUF: (socket: 548) (size: 33792) 10:50:39.722 AM: [5496.4724] 2 dtcp_setsocksize: TCP - setsockopt success on SO_RCVBUF: (socket: 1848) (size: 33792) 10:50:39.722 AM: [5496.4724] 2 dtcp_setsocksize: TCP - setsockopt success on SO_SNDBUF: (socket: 1848) (size: 33792) 10:50:39.722 AM: [5496.4724] 2 dtcp_setsocksize: TCP - setsockopt success on SO_RCVBUF: (socket: 1856) (size: 32768) 10:50:39.722 AM: [5496.4724] 2 dtcp_setsocksize: TCP - setsockopt success on SO_SNDBUF: (socket: 1856) (size: 32768) 10:50:39.737 AM: [5496.4724] 2 OVHasPrivileges: TCP - success: connection from host scacidoc05.landam.landamerica.net (10.212.171.38) bound to port (4551) 10:50:39.737 AM: [5496.4724] 4 tar_backup::V_SetupJobData: INF - dwJobData: 10:50:39.737 AM:
Re: [Veritas-bu] retrying Error on job keeps going status 13
What hardware did you change? Error 13/4 can be a real pain but they are often related to network issues or reading data off a file system. As this is happening to all your jobs it sounds network related Have you checked some of your system/NetBackup legacy logs? Also run a all log entries report on one of the job ids to check for more details regarding the error message Regards, Tal -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Preston, Douglas Sent: 12 April 2010 14:32 To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] retrying Error on job keeps going status 13 I had to replace the hardware on one of my media svers and now all my jobs on that media server end in status 13 Server O/S Windows 2003 Netbackup 6.5.3 Library Quantum (Adic) I2000 14 LTO2 drives Any ideas would surely be appreciated. Master server Job log 4/6/2010 10:01:33 AM - requesting resource scacidoc05-hcart2-robot-tld-0 4/6/2010 10:01:33 AM - requesting resource svcacibu1.NBU_CLIENT.MAXJOBS.scacidoc05 4/6/2010 10:01:33 AM - requesting resource svcacibu1.NBU_POLICY.MAXJOBS.1-doc05-test 4/6/2010 10:01:33 AM - granted resource svcacibu1.NBU_CLIENT.MAXJOBS.scacidoc05 4/6/2010 10:01:33 AM - granted resource svcacibu1.NBU_POLICY.MAXJOBS.1-doc05-test 4/6/2010 10:01:33 AM - granted resource 000385 4/6/2010 10:01:33 AM - granted resource IBMULTRIUM-TD213 4/6/2010 10:01:33 AM - granted resource scacidoc05-hcart2-robot-tld-0 4/6/2010 10:01:33 AM - estimated 0 kbytes needed 4/6/2010 10:01:35 AM - started process bpbrm (5340) 4/6/2010 10:01:44 AM - connecting 4/6/2010 10:01:44 AM - connected; connect time: 00:00:00 4/6/2010 10:01:45 AM - mounting 000385 4/6/2010 10:02:06 AM - mounted; mount time: 00:00:21 4/6/2010 10:02:07 AM - positioning 000385 to file 1396 4/6/2010 10:02:15 AM - Error bpbrm(pid=3740) could not write KEEPALIVE to COMM_SOCK 4/6/2010 10:02:43 AM - Error bpbrm(pid=3740) socket read failed, An existing connection was forcibly closed by the remote host. (10054) 4/6/2010 10:02:34 AM - positioned 000385; position time: 00:00:27 4/6/2010 10:02:34 AM - begin writing 4/6/2010 10:02:44 AM - Error bpbrm(pid=3740) could not send server status message 4/6/2010 10:02:55 AM - end writing; write time: 00:00:21 file read failed(13) Media server bpbkar log 10:50:39.706 AM: [5496.4724] 4 ov_log::OVInit: INF - Starting log file: F:\Program Files\Veritas\NetBackup\logs\BPBKAR\040610.LOG 10:50:39.706 AM: [5496.4724] 4 ov_log::OVInit: GENERAL Log Level: 2 10:50:39.706 AM: [5496.4724] 4 ov_log::OVInit: TCP Log Level: 3 10:50:39.706 AM: [5496.4724] 4 ov_log::OVInit: INF - the log mutex: 1776 BPBKAR NetBackup Backup/Archive 6.5GA [Oct 30 2008] Copyright 1993 - 2007 VERITAS Software Corporation All Rights Reserved. 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - WINSOCK.DLL Information: 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - Version: 2.0 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - Highest supported version: 2.2 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - Description: WinSock 2.0 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - System Status: Running 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - Max Sockets: 0 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - _pgmptr = 'F:\Program Files\Veritas\NetBackup\bin\bpbkar32.exe' 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - lpCmdLine = '-r 2678400 -ru root -dt 0 -to 300 -clnt scacidoc05 -class 1-doc05-test -sched Cumulative-Inc -st CINC -bpstart_to 300 -bpend_to 300 -read_to 300 -blks_per_buffer 127 -stream_count 4 -stream_number 4 -jobgrpid 962086 -use_otm -use_ofb -b scacidoc05_1270576234 -kl 400 -shm -fso -ct 13 ' 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - INI: drive=F, dir=\Program Files\Veritas\NetBackup 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - LOG: drive=F, dir=\Program Files\Veritas\NetBackup\logs 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - EXE: drive=F, dir=\Program Files\Veritas\NetBackup\bin 10:50:39.722 AM: [5496.4724] 2 date_debug: DAT - timezone: Pacific Standard Time, offset=28800, dst: Pacific Daylight Time 10:50:39.722 AM: [5496.4724] 2 date_debug: DAT - current time: 1270576239, 4/6/2010 10:50:39 AM 10:50:39.722 AM: [5496.4724] 2 date_debug: DAT - 01/01/94 UCT: 757382400, 12/31/1993 5:00:00 PM 10:50:39.722 AM: [5496.4724] 2 date_debug: DAT - 07/01/94 UCT: 773020800, 6/30/1994 5:00:00 PM 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - standard input handle = 548 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - standard output handle = 1848 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - standard error handle = 1856 10:50:39.722 AM: [5496.4724] 2 dtcp_setsocksize: TCP - setsockopt success on SO_RCVBUF: (socket: 548) (size: 33792) 10:50:39.722 AM: [5496.4724] 2 dtcp_setsocksize: TCP - setsockopt success on SO_SNDBUF: (socket: 548) (size: 33792) 10:50:39.722 AM: [5496.4724] 2 dtcp_setsocksize: TCP - setsockopt success
Re: [Veritas-bu] retrying Error on job keeps going status 13
This was a scsi backplane on a dell server. It controlled my O/S drives. We replaced server with an IBM server and had to reinstall O/S, Installed two new Fiber cards fro san and tape library connections, Re did all zoning and updated all drives and O/S updates to the very latest of all drivers and patches as of 19:00 hours yesterday. I have a case open with support and they had me try the patch from http://support.microsoft.com/kb/940349 I rebooted the server after applying the patch This patch did not fix issue. Doug Preston -Original Message- From: Shekel Tal [mailto:tal.she...@uk.fujitsu.com] Sent: Monday, April 12, 2010 6:51 AM To: Preston, Douglas; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] retrying Error on job keeps going status 13 What hardware did you change? Error 13/4 can be a real pain but they are often related to network issues or reading data off a file system. As this is happening to all your jobs it sounds network related Have you checked some of your system/NetBackup legacy logs? Also run a all log entries report on one of the job ids to check for more details regarding the error message Regards, Tal -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Preston, Douglas Sent: 12 April 2010 14:32 To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] retrying Error on job keeps going status 13 I had to replace the hardware on one of my media svers and now all my jobs on that media server end in status 13 Server O/S Windows 2003 Netbackup 6.5.3 Library Quantum (Adic) I2000 14 LTO2 drives Any ideas would surely be appreciated. Master server Job log 4/6/2010 10:01:33 AM - requesting resource scacidoc05-hcart2-robot-tld-0 4/6/2010 10:01:33 AM - requesting resource svcacibu1.NBU_CLIENT.MAXJOBS.scacidoc05 4/6/2010 10:01:33 AM - requesting resource svcacibu1.NBU_POLICY.MAXJOBS.1-doc05-test 4/6/2010 10:01:33 AM - granted resource svcacibu1.NBU_CLIENT.MAXJOBS.scacidoc05 4/6/2010 10:01:33 AM - granted resource svcacibu1.NBU_POLICY.MAXJOBS.1-doc05-test 4/6/2010 10:01:33 AM - granted resource 000385 4/6/2010 10:01:33 AM - granted resource IBMULTRIUM-TD213 4/6/2010 10:01:33 AM - granted resource scacidoc05-hcart2-robot-tld-0 4/6/2010 10:01:33 AM - estimated 0 kbytes needed 4/6/2010 10:01:35 AM - started process bpbrm (5340) 4/6/2010 10:01:44 AM - connecting 4/6/2010 10:01:44 AM - connected; connect time: 00:00:00 4/6/2010 10:01:45 AM - mounting 000385 4/6/2010 10:02:06 AM - mounted; mount time: 00:00:21 4/6/2010 10:02:07 AM - positioning 000385 to file 1396 4/6/2010 10:02:15 AM - Error bpbrm(pid=3740) could not write KEEPALIVE to COMM_SOCK 4/6/2010 10:02:43 AM - Error bpbrm(pid=3740) socket read failed, An existing connection was forcibly closed by the remote host. (10054) 4/6/2010 10:02:34 AM - positioned 000385; position time: 00:00:27 4/6/2010 10:02:34 AM - begin writing 4/6/2010 10:02:44 AM - Error bpbrm(pid=3740) could not send server status message 4/6/2010 10:02:55 AM - end writing; write time: 00:00:21 file read failed(13) Media server bpbkar log 10:50:39.706 AM: [5496.4724] 4 ov_log::OVInit: INF - Starting log file: F:\Program Files\Veritas\NetBackup\logs\BPBKAR\040610.LOG 10:50:39.706 AM: [5496.4724] 4 ov_log::OVInit: GENERAL Log Level: 2 10:50:39.706 AM: [5496.4724] 4 ov_log::OVInit: TCP Log Level: 3 10:50:39.706 AM: [5496.4724] 4 ov_log::OVInit: INF - the log mutex: 1776 BPBKAR NetBackup Backup/Archive 6.5GA [Oct 30 2008] Copyright 1993 - 2007 VERITAS Software Corporation All Rights Reserved. 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - WINSOCK.DLL Information: 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - Version: 2.0 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - Highest supported version: 2.2 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - Description: WinSock 2.0 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - System Status: Running 10:50:39.722 AM: [5496.4724] 4 dtcp_initialize: TCP - Max Sockets: 0 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - _pgmptr = 'F:\Program Files\Veritas\NetBackup\bin\bpbkar32.exe' 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - lpCmdLine = '-r 2678400 -ru root -dt 0 -to 300 -clnt scacidoc05 -class 1-doc05-test -sched Cumulative-Inc -st CINC -bpstart_to 300 -bpend_to 300 -read_to 300 -blks_per_buffer 127 -stream_count 4 -stream_number 4 -jobgrpid 962086 -use_otm -use_ofb -b scacidoc05_1270576234 -kl 400 -shm -fso -ct 13 ' 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - INI: drive=F, dir=\Program Files\Veritas\NetBackup 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - LOG: drive=F, dir=\Program Files\Veritas\NetBackup\logs 10:50:39.722 AM: [5496.4724] 2 WinMain: DAT - EXE: drive=F, dir=\Program Files\Veritas\NetBackup\bin 10:50:39.722 AM: [5496.4724] 2 date_debug: DAT - timezone: Pacific Standard Time, offset=28800, dst: Pacific Daylight Time 10:50:39.722 AM: [5496.4724] 2
