NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


Show Me
Status
Information Resources
Product(s)
Most Popular Subjects
Downloads
   

Symantec Suggests

  Next 

NetBackup 7.6.1 Status Code Reference Guide

NetBackup 7 .6.1 Status Code Reference Guide
DOC7674 | 2014-11-19
Documentation | CMS-XML

Robot Error status code 7

Robot Error status code 7
HOWTO104769 | 2014-11-20
How To | CMS-XML

Media Manager status code 7

Media Manager status code 7
HOWTO104395 | 2014-11-20
How To | CMS-XML

Device management status code 7

Message: Error in Sending User Message Explanation:
HOWTO104641 | 2014-11-20
How To | CMS-XML

NetBackup status code: 7

Explanation: Errors caused the user archive to fail. Recommended Action:
HOWTO103937 | 2014-11-20
How To | CMS-XML

Device configuration status code 7

A request was made to add or change the SCSI port number for a robot, but the SCSI port number provided was not valid. 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
HOWTO104554 | 2014-11-20
How To | CMS-XML

About Top 7 Job Error Log Summary

The table that appears in the section lists the top seven exit status codes responsible for maximum job failure. The table also lists the number of failed jobs for each exit status in the selected time frame. Note that the failed jobs that are shown in the Failed Job Count
HOWTO102993 | 2014-11-18
How To | CMS-XML

In NetBackup 7.6.0.x, P2V conversion jobs using Bare Metal Restore (BMR) may fail with Status 7 when the VMWare dataStore is incorrectly selected.

In NetBackup 7 .6.0.x, P2V conversion jobs using Bare Metal Restore (BMR) may fail with Status 7 when the VMWare dataStore is incorrectly selected.
TECH222564 | 2014-11-10
Technical Solutions | CMS-XML

MS SQL and other XBSA Backups fail with status code 239 reported after applying the NetBackup 7.5.0.7 maintenance release.

NetBackup for Microsoft SQL Server backups fail with status code 239 (the specified client does not exist in the specified policy ) reported after applying the NetBackup 7.5.0.7 maintenance release. Other XBSA based backups such as DB2 and Oracle RMAN have also been reported to fail for the same reason.
TECH215866 | 2014-11-11
Technical Solutions | CMS-XML

Accessing Vault Management via Java Console after upgrading NetBackup to version 7.6.0.2 or 7.6.0.3 generates error message “Access Denied. You do not have permission to perform this operation or access this resource.”

An error message similar to the following may appear Java GUI log located in install_path Veritas\NetBackup\logs\user_ops\nbjlogs [03-07-2014 16:34:05:499] pbxiop:INFO: createSocket - Trying to connect to nbmaster:1556:nbvault [03-07-2014 16:34:05:499] pbxiop:INFO: Connected to exchange at:nbmaster:1556:nbvault
TECH218104 | 2014-11-10
Technical Solutions | CMS-XML

Trying to install NetBackup 7.x installation on Windows 2008 R2 failed with error message

Error :1719, the Windows Installer service could not be accessed
TECH216778 | 2014-11-13
Technical Solutions | CMS-XML

NDMP backup behavior change in 7.6 causing backup failures with status code 25.

During the backup job, the message from the filer is displayed Active NDMP backup/restore streams reach the maximum concurrent streams supported 8. No more NDMP sessions can be started. Wait current backup/restore sessions finish before start new ones. and the job immediately fails with a status code of 25.
TECH225572 | 2014-11-11
Technical Solutions | CMS-XML

BUG REPORT: NetBackup SQL or Oracle database agents, or user initiated backups are failing with Status Code 41 after upgrading to NetBackup 6.5 or 7.0.

(018378e8) xlatemsg (translated) failed with status =1, jobid=61317(../JMProgLogComm.cpp:547) The dbclient log shows an error after client_read_timeout expires without the expected update to the comm file.
TECH58164 | 2014-10-20
Technical Solutions | CMS-XML

PureDisk / MSDP (Media Server Deduplication Pool) backups fail with STATUS 87 or STATUS 14 after the Storage Server has been upgraded to NetBackup 7.6

If an MSDP disk pool and storage server has been upgraded to NetBackup 7.6, but the clients backing up to the MSDP disk pool remain at an earlier version than NetBackup 7.6, problems can be seen where backups fail with STATUS 87 or STATUS 14 . On examination, the failing backups use client-side deduplication
TECH214856 | 2014-08-29
Technical Solutions | CMS-XML

After upgrading to NetBackup 7.5 (through 7.5.0.6) or 7.6, the Activity Monitor displays either job status and details such as queued or active job even though details shows job has completed.

) is included in the following releases: NetBackup 7 .5 Maintenance Release 7 ( 7 .5.0. 7 ) NetBackup 7.6 Maintenance Release 2 (7.6.0.2)
TECH210574 | 2014-08-12
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?