NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Device configuration status code 8

Device configuration status code 8
HOWTO104555 | 2014-11-20
How To | CMS-XML

Device management status code 8

Message: Error in Receiving User Message Explanation:
HOWTO104642 | 2014-11-20
How To | CMS-XML

NetBackup status code: 8

Message: unable to determine the status of rbak Explanation:
HOWTO103938 | 2014-11-20
How To | CMS-XML

Robot Error status code 8

A robotic daemon/process was unable to allocate memory. This error occurs when insufficient system memory is available. This error could result from the system being overloaded with too many processes and from insufficient physical and virtual memory.
HOWTO104770 | 2014-11-20
How To | CMS-XML

Media Manager status code 8

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 Ensure that the media ID, where requested, is not blank.
HOWTO104396 | 2014-11-20
How To | CMS-XML

Novell backups fail with status 58 and "<8> bpcd::bpcd_wait_for_request_state: WRN - bad request token (13312)" in the bpcd log.

8 bpcd::bpcd_wait_for_request_state: WRN - bad request token (13312)
TECH34333 | 2013-10-23
Technical Solutions | CMS-XML

STATUS 130, Backups of a FreeBSD 8.2 and MacOS 10 clients fail with error code 130

FreeBSD 8 .2 NetBackup: netbackup-freebsd6.0 7.5 Mac OS X 10.6.x
TECH195922 | 2014-02-18
Technical Solutions | CMS-XML

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

(Substitute the proper non-rewind device path if it is not nrst0a as in this example). Note: For cluster-mode NetApp, refer to the NetApp Document Clustered Data ONTAP 8 .2 Command Map for 7-mode Administrators as the dump command does not work for c-mode volumes. Excerpt:
TECH56492 | 2015-01-13
Technical Solutions | CMS-XML

Snapshot error encountered (status code 156)

Event Type: Error Event Source: VSS Event Category: None Event ID: 12302 Date: 1/ 8 /2009 Time: 1:36:21 AM User: N/A Computer: ARTICTALEVM8 Description: Volume Shadow Copy Service error : An internal inconsistency was detected in trying to contact shadow copy service writers. Please check to see that the Event Service and Volume Shadow Copy Service are operating properly.
HOWTO70792 | 2014-12-13
How To | CMS-XML

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

Observation of the bpdm log shows that the net_buffer_sz file is in place, but the requested size is not being honored by the operating system even though success (0) is returned to the application. 23682/1: 1.5405 open( /usr/openv/netbackup/net_buffer_sz , o_rdonly) = 8 23682/1: 1.5413 read(8, 2 6 2 1 4 4\n , 8192) = 7
TECH76201 | 2014-10-16
Technical Solutions | CMS-XML

How to enable debug logging on a NetApp NDMP device when NDMP backup fails with Status Code 99 - DUMP: could not create "backup" snapshot : No space left on device.

DUMP: DUMP IS ABORTED 8 . Review the available disk space on volume /vol/vol1. Note:
TECH68849 | 2014-01-20
Technical Solutions | CMS-XML

GENERAL ERROR: Backups and restores may fail, or troubleshooting may be hindered if the NetBackup log directories are not readable and writeable by user and application processes.

8 delete_old_files: WRN - Cannot unlink /usr/openv/netbackup/logs/user_ops/dbext/logs/9999.0.1234567890. Errno = 13: Permission denied
TECH52446 | 2013-11-21
Technical Solutions | CMS-XML

NetBackup status code 1800

invalid client list For Enterprise vault-type policies, please verify that multiple clients are not added to the list of clients if you specify any of the following Enterprise Vault 8 .0 directives in the backup selection: ev_index_location=
HOWTO92212 | 2013-10-03
How To | CMS-XML

NetBackup status code 2

For Enterprise Vault 8 .0, quiescence can fail if the Enterprise Vault component (Vault store or Index location) or its parent component (such as, vault store group or site) is already quiesced. The backups fail with a status 2. You should clear the backup mode and attempt to run the backup again.
HOWTO92210 | 2013-10-03
How To | CMS-XML

NetBackup status code: 23 - How to troubleshoot backups that fail with status 23 "socket read failed".

12:44:38.619 [4804.5184] 2 bpcd main: setup_sockopts complete 12:44:43.134 [4804.5184] 8 bpcd peer_hostname: gethostbyaddr failed : The requested name is valid, but no data of the requested type was found. (0)
TECH56079 | 2013-04-24
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?