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

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

STATUS CODE 13: Backups fail with status code 13 (file read failed) reported

16 bpbrm handle_backup: db_flistsend failed: file read failed ( 13 )
TECH58549 | 2014-12-15
Technical Solutions | CMS-XML

NDMP backup of EqualLogic fs7500 filer fails with status 13

The Job Details show that bpbrm received status 13 from bpdbm when requesting to insert the meta data about the files that were backed up into the image database. 06/29/2012 15:12:41 - Info ndmpagent (pid=9723) 0 entries sent to bpdbm
TECH192541 | 2014-12-01
Technical Solutions | CMS-XML

Accelerator backup produces Status 1 due to: WIN32 13: The data is invalid

One or multiple instances of the following message is observed in Activity Monitor Job Details resulting in a Status 1: 11/25/2014 9:01:03 PM - Error bpbrm(pid=634) from client MyClient: ERR - failure reading file
TECH226852 | 2014-12-09
Technical Solutions | CMS-XML

Media Manager status code 13

Media Manager status code 13
HOWTO104401 | 2014-11-20
How To | CMS-XML

Robot Error status code 13

Message: EMM error Explanation:
HOWTO104775 | 2014-11-20
How To | CMS-XML

Device management status code 13

Message: Error in IPC SHMGET call Explanation:
HOWTO104645 | 2014-11-20
How To | CMS-XML

Device configuration status code 13

Explanation: A request was made to list the device configuration, but an error was encountered while reading from the EMM database. Examine the daemon debug log and system logs for a more detailed message on the error.
HOWTO104559 | 2014-11-20
How To | CMS-XML

NetBackup status code: 13

A network communication problem that occurred on the master server, media server, or one of the clients. An I/O error that occurred during a read from the file system. Read of an incomplete file or a corrupt file.
HOWTO103943 | 2014-11-20
How To | 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
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?