cancel
Showing results for 
Search instead for 
Did you mean: 

Backup failing with error code 13 after writing succcessfully for sometime

Varma_Chiluvuri
Level 5
Certified

Feb 24, 2012 3:17:48 PM - requesting resource nbu-media-grv-nb-hcart3-robot-tld-3
Feb 24, 2012 3:17:48 PM - requesting resource sun107-nb.NBU_CLIENT.MAXJOBS.sape8pdrv-nb
Feb 24, 2012 3:17:48 PM - requesting resource sun107-nb.NBU_POLICY.MAXJOBS.Grv_AIX_Zones_1
Feb 24, 2012 3:17:49 PM - granted resource  sun107-nb.NBU_CLIENT.MAXJOBS.sape8pdrv-nb
Feb 24, 2012 3:17:49 PM - granted resource  sun107-nb.NBU_POLICY.MAXJOBS.Grv_AIX_Zones_1
Feb 24, 2012 3:17:49 PM - granted resource  I00676
Feb 24, 2012 3:17:49 PM - granted resource  GRV_T10000_02
Feb 24, 2012 3:17:49 PM - granted resource  nbu-media-grv-nb-hcart3-robot-tld-3
Feb 24, 2012 3:17:49 PM - estimated 0 kbytes needed
Feb 24, 2012 3:43:55 PM - Error bpbrm (pid=8585352) socket read failed: errno = 119 - System call timed out
Feb 24, 2012 3:43:57 PM - end writing; write time: 0:26:02
file read failed  (13) 

 

Please let me know your suggestions. :)

1 ACCEPTED SOLUTION

Accepted Solutions

Mark_Solutions
Level 6
Partner Accredited Certified

AHH! - those removed lines were very important!

Looks like you file system backup is trying to back up open SAP/Oracle files on that system and this is pretty much killing it until it falls over.

You need to assess what is on this server and if there are live databases use an agent to back those up but exclude them from your file system backups - even if it diod catpture them they would probably be of no use to you.

Have a good look at it, set you excludes and try again

View solution in original post

5 REPLIES 5

Mark_Solutions
Level 6
Partner Accredited Certified

OK - so some basic questions please:

O/S, NBU Version, Type of backup etc. etc. - as much info as you can - see the blog specifying what info should be provided on an initial posting - Thanks

Now - it times out after about 26 minutes so we need to know what it is doing during that time.

As the estimated bytes is 0 I am guessing it has never worked

So let us know what the job actually is and if you use bpstart notify scripts - it looks like what ever its initial processing is doing it is taking too long - either that or it has multiple NICs and is sending its data over the wrong NIC

Varma_Chiluvuri
Level 5
Certified

OS ---  AIX 6.1

NBU Version --- NetBackup-AIX53 7.0

Type of Backup --- OS backup(incremental)

The backup has written 19011072 Kb of data.

I have removed few lines of log, please find the full log here ....

Feb 24, 2012 3:17:48 PM - requesting resource nbu-media-grv-nb-hcart3-robot-tld-3
Feb 24, 2012 3:17:48 PM - requesting resource sun107-nb.NBU_CLIENT.MAXJOBS.sape8pdrv-nb
Feb 24, 2012 3:17:48 PM - requesting resource sun107-nb.NBU_POLICY.MAXJOBS.Grv_AIX_Zones_1
Feb 24, 2012 3:17:49 PM - granted resource  sun107-nb.NBU_CLIENT.MAXJOBS.sape8pdrv-nb
Feb 24, 2012 3:17:49 PM - granted resource  sun107-nb.NBU_POLICY.MAXJOBS.Grv_AIX_Zones_1
Feb 24, 2012 3:17:49 PM - granted resource  I00676
Feb 24, 2012 3:17:49 PM - granted resource  GRV_T10000_02
Feb 24, 2012 3:17:49 PM - granted resource  nbu-media-grv-nb-hcart3-robot-tld-3
Feb 24, 2012 3:17:49 PM - estimated 0 kbytes needed
Feb 24, 2012 3:17:55 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /dev/SRC is a socket special file. Skipping.
Feb 24, 2012 3:17:55 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /dev/log is a socket special file. Skipping.
Feb 24, 2012 3:17:55 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /dev/.SRC-unix/SRC2Laeqm is a socket special file. Skipping.
Feb 24, 2012 3:17:55 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /dev/.SRC-unix/SRC3Laeqo is a socket special file. Skipping.
Feb 24, 2012 3:17:55 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /dev/.SRC-unix/SRC4-aeqq is a socket special file. Skipping.
Feb 24, 2012 3:17:55 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /dev/.SRC-unix/SRC4Taeqp is a socket special file. Skipping.
Feb 24, 2012 3:17:55 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /dev/.SRC-unix/SRC9Taeqs is a socket special file. Skipping.
Feb 24, 2012 3:17:56 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /dev/.SRC-unix/SRCAJaeqt is a socket special file. Skipping.
Feb 24, 2012 3:17:56 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /dev/.SRC-unix/SRCJLaeqa is a socket special file. Skipping.
Feb 24, 2012 3:17:56 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /dev/.SRC-unix/SRCKBaeqb is a socket special file. Skipping.
Feb 24, 2012 3:17:56 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /dev/.SRC-unix/SRCKTaeqc is a socket special file. Skipping.
Feb 24, 2012 3:17:56 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /dev/.SRC-unix/SRCNBaequ is a socket special file. Skipping.
Feb 24, 2012 3:17:56 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /dev/.SRC-unix/SRCOLaeqv is a socket special file. Skipping.
Feb 24, 2012 3:17:56 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /dev/.SRC-unix/SRCOZaeqw is a socket special file. Skipping.
Feb 24, 2012 3:17:57 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /dev/.SRC-unix/SRCPBaeqx is a socket special file. Skipping.
Feb 24, 2012 3:17:57 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /dev/.SRC-unix/SRCQTaeqd is a socket special file. Skipping.
Feb 24, 2012 3:17:57 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /dev/.SRC-unix/SRCQZaeqe is a socket special file. Skipping.
Feb 24, 2012 3:17:57 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /dev/.SRC-unix/SRCRDaeqf is a socket special file. Skipping.
Feb 24, 2012 3:17:57 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /dev/.SRC-unix/SRCRDaeqg is a socket special file. Skipping.
Feb 24, 2012 3:17:57 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /dev/.SRC-unix/SRCRJaeqh is a socket special file. Skipping.
Feb 24, 2012 3:17:57 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /dev/.SRC-unix/SRCRLaeqi is a socket special file. Skipping.
Feb 24, 2012 3:17:58 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /dev/.SRC-unix/SRCRTaeqj is a socket special file. Skipping.
Feb 24, 2012 3:17:58 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /dev/.SRC-unix/SRCY-aeqk is a socket special file. Skipping.
Feb 24, 2012 3:17:58 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /dev/.SRC-unix/SRCb6amyg is a socket special file. Skipping.
Feb 24, 2012 3:17:58 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /dev/.SRC-unix/SRCwDaeql is a socket special file. Skipping.
Feb 24, 2012 3:17:54 PM - connecting
Feb 24, 2012 3:17:55 PM - connected; connect time: 0:00:00
Feb 24, 2012 3:17:55 PM - begin writing
Feb 24, 2012 3:17:58 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /etc/cluster/clcomd_sec is a socket special file. Skipping.
Feb 24, 2012 3:18:27 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /opt/IBM/ITM/aix526/ux/bin/pasipc/.pas_sock is a socket special file. Skipping.
Feb 24, 2012 3:18:27 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /opt/IBM/ITM/aix526/ux/bin/pasipc/.pas_wd_sock is a socket special file. Skipping.
Feb 24, 2012 3:18:58 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /opt/freeware/cimom/pegasus/etc/cimxml.socket is a socket special file. Skipping.
Feb 24, 2012 3:20:03 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /opt/openv/var/vnetd/bpcd.uds is a socket special file. Skipping.
Feb 24, 2012 3:20:03 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /opt/openv/var/vnetd/terminate_bpcd.uds is a socket special file. Skipping.
Feb 24, 2012 3:20:03 PM - Info bpbrm (pid=8585352) from client sape8pdrv-nb: TRV - /opt/openv/var/vnetd/terminate_vnetd.uds is a socket special file. Skipping.
Feb 24, 2012 3:38:55 PM - Error bpbrm (pid=8585352) from client sape8pdrv-nb: ERR - Cannot process sparse file /oracle/E8P/saptemp1/temp_2/temp.data2. Errno = 22: Invalid argument
Feb 24, 2012 3:38:55 PM - Error bpbrm (pid=8585352) from client sape8pdrv-nb: ERR - Cannot process sparse file /oracle/E8P/saptemp1/temp_3/temp.data3. Errno = 22: Invalid argument
Feb 24, 2012 3:38:55 PM - Error bpbrm (pid=8585352) from client sape8pdrv-nb: ERR - Cannot process sparse file /oracle/E8P/saptemp1/temp_4/temp.data4. Errno = 22: Invalid argument
Feb 24, 2012 3:43:55 PM - Error bpbrm (pid=8585352) socket read failed: errno = 119 - System call timed out
Feb 24, 2012 3:43:57 PM - end writing; write time: 0:26:02
file read failed  (13)
 

Mark_Solutions
Level 6
Partner Accredited Certified

AHH! - those removed lines were very important!

Looks like you file system backup is trying to back up open SAP/Oracle files on that system and this is pretty much killing it until it falls over.

You need to assess what is on this server and if there are live databases use an agent to back those up but exclude them from your file system backups - even if it diod catpture them they would probably be of no use to you.

Have a good look at it, set you excludes and try again

Amarnath_Sathis
Level 5

Please find the attached PDF for the In-Depth Troubleshooting Guide for Error Code: 13.

Follow this if any clarification you can get back.

CRZ
Level 6
Employee Accredited Certified

Please don't add generic information to threads which are over a month old.  I know WHY you're doing it, but, please, don't do it.