NetBackup Enterprise Server Search Results

Knowledge Base Search         Search Tips


Symantec Suggests


Media Manager status code 18

Allocation of system memory failed. This error occurs when insufficient system memory is available. The system may have too little physical and virtual memory to handle the current load of processes.
HOWTO104405 | 2014-11-20
How To | CMS-XML

NetBackup status code: 18

Check the NetBackup Problems report for clues on why the failure 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.
HOWTO103948 | 2014-11-20
How To | CMS-XML

Device configuration status code 18

Check the device configuration for configured robots, and specify the correct robot type applicable for the device configuration information being updated. 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
HOWTO104564 | 2014-11-20
How To | CMS-XML

STATUS CODE 42: Veritas NetBackup (tm) NDMP backups fail while backing up directories/volumes with large number of files with the error message "Error ndmpagent (pid=8998) connection 0x081871d8 ndmp_message_process_one failed, status = 18 (ndmp_xdr_decode_err)" and a NetBackup Status Code 42, network read failed.

Overview : Veritas NetBackup (tm) Network Data Management Protocol (NDMP) backups fail after running for a few hours with the error message listed below, in the Exact Error Message field and also generates and a NetBackup Status Code 42: network read failed. Please note: ndmp_xdr_decode_err
TECH47412 | 2014-06-13
Technical Solutions | CMS-XML

Vmware Backups Fail with Status 58 Or " connect failed STATUS (18) connect_failed " Or "status: FAILED, (44) connect_timeout; system: (10061) No connection could be made because the target machine actively refused it" Or "getsockopt so_error returned 10061 0x274d"

Job Details shows error : 5/07/2012 11:20:04 a.m. - Info nbjm(pid=3716) starting backup job (jobid=17870) for client NBclient, policy vadp_7503_nbclient_tape, schedule full-daily 5/07/2012 11:20:04 a.m. - estimated 0 Kbytes needed
TECH192643 | 2014-01-08
Technical Solutions | CMS-XML

NDMP restore from disk storage unit on DataDomain fails with "ndmp_message_process_one failed, status = 18 (ndmp_xdr_decode_err)"

13:14:21.040 [805] 2 NdmpSession: [27] Replying error = 0 13:14:21.040 [805] 2 mnstore03: /usr/openv/lib/ost-plugins/ image handle =0x982c950 fd =0 length =262144 offset =15074816
TECH124645 | 2010-01-22
Technical Solutions | CMS-XML

NetBackup status code: 18 pipe close failed

: Check the NetBackup Problems report for clues on why the failure 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.
TECH57652 | 2009-01-22
Technical Solutions | CMS-XML

GENERAL ERROR: During an NDMP restore, error 18 (ndmp_xdr_decode_err) is displayed.

GENERAL ERROR : During an NDMP restore, error 18 (ndmp_xdr_decode_err) is displayed.
TECH58371 | 2008-01-25
Technical Solutions | CMS-XML

THIRD PARTY: Multiple client backups exit with status 24 when the network is heavily loaded.

... 00:45: 18 .739 [11553] 2 bpbrm Exit: client backup EXIT STATUS 24: socket write failed Workaround #1:
TECH56950 | 2014-05-01
Technical Solutions | CMS-XML

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

00039393: file 17: eof after 1 records: 1024 bytes 00039394: file 18 : eof after 0 records: 0 bytes REQUIRED eot
TECH155113 | 2011-12-09
Technical Solutions | CMS-XML

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

The format for the log file entries is: date time media id drive index TapeAlert error 07/06/06 11: 18 :35 a26820 2 write_error lto2-1 07/06/06 11:18:41 a26820 2 tape_alert lto2-1 0x30001000 0x02000000
TECH48603 | 2010-01-29
Technical Solutions | CMS-XML

Accelerator job fails with status: 24: socket write failed

Error captured in Activity Monitor Job Details: 12/16/2014 2: 18 :12 PM - end writing 12/16/2014 2:18:17 PM - Info bpbrm(pid=7473) nbclient2.nbulab.symc is the host to backup data from
TECH227138 | 2014-12-16
Technical Solutions | CMS-XML

NetBackup backups intermittently fail with status 83 when writing to a Media Server Deduplication storage unit hosted on Windows 2012 R2 with a "Teredo Tunneling pseudo-interface" and the Windows firewall disabled.

will show bptm exiting with status 83. The client process may exit with a status 83, status 6, or other status depending on client type and exactly when in the process flow the failure occurs. 06/30/2014 18 :38:54 - Critical bptm (pid=5184) sts_get_lsu_prop_byname on LSU PureDiskVolume failed: 2060038 no such device 06/30/2014 18:38:54 - Critical bptm (pid=5184) Invalid storage device: PureDiskVolume no such device
TECH223550 | 2014-12-05
Technical Solutions | CMS-XML

SLP window close behavior causes status 157 174 191

18 :00:14.377 [8496.10056] dupreadline: read: EXIT STATUS 157
TECH226454 | 2014-11-24
Technical Solutions | CMS-XML

MS SQL and other XBSA Backups fail with status code 239 reported after applying the NetBackup maintenance release.

is 300 seconds. Backup started Tue Feb 18 18 :39:38 2014 nbpem
TECH215866 | 2014-11-11
Technical Solutions | CMS-XML

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?