Fix Veritas Netbackup Error Codes List Tutorial


Home > Error Code > Veritas Netbackup Error Codes List

Veritas Netbackup Error Codes List

Contents

It also occurs if the script returns an error. Please visit the Veritas support web site, and refer to Technote number 262225 for further information. * For the backups that run from a FlashBackup policy, the following appears in the This usually occurs when you use multiplexing, which increases the shared memory requirements. For this case, try adding or modifying the CLIENT_READ_TIMEOUT and CLIENT_CONNECT_TIMEOUT values in the server's /usr/openv/netbackup/bp.conf file. http://nbxcorp.com/error-code/veritas-netbackup-error-codes.html

On all but Macintosh clients, enable bpcd activity logging as follows: Create a bpcd activity log directory on the client. Note: If you are using bpstart_notify scripts on UNIX or Windows NT clients, verify that messages are not being written to stdout or stderr. o The bp.ini file on OS/2 and NetWare target clients. 2. 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. http://backup.technion.ac.il/codes

Netbackup Error Codes Pdf

If you cannot determine the cause from the Problems report, create activity log directories for the processes that could have returned this status code. The corrective action is to add CLIENT_READ_TIMEOUT to the /usr/openv/netbackup/bp.conf file and set it to increase the timeout interval. 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 On UNIX clients, check to see if the files or directories would be excluded because of an entry in /usr/openv/netbackup/exclude_list.

  • Then, retry the operation and check the resulting activity log.
  • Status Code 189 ==================== the server is not allowed to write to the client's filesystems The client does not allow writes from the server.
  • Recommended Action: First, verify that the server did not crash.
  • For detailed troubleshooting information, create activity log directories for the processes that you suspect of returning this status code.
  • Check the ps output to see if rbak is hung.
  • No altnames configuration for this client exists on the master server.
  • Status Code: 69 Top Message: invalid file list specification Explanation: The file list received from the server had invalid entries.
  • 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
  • On NetWare target and OS/2 clients, the master server name is the first SERVER entry in the bp.ini file.

This error is usually a result of the use of software from different version levels. Privacy Load More Comments Forgot Password? This email address doesn’t appear to be valid. Veritas Netbackup Error Codes Pdf If this is a NetBackup for NetWare client and has a version of NetBackup earlier than 3.0, verify that the client is in a Standard type class.

This is most commonly seen on Solaris 2 servers when an RDBMS is also running. Netbackup Status Codes Reference Guide If you change the server list on a Windows NT master server, stop and then restart the NetBackup Request Manager and NetBackup Database Manager services. The backup is retried automatically with a different volume if the backup tries attribute allows it in the NetBackup global attribute configuration. On UNIX and Windows NT clients, create a bpbkar activity log directory.

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 Netbackup 7.7 Status Codes Status Code: 46 Message: server not allowed access Explanation: The server is trying to access the client but the server is not listed on the client as a valid server. Status Code: 43 Top Message: unexpected message received Explanation: The client and server handshaking was not correct. For detailed troubleshooting information, create an activity log for the process that you suspect of returning this status code.

Netbackup Status Codes Reference Guide

Status Code 108 ==================== Status code not available. The accept system call timed out after 60 seconds. Netbackup Error Codes Pdf Both logs are created automatically. Netbackup Error Codes And Resolution Recommended Action: Save all error information and call customer support.

Status Code 100 ==================== system error occurred while processing user command A system call failure in bparchive, bpbackup, bplist, or bprestore. http://nbxcorp.com/error-code/wii-error-codes-101.html On UNIX clients, verify that the /usr/openv/netbackup/bin/bpcd binary exists and that it is the correct size. Download this guide and not only discover the latest upgrades to today's top enterprise backup vendors, but also learn where backup software works best in your computing environment. 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. Important Error Codes In Veritas Netbackup

Verify that the NetBackup Client service is running. 2. Sorry, we couldn't post your feedback right now, please try again later. Ensure 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 file. Check This Out On a UNIX client, add the VERBOSE option to the bp.conf file.

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 Netbackup Important Error Codes Status Code 205 ==================== cannot connect to server backup restore manager A process on the master server cannot connect to a process on a host on the network. This could be caused by the system being overloaded with too many processes and there is not enough physical and virtual memory.

On Windows NT clients, verify that the account used to start the NetBackup Client service has read access to the files.

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 Status Code 129 ==================== Disk storage unit is full As NetBackup writes to the file system for the disk storage unit, runs out of space. Recommended Action: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. Netbackup Error Code 23 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

Status Code 210 ==================== error receiving information on message queue When a NetBackup process attempts to receive a message from a NetBackup daemon using bprd on an internal message queue construct, 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 If nbjm received a negative error number, status 114 is issued. http://nbxcorp.com/error-code/wep-error-codes.html This error can occur because the permissions of the command do not allow it to be run.

Check for full file systems on the client. Status Code: 1 Message: the requested operation was partially successful Explanation: A problem that may require corrective action was detected during the requested operation. For example, a job fails with this error code if a policy is set up that specifies the following: * A storage unit that is on a SAN media server * You should begin the troubleshooting process by checking the logs for any further explanation of why the restore failed.

This email address is already registered. The bp.ini file on OS/2 and NetWare target clients. Status Code: 35 Message: cannot make required directory Explanation: Could not create a required directory. The symptoms of the problem vary.

Bookmark the permalink. ← Netbackup Important Ports AIX Startup Modes → Leave a Reply Cancel reply Enter your comment here... Recommended Action: 1.