Home > Error Code > Netbackup Error Codes Pdf

Netbackup Error Codes Pdf

Contents

The log messages were similar to the following: 01/31/96 14:05:23 ruble crabtree.null.com from client crabtree.null.com: ERR - Cannot write to STDOUT. If you continue to have problems, review "Resolving Network Communication Problems" on page 21 and "Verifying Host Names and Services Entries" on page 31. Status Code 34 ==================== failed waiting for child process A NetBackup process encountered a failure while waiting for a child process to complete. o On PC clients, increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and Reports." 4. Source

Please login. This problem can occur during a backup or restore in either a single or a multiple server configuration. UNIX and Windows NT clients are frequently not on the same subnet and use different domain servers. On NetWare target and OS/2 clients the master server name is the first SERVER entry in the bp.ini file. http://backup.technion.ac.il/codes

Netbackup Error Codes Pdf

Status Code 100 ==================== system error occurred while processing user command A system call failure in bparchive, bpbackup, bplist, or bprestore. The values on the Network tab are written to the services file when the NetBackup Client service starts. Recommended Action: If the server is a valid server, add its name to the client's server list: On Windows NT, 98, and 95 clients, add the server on the Servers Status Code: 68 Message: client timed out waiting for the file list Explanation: The client did not receive the list of files to back up within the allotted time.

  1. 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." Retry the operation and examine the
  2. However, the disk file path already exists and is not a directory.
  3. Check the NetBackup Problems report for clues on where and why the failure occurred.
  4. 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
  5. On PC clients, increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and Reports." 2. 2.
  6. Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred.
  7. Status Code 91 ==================== fatal NB media database error The tape manager (bptm) received an error while it read or updated its media catalog.
  8. Recommended Action: Check the NetBackup Problems report for clues on where and why the problem occurred.
  9. Statistics Search for: Recent Posts My new Blog Network Installation Manager(NIM) NTP Client configuration inAIX Enabling Telnet in Solaris10 Subsystem Resource Controller(SRC) Archives November 2012 Categories AIX AIX LESSONS GENERAL LINUX
  10. 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

On a UNIX client, use the ps command to check for a client process that is using too much CPU time. 4. On PC clients, increase the debug or log level as explained in the activity log topics in Chapter 3, "Using the Logs and Reports." Retry the backup and examine the resulting Status Code: 32 Message: could not set group id for process Explanation: Could not set the group ID of a process to the requesting user group. Veritas Netbackup Error Codes Pdf If the server is a valid slave server, verify that the storage unit for the slave server is defined.

Reinstall them if they are not the same as in the client directory under /usr/openv/netbackup/client on the server. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? If you change the server list on a UNIX master server, you must stop and then restart the NetBackup Request daemon (bprd) and NetBackup Database Manager daemon (bpdbm) for the changes If the logs show that it is associated with a subsequent error, it usually indicates a communication problem.

To increase virtual memory on Windows NT, 98, and 95: Display the Control Panel. Netbackup 7.7 Status Codes Please visit the Veritas support web site, and refer to Technote number 262225 for further information. 10:09:56.571 [1146] <16> bpbkar Exit: ERR - bpbkar FATAL exit status = 142: file does Retry the operation and check the resulting activity logs. Recommended Action: Verify that the name service (or services) being used by the client is configured to correctly resolve the host names of the NetBackup server.

Netbackup Status Codes Reference Guide

Also, verify that the NetBackup Client Service Port Number and NetBackup Request Service Port Number on the Network tab in the NetBackup Configuration dialog box match the settings in the services Retry the operation and check the resulting activity logs. Netbackup Error Codes Pdf Status Code 200 ==================== scheduler found no backups due to run When the NetBackup scheduler process (nbpem) checked the policy and the schedule configuration, it did not find any clients to Netbackup Error Codes And Resolution Recommended Action: 1.

Status Code: 32 Top Message: could not set group id for process Explanation: Could not set the group ID of a process to the requesting user group. this contact form This status code can also appear if the connection is broken between the master and slave server during a backup. Recommended Action: Save all error information and call customer support. To increase the amount of information that appears in the logs, see the logging topics in Chapter 3, "Using the Logs and Reports." 2. Important Error Codes In Veritas Netbackup

Status Code 258 ==================== Vault duplication was aborted by administrator request The administrator initiated an abort request on the active vault duplication job. Recommended Action: 1. Read of an incomplete or corrupt file. http://techkumar.com/error-code/msi-exit-codes.html o On clients, create a bpcd activity log directory (created automatically on Macintosh clients).

Note that NetBackup does not change storage units during the backup. Netbackup Important Error Codes On a UNIX client, add the VERBOSE option to the /usr/openv/netbackup/bp.conf file. Also delete /usr/openv/netbackup/bpbkar_path_tr so you do not generate larger log files than needed the next time you create directory /usr/openv/netbackup/logs/bpbkar.

Status Code 7 ==================== the archive failed to back up the requested files Errors caused the user archive to fail.

Examine the progress log on the client for messages on why the restore failed. Recommended Action: Perform "Resolving Network Communication Problems" on page 21. Recommended Action: 1. Netbackup Error Code 23 On Windows NT, verify that the recommended service packs are installed.

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. To display this dialog box, start the Backup, Archive, and Restore interface and click Configure on the Actions menu (also see "Using the Configure - NetBackup Window" on page 57). It can also occur if a large number of concurrent data streams are active at the same time. Check This Out Status Code: 31 Message: could not set user id for process Explanation: Could not set the user ID of a process to that of the requesting user.

Status Code 269 ==================== no vault session id was found This error is encountered when vltopmenu cannot find a sidxxx session id directory for the specified profile. No Yes How can we make this article more helpful? Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. Status Code 97 ==================== requested media id is in use, cannot process request An operation was requested on a media ID that is in use.

Status Code: 15 Top Message: file close failed Explanation: A close of a file or socket failed. Possible causes include: * An I/O error occurred during a write to the file system. * Write to a socket failed. Recommended Action: Check the class file list. Recommended Action: Examine the progress log of the archive on the client to determine if you need to retry the archive after correcting the problem.