NetBackup Enterprise Server Search Results

Knowledge Base Search         Search Tips

Show Me
Information Resources
Most Popular Subjects

Symantec Suggests


Media Manager status code 3

Media Manager status code 3
HOWTO104391 | 2014-11-20
How To | CMS-XML

Robot Error status code 3

Message: Error in getting shared memory Explanation:
HOWTO104765 | 2014-11-20
How To | CMS-XML

Device management status code 3

Message: Error in Sending Operator Message Explanation:
HOWTO104637 | 2014-11-20
How To | CMS-XML

Device configuration status code 3

An attempt to look up the host name for this host failed. 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
HOWTO104553 | 2014-11-20
How To | CMS-XML

NetBackup status code: 3

Examine the progress log or status of the archive on the client to determine if you need to retry the archive after correcting the problem. If the problem is not serious and the files were backed up, you can manually delete the files. To verify which files were backed up, use the NetBackup client-user interface in restore mode and browse the files in the archive.
HOWTO103933 | 2014-11-20
How To | CMS-XML

Accessing Vault Management via Java Console after upgrading NetBackup to version or 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

SQL restore fails with a status 5; dbclient log shows "Error in VxBSAAddToMultiObjectRestoreList: 3."

During a SQL restore, NetBackup fails with a status 5 on the master server. View Status on the SQL server finishes with Error (-1) .
TECH224033 | 2014-08-26
Technical Solutions | CMS-XML

NDMP restore jobs from tape will fail: read_data: unknown ndmp_task 3; EXITING with status 5

13:58:39.883 [13221] 2 ndmpagentsession_close_by_index[0]: Saving ndmpagent session (still needed for ndmp media session, index 0) 13:58:39.883 [13221] 2 read_data: ndmp_task = 3 13:58:39.883 [13221] 16 read_data: unknown ndmp_task 3
TECH205479 | 2013-12-13
Technical Solutions | CMS-XML

Restore to network mapped drive fails with (WIN32 3: The system cannot find the path specified. ) error

Restore to network mapped drive fails with (WIN32 3 : The system cannot find the path specified. ) error
TECH125618 | 2013-11-23
Technical Solutions | CMS-XML

NDMP restore (image from 7.0.1) fails with status 91 with NetBackup

An emergency engineering binary (EEB) for ETrack 2927983 was provided for NetBackup version 7.5.0. 3 . Then edit the /usr/openv/netbackup/bp.conf file to add this line to enable a restore from these images:
TECH205660 | 2013-10-29
Technical Solutions | CMS-XML

Unable to restore sybase database,show error information:"Backup Server Internal Error: Unable to get current date and time. Internal error."

2 -SERV sx-udbmgt -CLIENT sxdx-sippush-as 3 go Backup Server session id is: 5. Use this value when executing the
TECH209125 | 2013-10-22
Technical Solutions | CMS-XML

STATUS CODE: 103 After upgrading from NetBackup 4.5 Feature Pack 3 to NetBackup Feature Pack 6, Lotus Notes backups begin to fail with status code 103

Overview: After upgrading from NetBackup (tm) 4.5 FP3 to NetBackup FP6, Lotus Notes backups begin to fail with status code 103, error occurred during initialization, check configuration file. Troubleshooting:
TECH39434 | 2013-10-23
Technical Solutions | CMS-XML

BUG REPORT: A NetBackup for Lotus Notes database restore failed with Status Code 5 after installing Release Update 6.5.3

The transaction log recovery phase of a Lotus Notes restore, which occurs following the successful restore of a logged database, may fail after upgrading to NetBackup Release Update 6.5. 3 . If the client is reverted to a version of NetBackup earlier than 6.5.3, the restore and transaction log recovery are successful. The key messages identifying this issue will be written to the client s TAR log during the course of the restore:
TECH68775 | 2013-10-24
Technical Solutions | CMS-XML

Status code 174 is reported during clean up & Optimized duplications after applying Netbackup - exit status 174 on image cleanup jobs

00:07:09.910 [11775] 2 send_end_repl_marker: storage server type is not PureDisk 00:07:09.910 [11775] 2 delete_opt_dup_markers: Deleting the opt_dup markers 00:07:09.910 [11775] 16 Received error (2060022) from server
TECH179483 | 2013-10-24
Technical Solutions | CMS-XML

CORBA connection failures and status 25 after upgrading media server to or 2.5.3

Some media servers that are configured to restrict the source interfaces suffer CORBA connection failures after upgrading to NetBackup All jobs using that media server may fail with status 25. Affects NetBackup media servers, including 2.5.3 appliances, that are still using outdated Preferred Network settings in specific network configurations.
TECH208869 | 2013-09-24
Technical Solutions | CMS-XML

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?