NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 111

Media Manager status code 111
HOWTO104481 | 2014-11-20
How To | CMS-XML

NetBackup status code: 111

NetBackup status code : 111
HOWTO104036 | 2014-11-20
How To | CMS-XML

NetBackup status code 111: No entry was found in the server list

111
TECH58596 | 2009-01-12
Technical Solutions | CMS-XML

About NetBackup Search status codes and log files

51216 111 install_path
HOWTO85176 | 2013-09-27
How To | CMS-XML

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

(top down: one, two,.. eleven, twelve,.. ending in thirty two) 111 1111 1112 2222 2222 2333 1234 5678 9012 3456 7890 1234 5678 9012
TECH48603 | 2010-01-29
Technical Solutions | CMS-XML

DOCUMENTATION: How to troubleshoot and correct problems with media servers when the status changes in the Media Servers area of the NetBackup Administration GUI.

/usr/openv/netbackup/bin/vxlogcfg -a -p 51216 -o 156 -s DiagnosticLevel=6 -s DebugLevel=6 /usr/openv/netbackup/bin/vxlogcfg -a -p 51216 -o 111 -s DiagnosticLevel=6 -s DebugLevel=6 /usr/openv/netbackup/bin/vxlogcfg -a -p 51216 -o 137 -s DiagnosticLevel=6 -s DebugLevel=6
TECH69625 | 2009-01-15
Technical Solutions | CMS-XML

GENERAL ERROR: The message "tar_base::v_vtarmsgw: TRV - object not found for file system backup:" occurs in the client's bpbkar log.

does. 8:48:28. 111 AM: [388.2748] 2 tar_backup::backup_create: TAR - backup filename = D:\Backup\steve.sjc 8:48:28.111 AM: [388.2748] 2 tar_backup::backup_create: TAR - backup filename = D:\Backup\steve.doc
TECH39188 | 2014-12-15
Technical Solutions | CMS-XML

NetBackup status code: 904

(originator ID 111 ). All unified logging is written to /usr/openv/logs
HOWTO104382 | 2014-11-20
How To | CMS-XML

NetBackup status code: 403

For detailed troubleshooting information, create the admin debug log directory and retry the operation. Check the resulting debug logs. Additional debug information can be found in the log for nbemm (originator ID 111 ), which uses unified logging.
HOWTO104267 | 2014-11-20
How To | CMS-XML

NetBackup status code: 401

For detailed troubleshooting information, create the admin debug log directory and retry the operation. Check the resulting debug logs. Additional debug information can be found in the log for nbemm (originator ID 111 ), which uses unified logging.
HOWTO104265 | 2014-11-20
How To | CMS-XML

NetBackup status code: 400

(originator ID 111 ) which uses unified logging. Click here to view technical notes and other information in the Symantec Knowledge Base about this status code.
HOWTO104264 | 2014-11-20
How To | CMS-XML

NetBackup status code: 408

For detailed troubleshooting information, create the admin debug log directory and retry the operation. Check the resulting debug logs. Additional debug information can be found in the log for nbemm (originator IDs 111 and 143), which uses unified logging.
HOWTO104272 | 2014-11-20
How To | CMS-XML

NetBackup status code: 405

For detailed troubleshooting information, create the admin debug log directory and retry the operation. Check the resulting debug logs. Additional debug information can be found in the log for nbemm (originator IDs 111 and 143), which uses unified logging.
HOWTO104269 | 2014-11-20
How To | CMS-XML

NetBackup status code: 407

(originator IDs 111 and 143), which uses unified logging. Click here to view technical notes and other information in the Symantec Knowledge Base about this status code.
HOWTO104271 | 2014-11-20
How To | CMS-XML

NetBackup status code: 402

For detailed troubleshooting information, create the admin debug log directory and retry the operation. Check the resulting debug logs. Additional debug information can be found in the log for nbemm (originator ID 111 ), which uses unified logging.
HOWTO104266 | 2014-11-20
How To | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?