cancel
Showing results for 
Search instead for 
Did you mean: 

System state / Shadow Copy Components backup failing with error code 13

AnilaReddy
Level 3

Hi All,

 

Wish you happy ne year to all.... 

 

Iam facign issue to fix System state / Shadow Copy Components backup failure, backup is failing ith error code 13.

 

Master server OS & NBU Version: HPUX - 7.5.0.6

Client server OS: idnos 2008 R2: 7.5.0.6

 

1) All writers are stable.

2) rebooted server and tryed backup but no luck

3) reregistered vss writers, but still no luck.

4) local NT backup is orkign fine and completed as well

backup speed is good also, after writign specific amount of data and files stream getting fail, no comunication issues. backups are moving to DD.

Pelase refer belo job logs and help me to fix issue, could you please suggst what next we can check.

01/01/2015 09:34:07 - Info nbjm (pid=9445) starting backup job (jobid=3556933) for client <client server>, policy xxx, schedule Weekly-Full
01/01/2015 09:34:07 - Info nbjm (pid=9445) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=3556933, request id:{3E1B929C-91C3-11E4-8A88-10604B350AB6})
01/01/2015 09:34:07 - requesting resource <STU group>
01/01/2015 09:34:07 - requesting resource <masterserver>.NBU_CLIENT.MAXJOBS.<client server>
01/01/2015 09:34:07 - requesting resource <masterserver>.NBU_POLICY.MAXJOBS.xxxxx
01/01/2015 09:34:07 - granted resource  <masterserver>.NBU_CLIENT.MAXJOBS.<client server>
01/01/2015 09:34:07 - granted resource  <masterserver>.NBU_POLICY.MAXJOBS.xxxxx
01/01/2015 09:34:07 - granted resource  MediaID=@aaaae;DiskVolume=stu ;DiskPool= xxxx;Path= xxxx;StorageServer=xxx;MediaServer=<media server1>
01/01/2015 09:34:07 - granted resource  <Stu group>
01/01/2015 09:34:07 - estimated 1485552 kbytes needed
01/01/2015 09:34:07 - Info nbjm (pid=9445) resumed backup (backupid=<masterserver>_1420122460) job for client <client server>, policy xxxxx, schedule Weekly-Full on storage unit <STU group>
01/01/2015 09:34:09 - started process bpbrm (pid=3672)
01/01/2015 09:34:10 - connecting
01/01/2015 09:34:11 - Info bpbrm (pid=3672) starting bpbkar on client
01/01/2015 09:34:11 - connected; connect time: 0:00:00
01/01/2015 09:34:14 - Info bpbkar (pid=4736) Backup started
01/01/2015 09:34:14 - Info bpbrm (pid=3672) bptm pid: 3676
01/01/2015 09:34:15 - Info bptm (pid=3676) start
01/01/2015 09:34:16 - Info bptm (pid=3676) using 524288 data buffer size
01/01/2015 09:34:16 - Info bptm (pid=3676) setting receive network buffer to 262144 bytes
01/01/2015 09:34:16 - Info bptm (pid=3676) using 64 data buffers
01/01/2015 09:34:18 - Info bptm (pid=3676) start backup
01/01/2015 09:34:19 - Info bptm (pid=3676) backup child process is pid 3680
01/01/2015 09:34:19 - begin writing
01/01/2015 09:34:50 - Error bpbrm (pid=3672) socket read failed: errno = 232 - Connection reset by peer
01/01/2015 09:34:50 - Error bptm (pid=3680) system call failed - Connection reset by peer (at child.c.1298)
01/01/2015 09:34:50 - Error bptm (pid=3680) unable to perform read from client socket, connection may have been broken
01/01/2015 09:34:50 - Error bptm (pid=3676) media manager terminated by parent process
01/01/2015 09:34:58 - Error bpbrm (pid=3672) could not send server status message
01/01/2015 09:34:58 - Info bpbkar (pid=4736) done. status: 13: file read failed
01/01/2015 09:34:58 - end writing; write time: 0:00:39
file read failed  (13)

 

1 ACCEPTED SOLUTION

Accepted Solutions

Michael_G_Ander
Level 6
Certified

The bpfis and bpkar together with the system and application event logs can probably give you an indication of what problem is. You might have to increase the verbosity level though

In my experience lot of these errors is caused by too small a shadow storage area, which not always shows up in the logs unfortunately.

http://blogs.technet.com/b/askcore/archive/2010/06/18/reasons-why-the-error-enumeration-of-the-files... is nice to know about when troubleshooting system state/shadow copy issues

Hopes this helps

 

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

View solution in original post

4 REPLIES 4

Michael_G_Ander
Level 6
Certified

The bpfis and bpkar together with the system and application event logs can probably give you an indication of what problem is. You might have to increase the verbosity level though

In my experience lot of these errors is caused by too small a shadow storage area, which not always shows up in the logs unfortunately.

http://blogs.technet.com/b/askcore/archive/2010/06/18/reasons-why-the-error-enumeration-of-the-files... is nice to know about when troubleshooting system state/shadow copy issues

Hopes this helps

 

The standard questions: Have you checked: 1) What has changed. 2) The manual 3) If there are any tech notes or VOX posts regarding the issue

Marianne
Level 6
Partner    VIP    Accredited Certified

All I see is a network error within 30 seconds:

01/01/2015 09:34:19 - begin writing
01/01/2015 09:34:50 - Error bpbrm (pid=3672) socket read failed: errno = 232 - Connection reset by peer

Have you created log folders on the client?
I would like to see bpbkar log at this point in time. Event Viewer logs may also be helpful.

Are other backups working on this client?

Have you tried to backup SCC to disk on this client? What is the result?

AnilaReddy
Level 3

This issue resolve with help of blog suggested by Michael..

 

 

Thanks all

Marianne
Level 6
Partner    VIP    Accredited Certified

Please be kind enough to mark Michael's post as Solution.

Marking a Solution (or split solution) for a helpful post does 2 things:
1. It helps other people with similar queries. When they Google and find your post, it will show a line like this at the top of the page:
This issue has been solved. See solution.
When the person then clicks on 'See solution' link, it will take him/her straight to the solution.

2. It gives a couple of points to the person(s) who helped you.
ALL of us helping here (even Symantec Employees) are doing so in our own time.
We help on the forum because we love the product and we really like to help people who battle with issues/queries/problems.