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

Shadow Copy Components / System State backup fails with status code 13: file read failed

14:33:49.015 [4968.2376] 2 onlfi_vfms_logf: INF - snapshot services: winfsys:Mon Jan 26 2015 14:33:49.015000 WinFsysFiCoordinator::claim, GetVolumeInformationW,Name:[ System State:\ ], fsname: [], Status : [0]
TECH227864 | 2015-02-18
Technical Solutions | CMS-XML

RMAN backup to sbt_tape is much slower than backup to DISK, may fail with status 13

RMAN backup to sbt_tape is much slower than backup to DISK, may fail with status 13
TECH130209 | 2015-02-03
Technical Solutions | CMS-XML

Backup fails with status 13 after bpbrm reports; socket read failed: errno = 62 - Timer expired

Backup fails with status 13 after bpbrm reports; socket read failed: errno = 62 - Timer expired
TECH71821 | 2015-02-03
Technical Solutions | CMS-XML

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

and Job Details show the following error : 15:24:07.908 [31147] 2 bpbrm mm_sig: received ready signal from media manager
TECH141299 | 2015-02-03
Technical Solutions | CMS-XML

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

for the child or application backup job shows that bpbrm timed out while awaiting progress updates from the client: 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 | 2015-02-03
Technical Solutions | CMS-XML

STATUS CODE 13: Backups fail with Status Code 13 "file read failed", indicating that a read of a file or socket has failed. Winsock errors 10054 and 10053 may also be seen in the bpbkar log on the client.

STATUS CODE 13: Backups fail with Status Code 13 "file read failed", indicating that a read of a file or socket has failed. Winsock errors 10054 and 10053 may also be seen in the bpbkar log on the client.
TECH37372 | 2015-02-04
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
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?