Home > Error Code > Netbackup Error Codes And Solutions

Netbackup Error Codes And Solutions

Contents

On a UNIX client, add the VERBOSE option to the /usr/openv/netbackup/bp.conf file. You may also refer to the English Version of this knowledge base article for up-to-date information. Recommended Action: 1. How can a Docker backup be more reliable and consistent? http://techkumar.com/error-code/windows-error-codes-and-solutions-pdf.html

This is one of the NetBackup status codes that often relates to a security or configuration issue. This has been seen to occur during backups when directories have thousands of unmodified files; it has also been seen when backing up file systems or directories that reside on optical On Windows, the server list contains no entries. On a UNIX system, check that /etc/services and NIS services map (if applicable) have entries for the NetBackup services: bpcd, bpdbm, and bprd. 3. additional hints

Netbackup Error Codes And Solutions

Status Code 216 ==================== failed reading retention database information During its periodic checking of the NetBackup configuration, nbpem did not read the list of retention levels and values. Recommended Action: Check the NetBackup Problems report for clues on where and why the problem occurred. If the problem is due to mandatory file locking, you can have NetBackup skip the locked files by setting LOCKED_FILE_ACTION to SKIP in the /usr/openv/netbackup/bp.conf file on the client. Status Code 238 ==================== the database contains conflicting or erroneous entries The catalog has an inconsistent or a corrupted entry.

  1. Status Code 127 ==================== specified media or path does not contain a valid NB database backup header The bprecover command was issued and the media ID specified does not have valid
  2. This error should not occur through normal use of NetBackup.
  3. b.
  4. Another possibility: a media ID in the NetBackup catalog backup configuration does not match the media type that was entered in the volume configuration.
  5. Status Code 33 ==================== failed while trying to send mail An email notification about backup, archive, or restore results has failed.
  6. Status Code 97 ==================== requested media id is in use, cannot process request An operation was requested on a media ID that is in use.
  7. This status code is used for a generic system call failure that does not have its own status code.
  8. A possible cause is a permission problem with the file.

If you cannot determine the cause from the Problems report, create activity log directories for the processes that could have returned this status code. This communication is required for most operations. Status Code 145 ==================== daemon is already running Another copy of the process is running. Netbackup 7.7 Status Codes Visit Symantec's website to read its recommended action.

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 165 ==================== NB image database contains no image fragments for requested backup id/copy number A restore was attempted and NetBackup has no record of the fragments that are associated If that is not the problem and you need more information: 1. The best way to do that is to look through the backup logs for any hint as to what might be causing the problem.

o On Windows NT, 98, and 95 systems, the master server is designated as Current on the Servers tab in the NetBackup Configuration dialog box. Important Error Codes In Veritas Netbackup Status Code 16 ==================== unimplemented feature The specified operation is not implemented. Status Code 221 ==================== continue This status code is used to coordinate communication between various NetBackup processes and normally does not occur. If the logs show that it is associated with a subsequent error, it usually indicates a communication problem.

Netbackup Error Codes Pdf

The maximum number is specified in the Media and Device Management volume configuration. her latest blog 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. Netbackup Error Codes And Solutions Status Code 218 ==================== failed reading policy database information During the periodic checking of the NetBackup configuration, nbpem did not read the backup policy configuration. Veritas Netbackup Error Codes List No Yes How can we make this article more helpful?

One customer running both NetBackup and ORACLE on their Solaris server made the following changes to their /etc/system file and then rebooted the system (boot -r); the changes were found to http://techkumar.com/error-code/msi-exit-codes.html Status Code 46 ==================== server not allowed access The server tries to access a client, but access is blocked. This error can be caused by the system not having enough semaphores allocated. Sorry, we couldn't post your feedback right now, please try again later. Netbackup Error Codes And Resolution

Sign in 3 0 Don't like this video? Datalink Corp 627 views 39:28 Troubleshooting VMware Shanpshot Errors - Duration: 5:39. Status Code: 18 Top Message: pipe close failed Explanation: Close of a pipe failed, when one process tries to start a child process. have a peek here Status Code 42 ==================== network read failed An attempt to read data from a socket failed.

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, Veritas Netbackup Error Codes Pdf Sign in to make your opinion count. Status code 40 can also be due to the operator denying a mount request.

Either no Vault jobs were run for this profile or the corresponding sidxxx session id directory (or directories) were removed from the following directory: UNIX: /usr/openv/netbackup/vault/sessions/vault_name Windows: install_path\NetBackup\vault\sessions\vault_name Status Code 270

If the server cannot connect to the client, create bpcd or bpbkar (UNIX and Windows NT only) activity log directories on the client, retry the operation, and check the resulting logs. You may also refer to the English Version of this knowledge base article for up-to-date information. o The bp.conf file on UNIX and Macintosh clients. Netbackup Error Code 1 Since the backup was successful, you can delete the files that were backed up (or have the system administrator delete the files if you do not have the necessary permissions).

Status Code 23 ==================== socket read failed A read operation from a socket failed. Terms of use for this information are found in Legal Notices.

Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may For example: this status appears if you add a new policy when an existing policy has the same name or definition such as attributes or clients. Check This Out Look in the activity log files to find more information on the problem.

This problem can occur during a backup or restore in either a single or a multiple server configuration. For this case, add the following to the client's bp.conf file: VERBOSE and as root on the client execute: touch /usr/openv/netbackup/bpbkar_path_tr mkdir /usr/openv/netbackup/logs/bpbkar Then retry the operation. You should begin the troubleshooting process by checking the logs for any further explanation of why the restore failed. For example, the entity can be a file or it can be policy information.

In some cases, 1,023-character file paths are allowed, but try to keep the path under 1,000 characters if possible. For detailed troubleshooting information, create an activity log directory for the process that you suspect of returning this status code. In particular, check for a full disk partition. 2. This status code is used for a generic system call failure that does not have its own status code.

Examine the progress log on the client for messages on why the restore failed. For example, in one instance, the following was seen in the bpsched activity log. This error indicates a problem on the master server. Status Code 225 ==================== text exceeded allowed length Text in a request exceeds a buffer size.

For detailed troubleshooting information, create an activity log directory for the process that you suspect of returning this status code. For example, a NetBackup master server has NetBackup 6.5 and the media server or the client has NetBackup 4.5. This error can also occur if the wrong parameters are used when you run a command line. Please login.

Recommended Action: 1. This problem can sometimes be due to a corrupt binary. Retry the operation and examine the resulting logs. 5. This cause of this error may be that the system is overloaded with too many processes and it does not enough physical and virtual memory.

Status Code 193 ==================== VxSS authentication is requested but not allowed On one side of a NetBackup network connection, the system requires VxSS authentication. On UNIX, the /usr/openv/netbackup/bp.conf file does not exist. Recommended Action: Save all error information and call customer support. Status Code 74 ==================== client timed out waiting for bpstart_notify to complete The bpstart_notify script on the client takes too long.