NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Device configuration status code 15

Device configuration status code 15
HOWTO104561 | 2014-11-20
How To | CMS-XML

Media Manager status code 15

Exceeds the allowed length of a volume group name 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
HOWTO104403 | 2014-11-20
How To | CMS-XML

Device management status code 15

An attempt was made to mount media on a drive or to reserve a shared drive that was logically configured to the DOWN state. 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
HOWTO104647 | 2014-11-20
How To | CMS-XML

NetBackup status code: 15

Check the NetBackup Problems report for clues on where and why the problem occurred. For detailed troubleshooting information, create a debug log directory for the process that returned this status code . Then retry the operation and check the resulting debug log.
HOWTO103945 | 2014-11-20
How To | CMS-XML

GENERAL ERROR: What does the error "<16> bpcd main: authentication failed: 15" in the bpcd log indicate?

exit status 54: timed out connecting to client and/or 16 bpcd main: authentication failed: 15
TECH33037 | 2013-10-23
Technical Solutions | CMS-XML

Oracle RMAN application backup job hangs and the automatic job fails with status 6 at 15 minutes after the data transfer completes.

If the child process does not exit promptly, and thereby close it s copy of the file descriptors, those sockets will remain up after the dbclient has closed it s copy of the same file descriptors. As a result, the NetBackup media server will be unaware that the data transfer has completed. This will delay server status being written to the comm file and the dbclient will timeout in 900 seconds.
TECH73130 | 2013-03-27
Technical Solutions | CMS-XML

GENERAL ERROR: VMware backups fail with error 11, and in bpbkar vfm error = 14 or vfm error = 15

tar_base::v_vtarmsgw: INF - EXIT STATUS 11: system call failed
TECH128651 | 2010-01-23
Technical Solutions | CMS-XML

NetBackup Status Code 15: file close failed

and why the problem occurred. For detailed troubleshooting information, create a debug log directory for the process that returned this status code . Then retry the operation and check the resulting debug log.
TECH57164 | 2009-01-28
Technical Solutions | CMS-XML

BUG REPORT: Oracle restores which use multiple channels fail with a timeout error if resources are not allocated within 15 minutes of the restore starting.

A Veritas NetBackup (tm) multi-channel Oracle restore fails after 900 seconds ( 15 minutes). The restore fails because NetBackup is unable to allocate all necessary resources for the restore. Attempts to restore the same backup using single channel is successful.
TECH49865 | 2006-01-18
Technical Solutions | CMS-XML

Status Code 40 after Backup running for 15 Minutes - Everytime | Symantec Connect

Refer to this technote of how to configure the settings on AIX: You must configure the tcp keepalive parameter to send keep alive packages faster than 15 minutes. Assumption is the mother of all mess ups.
Connect Forums | HTML

Backup fails with status 24 after the network stops delivering data to the media server.

10.43.2.62.13724 198.235.125.52.42318 49680 0 49680 0 ESTABLISHED Friday October 9 05: 15 :08 GMT 2009 10.43.2.62.13724 198.235.125.52.42317 1
TECH76201 | 2014-10-16
Technical Solutions | CMS-XML

How to troubleshoot NDMP Backups failures when status code 99 (or other NDMP backup failure) is reported. Includes logging instructions.

15 . Cut and paste the Job Details for the job in the Activity Monitor during the backup attempt. Send that to Symantec Support along with the nbsu output file and the bppllist output.
TECH56492 | 2014-10-01
Technical Solutions | CMS-XML

in-depth Troubleshooting Guide for Exit Status Code 50

A Status 50 error can be seen with Domino Server 6.0.2 and later on a Linux Platform. Lotus Support has acknowledged a new variable in the Lotus C API called backup_timeout. When the backup of a (usually large) database exceeds the default backup_timeout setting of 15 minutes, the API will return a Status 50 and log the following in the bpbkar log:
TECH43182 | 2013-10-17
Technical Solutions | CMS-XML

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

00039383: file 16: record 1: size 1024: NBU TIR header backup_id system_1285156950: frag -1: file 15 : copy 1 expiration 1285761750: retention 0: block_size 262144
TECH155113 | 2011-12-09
Technical Solutions | CMS-XML

DOCUMENATION: An breakdown of TapeAlert flags to assist with troubleshooting TapeAlert errors

07/06/06 11:18:41 a26820 2 tape_alert lto2-1 0x30001000 0x02000000 07/10/06 15 :47:29 A26863 2 write_error lto2-1 07/10/06 15:47:40 A26863 2 tape_alert lto2-1 0x30001000 0x02000000
TECH48603 | 2010-01-29
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?