NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


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

Symantec Suggests

  Next 

OpsCenter Error Messages added in 7.5

OpsCenter Error Messages added in 7.5 Following table lists OpsCenter error messages with the possible root cause of the problem and details about the solutions that can be applied. Table: OpsCenter Erros codes with Description
HOWTO71918 | 2012-02-08
How To | CMS-XML

NetBackup 7.6.1 Status Code Reference Guide

NetBackup 7 .6.1 Status Code Reference Guide
DOC7674 | 2014-11-19
Documentation | 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

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

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

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

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-08-18
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

After upgrading to 7.6.0.1/2.6.0.1, VMware backups via SAN may fail with Status 130 due to bpbkar core dump

Detail Status : 17-1-2014 21:42:47 - Info bpbkar(pid=61092) INF - Transport Type = san 17-1-2014 21:51:51 - Error bpbrm(pid=61074) from client VMCLIENT: ** (process:61092): WARNING **: MXUserDumpExclLock: Exclusive lock @ 0x96a590
TECH214512 | 2014-08-12
Technical Solutions | CMS-XML

Upgrade to 7.6.0.1 failing with: SQL Anywhere Error -195: Column 'displayOrder' in table 'report_tablecolumn' cannot be NULL

When upgrading NetBackup OpsCenter from 7 .5.0.6 to 7 .6.0.1, the database upgrade failed with this message: SQL Anywhere Error -195: Column displayOrder in table report_tablecolumn cannot be NULL
TECH216541 | 2014-07-15
Technical Solutions | CMS-XML

Unable to launch NetBackup 7.x Java GUI console on Windows 2008 Server, Windows 7, receiving popup error: 521 & 520

=================================== netbackup-java Initialization Error : nb-java configuration file, C:\\Program Files\\Veritas\\java\\nbjconf, does not exist.
TECH214044 | 2014-07-15
Technical Solutions | CMS-XML

STATUS CODE: 50 - Unable to label the new media in NetBackup (tm) 7.x

NetBackup 7 .0 Windows Server 2008 R2
TECH196071 | 2014-06-20
Technical Solutions | CMS-XML

"Error occurred while connecting to the OpsCenter Server. Please ensure that the server is running." After upgrading to 7.0.1

" Error occurred while connecting to the OpsCenter Server. Please ensure that the server is running." After upgrading to 7.0.1
TECH140359 | 2014-05-01
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?