NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

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

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.
HOWTO90902 | 2013-10-02
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.
HOWTO90447 | 2013-10-02
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
HOWTO91061 | 2013-10-02
How To | CMS-XML

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.
HOWTO51251 | 2012-11-19
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.
HOWTO50795 | 2012-11-19
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
HOWTO51410 | 2012-11-19
How To | CMS-XML

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.
HOWTO35361 | 2010-10-29
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.
HOWTO34904 | 2010-10-29
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 . Verify that all Media Manager binaries are at a compatible version level.
HOWTO35520 | 2010-10-29
How To | 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/libstspiDataDomain.so:stspi_read_image 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
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?