Veritas Netbackup Error Codes List
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. Then, retry the operation and check the resulting activity logs. 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 Status Code 197 ==================== the specified schedule does not exist in the specified policy A user backup or archive request specified the exact policy and schedule to use when a backup http://pdctoday.com/error-code/veritas-netbackup-error-codes.php
Status Code 209 ==================== error creating or getting message queue When a NetBackup process attempts to create an internal message queue construct for inter-process communication, an error occurs. For a FlashBackup client, check the /var/adm/messages log for errors like the following: Mar 24 01:35:58 bison unix: WARNING: sn_alloccache: cache /dev/rdsk/c0t2d0s3 full - all snaps using this cache are now Status Code 91 ==================== fatal NB media database error The tape manager (bptm) received an error while it read or updated its media catalog. Status Code: 39 Message: client name mismatch Explanation: The name that the client used in a request to the NetBackup server did not match the client name configured in the class http://backup.technion.ac.il/codes
Netbackup Error Codes Pdf
Recommended Action: Check the bpstart_notify script on the client to see if it performs as desired. Get Symantec's explanation of how to fix this issue. Then, retry the operation and check the resulting activity logs.
Recommended Action: Perform "Resolving Network Communication Problems" on page 21. Status Code 23 ==================== socket read failed A read operation from a socket failed. Status Code: 24 Top Message: socket write failed Explanation: A write operation to a socket failed. Veritas Netbackup Error Codes Pdf Recommended Action: Change either the NetBackup client name setting on the client (see the applicable NetBackup users guide) or the one in the class configuration on the server so the two
This error is usually a result of the use of software from different versions. Netbackup Status Codes Reference Guide Status Code: 62 Message: wbak exited abnormally Explanation: The wbak process on the Apollo exited abnormally. Status Code 97 ==================== requested media id is in use, cannot process request An operation was requested on a media ID that is in use. additional hints Status Code 71 ==================== none of the files in the file list exist The files in the file list did not match any of the files on the client.
On Windows NT, 98, and 95 systems, the master server is designated as Current on the Servers tab in the NetBackup Configuration dialog box. Netbackup 7.7 Status Codes 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 The SYSTEM account cannot access network drives. If you change the server list on a master server, stop and restart the NetBackup database manager and request daemons (UNIX) or the NetBackup Database Manager and NetBackup Request Manager services
Netbackup Status Codes Reference Guide
Recommended Action: This is usually caused by someone intentionally terminating a backup. https://nixguru.wordpress.com/2012/11/18/netbackup-important-error-codes-its-solutions/ Status Code 154 ==================== storage unit characteristics mismatched to request A backup was attempted and the storage unit selected for use had the characteristics that were not compatible with the backup Netbackup Error Codes Pdf Check the inetd log to see if NetBackupListen is running. Netbackup Error Codes And Resolution Check for full file systems on the client. 3.
On all but Macintosh clients, enable bpcd activity logging as follows: a. have a peek at these guys For example, if a NetBackup master server has NetBackup 3.2 and the slave server has NetBackup 3.0. Status Code: 9 Message: an extension package is needed but was not installed Explanation: A NetBackup extension product is required in order to perform the requested operation. Status Code: 25 Message: cannot connect on socket Explanation: A process timed out while connecting to another process for a particular operation. Important Error Codes In Veritas Netbackup
- Status Code: 61 Top Message: wbak was killed Explanation: The wbak process on the Apollo was killed.
- Submit your e-mail address below.
- If you cannot determine the cause from the Problems report, create activity log directories for the processes that could have returned this status code.
- You should begin the troubleshooting process by checking the logs for any further explanation of why the restore failed.
- Determine the client and server that had the handshake failure.
Status Code 67 ==================== client backup failed to read the file list The client did not read the list of files to back up. Status Code 32 ==================== could not set group id for process Could not set the group ID of a process to the requesting user group. Check the level of network activity. http://pdctoday.com/error-code/windows-vista-error-codes-list.php No Yes How can we make this article more helpful?
No Yes Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES Netbackup Important Error Codes Verify that the client and servers are operational and connected to the network. 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
For detailed debug information: 1.
Email Address (Optional) Your feedback has been submitted successfully! On UNIX and Windows NT clients, create a bpbkar activity log directory. On Windows NT clients, verify that the account used to start the NetBackup Client service has read access to the files. Netbackup Error Code 23 Retry the backup and examine the resulting logs to determine the cause of the failure. 2.
However, the disk file path already exists and is not a directory. Recommended Action: First, verify that the server did not crash. The installation will complete successfully under a non-administrator account but the NetBackup Client service is not added to Windows NT and the NetBackup server cannot access the client. this content As a result, the server attempts to make a non-encrypted backup of the client.
Other possible causes of this error: * nbjm is unable to connect to bpcd on the media server * nbpem is unable to connect to nbproxy * bptm on the media When you are through investigating the problem, delete the /usr/openv/netbackup/logs/bpbkar directory, since the log files can become quite large and are not deleted automatically. On a Windows NT master server, verify that the NetBackup Request Manager and NetBackup Database Manager services are running. On Windows NT, verify that the recommended service packs are installed.
Try to ping the client from the server and the server from the client. Status Code 243 ==================== the client is not in the configuration The specified client name was not in the catalog. 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. On a UNIX client, use the ps command to check for a client process that is using too much CPU time.
On Windows NT, verify that the recommended service packs are installed. Status Code: 66 Message: client backup failed to receive the CONTINUE BACKUP message Explanation: The client bpbkar process did not receive the message from the server that indicates that the server Status Code 93 ==================== media manager found wrong tape in drive When you load a volume for a backup or restore, the tape manager (bptm) found a volume that loaded without A socket read failure can be caused by a network problem or a problem with the process that is writing to the socket.
Status Code 73 ==================== bpstart_notify failed The bpstart_notify script returned a nonzero exit code. Status Code: 27 Message: child process killed by signal Explanation: A child of the process reporting this error was killed. Status Code 215 ==================== failed reading global config database information During the periodic checking of the NetBackup configuration, nbproxy was unable to read the global configuration parameters. On UNIX, and Macintosh clients, add a SERVER entry in the bp.conf file. • On NetWare target and OS/2 clients add a SERVER entry in the bp.ini file.