NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 136

Media Manager status code 136
HOWTO90998 | 2013-10-02
How To | CMS-XML

NetBackup status code: 136

NetBackup status code : 136
HOWTO90557 | 2013-10-02
How To | CMS-XML

Media Manager status code 136

Media Manager status code 136
HOWTO51347 | 2012-11-19
How To | CMS-XML

NetBackup status code: 136

NetBackup status code : 136
HOWTO50905 | 2012-11-19
How To | CMS-XML

NetBackup status code: 136

NetBackup status code : 136
HOWTO35015 | 2010-10-29
How To | CMS-XML

Media Manager status code: 136

Media Manager status code : 136
HOWTO35457 | 2010-10-29
How To | CMS-XML

GENERAL ERROR: The "nbemmcmd" command returns "invalid host name (136)" when trying to add hosts to the enterprise media manager (EMM) server.

Overview: When using the VERITAS NetBackup (tm) nbemmcmd command to add hosts to the EMM server, the following is returned: invalid host name ( 136 )
TECH44259 | 2006-01-14
Technical Solutions | CMS-XML

In the VERITAS NetBackup (tm) 5.0 for UNIX and Windows Troubleshooting Guide, the recommended action for Status code 135 is incorrect.

The manual incorrectly shows the same recommended action for both status code 135 and 136 . The correct recommended action for a status 135 is: Retry the operation as a root user (administrator on Windows) on the master server. Also see status code 131.
TECH31835 | 2005-01-29
Technical Solutions | CMS-XML

We are getting the Errors:When we click on Device Monitor error "invalid host name 136" | Symantec Connect

01:04:27.262 [19406] <16> emmlib_listmachineconfig: (0) failed, emmError = 2000000, nbError = 0 01:04:27.263 [19406] <16> nbemmcmd: (-) Translating emm_error_machinenotexist(2000000) to 136 in the Media context 01:04:27.292 [19406] <16> nbemmcmd: (-) Translating emm_error_machinenotexist(2000000) to 136 in the Media context
Connect Forums | HTML

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

client003# cksum keyfile 181077776 136 keyfile WORKING CLIENT --
TECH215265 | 2014-02-22
Technical Solutions | CMS-XML

Image Cleanup getting status 191 or invalid command parameter(20)

14:10:27.806 [849325] 4 delete_expired_backups: deleted 4 expired records, compressed 0, tir removed 0, deleted 0 expired copies 14:10:28. 136 [849325] 16 delete_expired_backups: OVsystem(/usr/openv/netbackup/bin/admincmd/nbdelete -allvolumes -jobid 10957) failed (191) admin log for status 191
TECH65084 | 2014-01-20
Technical Solutions | CMS-XML

While running backups in PureDisk, getting error status 129 and status 83.

Space used within containers : 537737343476 bytes (500.81GB) Space available within containers: 146870350185 bytes ( 136 .78GB) Space needs compaction : 121658193411 bytes (113.30gb)
TECH168898 | 2013-12-04
Technical Solutions | CMS-XML

nbfdrv64 dies on new FT media servers, erroring with "InitPipe returned 983081"

pci1077,2422.1077.135 pci1077,2422.1077. 136 pci1077,2422.1077.13A
TECH144936 | 2013-10-16
Technical Solutions | CMS-XML

NetBackup status code: 1

No images were found to synthesize (status code = 607). TIR information has been pruned from component images ( status code = 136 ). Image format is unsupported (status code = 79).
HOWTO90430 | 2013-10-02
How To | CMS-XML

NetBackup Replication Director SnapMirror replications complete but hang in a post-processing stage lasting for up to 24 hours before a Status 0 is returned, or fail with a Status 174 or 34.

Policy Name: NetBackup Mirror, then back up Policy Id: 136 Started Timestamp: 12 Jul 2013 06:26:40
TECH208545 | 2013-07-15
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?