Status 13

[dwilson]

We are receiving a Status 13 error on  our SQL servers and cannot seem to figure out what is causing it. Below is our environment and Job Details we are receiving.

Environment

Master Server 7.6.0.2 (Windows Server 2008 R2)

Media Server 2.6.0.2 (Symantec 5220 appliance)

Client 7.6.0.2 ( Windows Server 2012

Job Details

2/20/2015 6:11:26 PM - Info nbjm(pid=5580) starting backup job (jobid=608077) for client USXD1SQLPRDS2, policy SQL_Wkend_SRV_HQ, schedule SQL_Server_Weekly_Full 
2/20/2015 6:11:26 PM - Info nbjm(pid=5580) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=608077, request id:{D7E91228-F1ED-4904-9EDE-AD0E730275E1}) 
2/20/2015 6:11:26 PM - requesting resource stu_disk_USXHQBCKSYM
2/20/2015 6:11:26 PM - requesting resource usxhqbck.NBU_CLIENT.MAXJOBS.USXD1SQLPRDS2
2/20/2015 6:11:26 PM - requesting resource usxhqbck.NBU_POLICY.MAXJOBS.SQL_Wkend_SRV_HQ
2/20/2015 6:11:26 PM - awaiting resource stu_disk_USXHQBCKSYM - Maximum job count has been reached for the storage unit
2/20/2015 8:14:46 PM - granted resource usxhqbck.NBU_CLIENT.MAXJOBS.USXD1SQLPRDS2
2/20/2015 8:14:46 PM - granted resource usxhqbck.NBU_POLICY.MAXJOBS.SQL_Wkend_SRV_HQ
2/20/2015 8:14:46 PM - granted resource MediaID=@aaaak;DiskVolume=PureDiskVolume;DiskPool=dp_disk_usxhqbcksym;Path=PureDiskVolume;StorageSer...
2/20/2015 8:14:46 PM - granted resource stu_disk_USXHQBCKSYM
2/20/2015 8:14:46 PM - estimated 22359200 Kbytes needed
2/20/2015 8:14:46 PM - Info nbjm(pid=5580) resumed backup (backupid=USXD1SQLPRDS2_1424473251) job for client USXD1SQLPRDS2, policy SQL_Wkend_SRV_HQ, schedule SQL_Server_Weekly_Full on storage unit stu_disk_USXHQBCKSYM
2/20/2015 8:14:47 PM - started process bpbrm (420)
2/20/2015 8:14:48 PM - Info bpbrm(pid=420) USXD1SQLPRDS2 is the host to backup data from    
2/20/2015 8:14:48 PM - Info bpbrm(pid=420) reading file list for client       
2/20/2015 8:14:48 PM - Info bpbrm(pid=420) accelerator enabled          
2/20/2015 8:14:50 PM - Info bpbrm(pid=420) starting bpbkar on client        
2/20/2015 8:14:50 PM - connecting
2/20/2015 8:14:50 PM - connected; connect time: 0:00:00
2/20/2015 8:15:01 PM - Error bpbrm(pid=420) socket read failed: errno = 104 - Connection reset by peer 
2/20/2015 8:15:05 PM - Info bpbkar(pid=0) done. status: 13: file read failed      
2/20/2015 8:15:05 PM - end writing
file read failed(13)

[Marianne]

Mmmm... not a timeout as backup fails within a few seconds:

2/20/2015 8:14:50 PM - connected; connect time: 0:00:00
2/20/2015 8:15:01 PM - Error bpbrm(pid=420) socket read failed: errno = 104 - Connection reset by peer  

Only thing to do is enable logs. I doubt that level 0 will be sufficient. 
Level 3 could suffice for Connect assistance, but if a call with Symantec is needed they will ask for level 5 logs.

This looks like a normal filesystem backup, not SQL, right?

On media server: bpbrm and bptm

On client: bpcd and bpbkar

Check OS Event logs on the client - System and Application.
Look for something that could be killing processes (AV or other security software).

[dwilson]

Thanks Marianne, that is correct MS-Windows policy trying to do Shadow Copy and C: backups. I will get these logs enabled and run the job and then report back.

[dwilson · Accepted solution]

Sorry I havent updated, other projects. We finally got this issue straightened out by rebooting the client.