Home > Error Code > Veritas Netbackup Error Codes List

Veritas Netbackup Error Codes List

Contents

Status Code 273 ==================== invalid job id This error can occur in either of the following situations: * The specified job is not an active Vault job * The specified active Status Code 170 ==================== third party copy backup failure Usually indicates a problem with the 3pc. If the preceding steps do not resolve this problem, see "Resolving Network Communication Problems" on page 21. 61  62  63  64  65  66  67  68  69 Top Status Code: 60 Status Code 174 ==================== media manager - system error occurred An abnormal condition caused a tape manager (bptm) or disk manager (bpdm) failure. weblink

Status Code 196 ==================== client backup was not attempted because backup window closed A backup or an archive operation that the backup scheduler queued was not attempted because the backup window The getservbyname()function uses the name of the service to find a service entry in the services file. (Or NIS services map on UNIX if it is configured.) Status Code 20 ==================== The SYSTEM account cannot access network drives. Status Code 73 ==================== bpstart_notify failed The bpstart_notify script returned a nonzero exit code. http://backup.technion.ac.il/codes

Veritas Netbackup Error Codes List

b. Example: Download also the "Veritas NetBackup Troubleshooting Guide for UNIX, Linux, and Windows" Share this:EmailPrintLinkedInFacebookTwitterGoogleTumblrPinterestLike this:Like Loading... Status Code 56 ==================== client's network is unreachable An error reported that the client could not reach the host (WSAENETUNREACH on Windows or ENETUNREACH on UNIX) when the client performed a Recommended Action: 1.

Verify that the bpcd and bprd port numbers in the %SystemRoot%\system32\drivers\etc\services file on the server matches the setting on the client. Status Code 213 ==================== no storage units available for use The NetBackup resource broker (nbrb) did not find any storage units available for use. Status Code 257 ==================== failed to get job data This error can indicate either of the following: * Vault failed to get job data because of a broken connection with the Netbackup 7.7 Status Codes If you cannot determine the cause from the Problems report, create activity log directories for the processes that returned this status code.

If so, kill it and try again. Status Code 160 ==================== authentication failed NetBackup encounters a problem when two systems attempt to authenticate one another. On the other side of the connection, the other system is not configured to use VxSS. Status Code 207 ==================== error obtaining date of last backup for client When nbpem tries to obtain the date of the last backup for a particular client, policy, and schedule combination,

The company plans to integrate ... Veritas Netbackup Error Codes Pdf Status Code 258 ==================== Vault duplication was aborted by administrator request The administrator initiated an abort request on the active vault duplication job. These clients can handle only one NetBackup job at a time. 4. Status Code 34 ==================== failed waiting for child process A NetBackup process encountered a failure while waiting for a child process to complete.

  1. Load More View All Problem solve PRO+ Content Find more PRO+ content and other member only offers, here.
  2. Get Symantec's explanation of how to fix this issue.
  3. file or the mover.conf file. (For detailed causes, see recommended actions.) For more information on these files, refer to the NetBackup Snapshot Client Configuration online document.
  4. Try to determine the file and why the error occurred.
  5. Share this:TwitterFacebookLike this:Like Loading...
  6. Sorry, we couldn't post your feedback right now, please try again later.
  7. Status Code 167 ==================== cannot find requested volume pool in EMM database A backup to a nonrobotic drive was attempted and the tape manager (bptm) cannot find or add the specified
  8. A possible cause is a permission problem with the file.

Netbackup Error Codes And Resolution

Status Code 142 ==================== file does not exist To back up a VxFS file system with Snapshot Client, the VxFS file system on the client must be patched with correct, dynamically Status Code 140 ==================== user id was not superuser A user or process that did not have root privileges (on UNIX) or administrator privileges (on Windows) started the process. Veritas Netbackup Error Codes List Correct problems and retry the backup. 2. Important Error Codes In Veritas Netbackup Status Code: 51 Top Message: timed out waiting for database information Explanation: The database process did not respond within five minutes.

Please provide a Corporate E-mail Address. have a peek at these guys Retry the operation and check the resulting activity logs for detailed troubleshooting information. On UNIX clients, verify that you have write permission to the directories that contain the files. Verify that the client name is correct in: o The NetBackup class configuration on the master server. Netbackup Important Error Codes

This usually results from different versions of NetBackup software being used together. * If a client receives this error in response to a list or restore request, then the DISALLOW_CLIENT_LIST_RESTORE or A frequent cause is that the server's file system is full. A client and server with multiple network connections can encounter this problem in the following situation: the name by which the client is configured is not the one by which its http://nodatasource.com/error-code/netbackup-error-codes-pdf.html Status Code 284 ==================== error(s) occurred during vault report distribution Vault encountered errors during the report distribution phase.

To display this dialog box, start the Backup, Archive, and Restore interface on the client and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on Netbackup Error Code 23 Status Code: 21 Top Message: socket open failed Explanation: A socket open failed. Close Sign In Download Attachments Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Description NetBackup 7.7 Status Codes Reference Guide The attached guide documents the

o Create a bpcd activity log directory (this log is created automatically on Macintosh clients.

Status Code 80 ==================== Media Manager device daemon (ltid) is not active If the server is UNIX, the NetBackup device manager daemon, ltid, is not running. Status Code 39 ==================== client name mismatch The client used a name in a request to the NetBackup server that did not match the configured name in the policy on the Status Code 185 ==================== tar did not find all the files to be restored The tar file list contained files that were not in the image. Netbackup Error Code 24 Examine other activity logs or the progress log on the client. 7.

Related This entry was posted in Netbackup and tagged Netbackup Status Code, Veritas Netbackup, Veritas Netbackup Error Codes, Veritas Netbackup Troubleshooting Guide. Status Code 99 ==================== NDMP backup failure The paths in your NDMP policy file list did not back up successfully. An overloaded network can cause this error. 5. this content If the logs show that it is associated with a subsequent error, it usually indicates a communication problem.

NetBackup executes client processes with the group ID of the requesting user. Another possible cause: the last available drive has a mount request for a non-backup (such as a restore). Status Code 217 ==================== failed reading storage unit database information During its periodic checking of the NetBackup configuration, nbpem did not read the storage unit configuration. E-Zine Everything you need to know about storage snapshots E-Chapter Double down: When backups and archives beat as one E-Handbook Direct backup changes rules, cost of backup Brien Poseyasks: What NetBackup

If these services are not running, start them. o Increase the amount of debug information included in the logs as explained in the activity log topics in Chapter 3, "Using the Logs and Reports." 3. For detailed troubleshooting information, create an activity log directory for the process that returned this status code, retry the operation, and check the resulting activity log. Status Code 220 ==================== database system error The bpdbm process (UNIX), or the NetBackup Database Manager service (Windows) did not create a directory path for its configuration catalogs.

Recommended Action: 1. Note that NetBackup does not change storage units during the backup. Status Code 233 ==================== premature eof encountered This status code is an intermediate one that usually precedes another status code and is associated with a problem in network communication. Email Address (Optional) Your feedback has been submitted successfully!

The accept system or winsock call timed out after 60 seconds. Login SearchDataBackup SearchSolidStateStorage SearchConvergedInfrastructure SearchCloudStorage SearchDisasterRecovery SearchStorage SearchITChannel Topic Backup software Backup tools View All Archiving Virtual server backup Cloud backup Security View All Data reduction View All Backup tools View