NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 143

NetBackup status code : 143
HOWTO104064 | 2014-11-20
How To | CMS-XML

Media Manager status code 143

Media Manager status code 143
HOWTO104508 | 2014-11-20
How To | CMS-XML

NetBackup (tm) Block Level Incremental backups fail with "exit status 143."

143
TECH35195 | 2013-10-24
Technical Solutions | CMS-XML

NetBackup restore and backup status codes

Status Code 143 . Invalid command protocol.
HOWTO89629 | 2013-10-02
How To | CMS-XML

NetBackup status code: 2021

The mds unified logging files (OID 143 ) from the master server at debug level 2. The nbrb
HOWTO104849 | 2014-11-20
How To | CMS-XML

NetBackup status code: 2029

The mds unified logging files (OID 143 ) from the master server at debug level 2. The nbrb
HOWTO104852 | 2014-11-20
How To | CMS-XML

NetBackup status code: 2016

The mds unified logging files (OID 143 ) from the master server at debug level 2. The nbrb
HOWTO104844 | 2014-11-20
How To | CMS-XML

NetBackup status code: 2015

The mds unified logging files (OID 143 ) from the master server at debug level 2. The nbrb
HOWTO104843 | 2014-11-20
How To | CMS-XML

NetBackup status code: 2013

The mds unified logging files (OID 143 ) from the master server at debug level 2. The nbrb
HOWTO104841 | 2014-11-20
How To | CMS-XML

NetBackup status code: 2003

Check the following logs: The MDS unified logging files (OID 143 ) from the master server at debug level 2. The nbrb
HOWTO104831 | 2014-11-20
How To | CMS-XML

NetBackup status code: 2025

The mds unified logging files (OID 143 ) from the master server at debug level 2. The nbrb
HOWTO104857 | 2014-11-20
How To | CMS-XML

NetBackup status code: 2024

The mds unified logging files (OID 143 ) from the master server at debug level 2. The nbrb
HOWTO104856 | 2014-11-20
How To | CMS-XML

NetBackup status code: 2110

The policy that you use to run the job may indicate which server the job requires. If not, find the server that the job is looking for by setting the MDS VxUL logging (OID 143 ) to debug level 2 and retry the job. The MDS log usually indicates which hostname is causing the problem.
HOWTO105302 | 2014-11-20
How To | CMS-XML

NetBackup status code: 2026

The mds unified logging files (OID 143 ) from the master server at debug level 2. The nbrb
HOWTO104858 | 2014-11-20
How To | CMS-XML

NetBackup status code: 2022

The mds unified logging files (OID 143 ) from the master server at debug level 2. The nbrb
HOWTO104854 | 2014-11-20
How To | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?