NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

in-depth Troubleshooting Guide for Exit Status Code 13 in NetBackup (tm) Server / Enterprise Server 5.0 / 5.1

13
TECH38879 | 2013-10-23
Technical Solutions | CMS-XML

NetBackup status code 13

After a NetBackup installation, it is possible for the first ev-sql backup policy to fail with a status 13 error . If an ev-sql backup fails with a status 13, do the following:
HOWTO92227 | 2013-10-03
How To | CMS-XML

NetBackup status code 13

After a NetBackup installation, it is possible for the first ev-sql backup policy to fail with a status 13 error . If an ev-sql backup fails with a status 13, do the following:
HOWTO70029 | 2012-02-07
How To | CMS-XML

NetBackup status code 13

After a NetBackup installation, it is possible for the first ev-sql backup policy to fail with a status 13 error . If an ev-sql backup fails with a status 13, do the following:
HOWTO54622 | 2011-06-20
How To | CMS-XML

in-depth Troubleshooting Guide for Exit Status Code 13 in NetBackup Server (tm) / NetBackup Enterprise Server (tm) 6.0

13
TECH43240 | 2010-09-07
Technical Solutions | CMS-XML

SharePoint backup fails with status code 13 due to conflicting streams backup.

Job detailed status : 6/20/2014 2:01:10 AM - Info bptm(pid=5432) start 6/20/2014 2:01:10 AM - begin writing
TECH222208 | 2014-08-06
Technical Solutions | CMS-XML

Error status - backup error 13 file read failed. Job details show 'socket read failed: errno = 62 - Timer expired'

bpbrm shows the following error : 15:24:07.908 [31147] 2 bpbrm mm_sig: received ready signal from media manager 15:29:07.908 [31147] 16 bpbrm readline: socket read failed: errno = 62 - Timer expired .. 15:29:30.716
TECH141299 | 2014-05-29
Technical Solutions | CMS-XML

13: Some of the clients behind the firewall are failing with a Status 13 file read failure / 131 - Connection reset by peer

• UNIX: /usr/openv/netbackup/bin/admincmd # resilient_clients status | on | off nbuclientname ex. resilient_clients on mynbuclientname
TECH178712 | 2014-05-07
Technical Solutions | CMS-XML

NetBackup for Microsoft Sharepoint 2010 Agent backups fail with status 13 when using SQL 2012 backend after bpbkar32.exe crashes.

Application Error e1000 Faulting application name: bpbkar32.exe
TECH214203 | 2014-05-08
Technical Solutions | CMS-XML

file read failed:Status 13 on all VMs using SAN transfer type - " VixDiskLib: No transport modes availble to access disks"

bpbkar ends with status 6:
TECH165311 | 2014-04-23
Technical Solutions | CMS-XML

Incremental backup failed for db2 database with status code 13 on unix client.

Job detailed status : 2014/1/21 22:06:54 - Error bpbrm(pid=15740) socket read failed: errno = 62 - Timer expired 2014/1/21 22:06:56 - Error bptm(pid=15743) media manager terminated by parent process
TECH215027 | 2014-03-26
Technical Solutions | CMS-XML

Shadow Copy Components Backup fails with status 13 due to error "Could not allocate memory for Metadata Stream"

Shadow Copy Components backup fails with status 13
TECH176570 | 2014-02-06
Technical Solutions | CMS-XML

BUG REPORT: Large NDMP backup with HIST=Y fails with status 150/13/84 during image catalog update after the data transfer completes.

shows that bpdbm returned a status 13 while ndmpagent returned a status 0.
TECH69804 | 2014-01-20
Technical Solutions | CMS-XML

NetBackup for Microsoft Exchange database availability group (DAG) backups fail with Status 13 on a Passive node copy

NetBackup for Microsoft Exchange database availability group (DAG) backups fail with Status 13 on a Passive node copy
TECH171234 | 2013-11-27
Technical Solutions | CMS-XML

VMware ESX5 and esx5i virtual machine backups fail with Status 13.

Status 13
TECH184005 | 2013-11-27
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?