Home > Error Code > Veritas Netbackup Error Codes

Veritas Netbackup Error Codes


Enable detailed activity logging on the client: o Create bpcd and bpbkar (UNIX or Windows NT only) activity log directories. Recommended Action: 1. This list comes from the server. Recommended Action: 1. http://itechnologysolutionsllc.com/error-code/veritas-netbackup-error-codes-list.php

Status Code 265 ==================== session id file is empty or corrupt The session ID that is stored in the following file is corrupt. Status Code 141 ==================== file path specified is not absolute The file specification must be an absolute path. Status Code: 36 Top Message: failed trying to allocate memory Explanation: Allocation of system memory failed. Recommended Action: Perform "Resolving Network Communication Problems" on page 21. https://www.veritas.com/support/en_US/article.DOC6471

Netbackup Error Codes And Solutions

Loading... Status Code 81 ==================== Media Manager volume daemon (vmd) is not active The tape manager (bptm) did not communicate with the NetBackup Volume Manager (vmd). 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

  • To increase the logging level, set the loglevel parameter in the mac.conf file to a higher value. 1.
  • Note that NetBackup does not change storage units during the backup.
  • To back up network drives or UNC paths, change the NetBackup Client service startup to log in as a user that has permission to access network drives.
  • Recommended Action: Check the NetBackup Problems report for clues on where and why the problem occurred.

Recommended Action: 1. On Windows NT, stop and restart the NetBackup Request Manager and NetBackup Database Manager services. 3. Status Code: 8 Top Message: unable to determine the status of rbak Explanation: On DomainOS clients, rbak is used to do restores. Netbackup 7.7 Status Codes Status Code 203 ==================== server backup restore manager's network is unreachable A process on the master server cannot connect to a particular host on the network when it tries to initiate

No Yes How can we make this article more helpful? Netbackup Error Codes Pdf For example, this error occurs if a NetBackup master or media server is shut down or rebooted when a backup or restore is in progress. An overloaded network can cause this error. 5. https://www.veritas.com/support/en_US/article.DOC8599 Recommended Action: Verify that the server software has been installed correctly on the master server and all slave servers.

On Windows NT, verify that the %SystemRoot%\system32\drivers\etc\services file has the correct entries for bpcd, bpdbm, and bprd. Important Error Codes In Veritas Netbackup Status Code 183 ==================== tar received an invalid archive The data that was passed to tar was corrupt. Check the IP address for the client. SearchDisasterRecovery Dell Services elevates Alabama city's DR plan with the cloud After a massive tornado touched down across the state, the city of Opelika, Ala., looked to the cloud to get

Netbackup Error Codes Pdf

Both logs are created automatically. This error indicates that the client and server were able to initiate communications, but encountered difficulties and the communications did not complete. Netbackup Error Codes And Solutions If that is not the problem: 1. Veritas Netbackup Error Codes List On Windows, the server list contains no entries.

Status Code 199 ==================== operation not allowed during this time period A user backup or archive was requested and this client is not in a policy that has the following: a his comment is here Status Code 66 ==================== client backup failed to receive the CONTINUE BACKUP message The client bpbkar process did not receive the message from the server that indicates that the server is To increase the amount of information that appears in the logs, see the logging topics in Chapter 3, "Using the Logs and Reports." 2. Status Code 246 ==================== no active policies in the configuration database are of the correct client type A user backup request was not satisfied because no active policies were the type Netbackup Error Codes And Resolution

o On other PC clients except Macintosh, create an activity log directory for bpcd (the bpcd log is created automatically on Macintosh). On Windows NT clients, verify that the NetBackup Client service is running. 3. Another possibility: a media ID in the NetBackup catalog backup configuration does not match the media type that was entered in the volume configuration. http://itechnologysolutionsllc.com/error-code/windows-system-error-codes-exit-codes-description.php Status Code 35 ==================== cannot make required directory Could not create a required directory.

If the problem is not serious and the files were backed up, you can manually delete the files. Veritas Netbackup Error Codes Pdf Then, retry the operation and check the resulting activity log. Status Code 170 ==================== third party copy backup failure Usually indicates a problem with the 3pc.

Status Code 119 ==================== Status code not available.

Then, retry the operation and check the resulting activity log. You have exceeded the maximum character limit. 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. Netbackup Error Code 1 Errors associated with NetBackup status codes can often be traced to permissions issues, resource allocation issues, or other simple configuration or logistical issues.

Check the script for problems. Verify that the server list settings are correct on both the client and the server. A possible cause could be a high network load. navigate here Status Code 90 ==================== media manager received no data for backup image The tape manager (bptm) or disk manager (bpdm) received no data when it performed a backup, archive, or duplication.

Possible causes include: * An I/O error occurred during a read from the file system. * Read of an incomplete file or a corrupt file. * Socket read failure. Status Code: 71 Top Message: none of the files in the file list exist Explanation: The files in the file list did not match any of the files on the client. Status Code 129 ==================== Disk storage unit is full As NetBackup writes to the file system for the disk storage unit, runs out of space. This is a non-specific error that basically says, "Something went wrong, but I'm not going to tell you what it was." Unfortunately, there is no magical fix for this error.

Possible causes are: A process does not have permission to create the directory The path to the directory is not valid An IO error occurs There was Status Code 114 ==================== unimplemented error code This error should not occur. On a Windows NT NetBackup server (master or slave), check the Event Viewer Application log for error messages that indicate why the tape mount did not complete. This error can occur because the permissions of the command do not allow it to be run.

Status Code: 62 Top Message: wbak exited abnormally Explanation: The wbak process on the Apollo exited abnormally. Status Code: 25 Top Message: cannot connect on socket Explanation: A process timed out while connecting to another process for a particular operation. Check the progress log for any unusual messages from rbak. If the bpbrm log has entries similar to the following: bpbrm hookup_timeout: timed out waiting during the client hookup bpbrm Exit: client backup EXIT STATUS 41: network connection timed out then

Follow us