NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

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

11
TECH39254 | 2013-10-23
Technical Solutions | CMS-XML

hp-ux 11.31 Itanium backups fail with BPTM Error "External event caused rewind during write"

NetBackup 7.0.1 is not yet fully compatible with the new structures of the Agile paths on hp-ux 11 .31 Itanium edition. As a result, when NetBackup 7.0.1 is installed as a media server and IBM LTO drives are used with the IBM ATDD driver, on closing out the last backup fragment, the ATDD driver will fail to correctly write the End Of Tape (EOT) marker after the empty backup header.
TECH155113 | 2011-12-09
Technical Solutions | CMS-XML

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

11
TECH43239 | 2008-01-03
Technical Solutions | CMS-XML

Media Manager status code 11

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

NetBackup status code: 11

A system call has failed. This status code is used for a generic system call failure that does not have its own status code .
HOWTO103941 | 2014-11-20
How To | CMS-XML

Robot Error status code 11

Recommended Action: Examine command output, debug logs, and system logs for a more detailed message on the error . See Setting debug logging to a higher level in the Troubleshooting Guide
HOWTO104773 | 2014-11-20
How To | CMS-XML

Device configuration status code 11

Examine command output, debug logs, and system logs for a more detailed message on the error . See Setting debug logging to a higher level in the Troubleshooting Guide Check the tpconfig
HOWTO104558 | 2014-11-20
How To | CMS-XML

VMware backups and restores using NBD or NBDSSL transport may fail with status 11 if the backup or restore takes a very long time

VMware backups and restores using NBD or NBDSSL transport may fail with status 11 if the backup or restore takes a very long time
TECH218010 | 2014-06-03
Technical Solutions | CMS-XML

non-vmware flashbackup-windows backups fail with error 11, and in bpbkar vfm error = 14

non-vmware flashbackup-windows backups fail with error 11 , and in bpbkar vfm error = 14
TECH177367 | 2014-04-08
Technical Solutions | CMS-XML

VMware vStorage backup fails with Status 11 - Error- System Call failed (11)

Detailed Job Status reports: Error- System Call failed (11)
TECH147186 | 2014-03-15
Technical Solutions | CMS-XML

Client with encryption policy attribute is failing the backup with status 49. Job details show status 11: system call failed

Client with encryption policy attribute is failing the backup with status 49. Job details show status 11: system call failed
TECH215265 | 2014-02-22
Technical Solutions | CMS-XML

STATUS CODE: 11 - Backup attempts of a particular client fail with status code 11: system call failed.

14:15:26.404 [9685] 2 db_end_sts: no DONE from db_getreply(): system call failed 14:15:26.405 [9685] 2 db_flistsend: db_end_sts() failed: system call failed ( 11 ) 14:15:26.405 [9685] 16 bpbrm main: db_flistsend failed: system call failed (11)
TECH43310 | 2013-10-23
Technical Solutions | CMS-XML

STATUS CODE: 11 The catalog backup fails with status 11 in the activity monitor or in a "system call failed" pop-up window.

STATUS CODE : 11 The catalog backup fails with status 11 in the activity monitor or in a "system call failed" pop-up window.
TECH27807 | 2013-10-23
Technical Solutions | CMS-XML

VMware Backups may fail with Status code 11 and Status code 13 due to NetBackup I/O related issues

Detail Status :
TECH175713 | 2013-10-14
Technical Solutions | CMS-XML

VMware Full Mapped backup failing with status 13 and bpbkar exiting with status 11 system call failed

VxMS logs indicate that there is a connectivity issue with the SAN disks. In this situation, the disk path is lost and subsequently a SAN I/O error is encountered. The SAN or Appropriate Administrators should be engaged to further isolate the issue or reconfigure the SAN.
TECH167193 | 2013-10-03
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?