NetBackup Common Fault Handling

Common NBU Errors and Troubleshooting

1. Typical Fault 1

Common Errors and Troubleshooting

Common Error Resolution

Veritas NetBackup provides powerful fault response capabilities to effectively and timely handle various backup failures. These include backup status codes (status), error messages, report information, and debug logs. The following section focuses on explaining common errors and troubleshooting methods based on backup status codes.

1. NetBackup Status Code: 0

Message: Requested operation completed successfully

Explanation: No issues were detected for the requested operation.

1. NetBackup Status Code: 1

Message: Requested operation partially successful

Explanation: A potential issue requiring correction was detected during the execution of the requested operation.

Recommended Action:

1. Ensure the backup file is not currently in use or being modified.
2. Check if the file or directory path length exceeds 1023 characters.
3. Unable to open file. Check file permissions or look for hidden files in the directory.
4. NetBackup Status Code: 2

Message: None of the requested files were backed up

Explanation: The backup or archive operation could not back up any files from the specified file list.

Recommended Action: Verify that these files exist and that you have read permissions for them.

1. Check the client's file list to determine if one or more filenames contain trailing spaces. Remove all unintentionally added trailing characters.
2. On Windows clients, verify that the account used to start the NetBackup client service has read permissions for these files.
3. NetBackup Status Code: 6

Message: The backup operation failed to back up the requested files.

Explanation: The error that occurred caused the user backup to fail.

Recommended Action:

1. Verify that you have read permissions for these files. Check file read permissions or user permissions on Windows.
2. For Database Extension clients (such as NetBackup for Oracle), this may indicate a problem with the script controlling the backup. For details, check the script's Out file and error messages.
3. NetBackup Status Code: 41

Message: Network connection timeout

Explanation: The server did not receive any information from the client for too long.

Recommended Action:

1. On the NetBackup server, use Host Properties to change the Client connect timeout or Client read timeout. The default is 300 seconds.
2. If the backup still fails after changing the above properties, check whether network communication is abnormal.
3. NetBackup Status Code: 50

Message: Client process aborted

Explanation: The client backup was aborted. One scenario in which this code appears is when the NetBackup master server or media server shuts down or restarts while a backup or restore is in progress.

1. NetBackup Status Code: 54

Message: Timeout connecting to the client

Explanation: The server could not complete the connection to the client. The accept system or Winsock call timed out after 60 seconds.

1. NetBackup Status Code: 57

Message: Client connection refused

Explanation: The client refused the connection on the bpcd port. This may occur because no process is listening on the bpcd port, or because too many connections to the bpcd port exceed the number that the network subsystem can handle using the listen() call.

1. NetBackup Status Code: 71

Message: None of the files in the file list exist

Explanation: The files in the file list do not match any files on the client. This error occurs when there is only one file in the file list and it cannot be backed up due to an I/O error.

Recommended Action:

1. Verify that the correct file list has been specified for this client.
2. On Windows clients, verify that the account used to start the NetBackup client service has read permissions for these files.
3. NetBackup Status Code: 96

Message: Unable to allocate new media for backup; no media available in the storage unit

Explanation: The tape manager (bptm) cannot allocate a new volume for the backup. It indicates that the storage unit has no other available volumes in the volume pool for this backup. Note that NetBackup does not change storage units during backup.

Recommended Action:

Use the available_media command to check tape usage.

On UNIX, this script is located at:

/usr/openv/netbackup/bin/goodies/available_media

On Windows, this script is located at:

install_path\NetBackup\bin\goodies\available_media

1. NetBackup Status Code: 196

Message: No attempt was made to back up the client because the backup window has passed

Explanation: The backup scheduler did not attempt to execute the queued backup or archive operation because the backup window is no longer open.

Recommended Action:

1. Please check if any processes are frozen and continuously occupying the drive. If so, restart the backup server or media server services and retry the backup.
2. If possible, modify the schedule to extend the backup window time for this policy and schedule combination to prevent this error from occurring again.

If you must run this backup, use the Manual Backup command on the Policy menu of the Backup Policy Management window to execute the backup. Manual backups ignore the backup window.

1. NetBackup Status Code: 198

Message: No active policy contains a schedule of the requested type for this client.

Explanation: A user backup or archive was requested, but this client is not included in a policy that has a user backup schedule or archive schedule.

Recommended Action:

1. Determine whether the client is located in any policy with an appropriate type (user backup or archive) schedule.
2. If the client is in such a policy, check the General Policy Properties to ensure the policy is set as an active policy.
3. If the client is not in such a policy, add an appropriate type schedule to an existing policy containing this client, or create a new policy with this client and an appropriate type schedule.
4. NetBackup Status Code: 219

Message: Required storage unit is unavailable.

Explanation: The policy or schedule being backed up requires a specific storage unit, but that storage unit is currently unavailable. Other attempts to use this storage unit during the current backup session will also result in this error.

Recommended Action:

Locate the failed job in the Job Details window.

1. Verify that the schedule specifies the correct storage unit and that the storage unit exists.
2. Verify that the Media Manager device daemon (ltid) is running (if the server is a UNIX system), or verify that the NetBackup Device Manager service is running (if the server is a Windows system). Use bpps on UNIX and Activity Monitor on Windows, or the Services application in the Windows Control Panel.
3. Ensure the Maximum concurrent jobs property is not set to 0 (for disk storage units), and the Maximum concurrent drives property is not set to 0 (for Media Manager storage units).
4. If the storage unit is tape or optical, verify that at least one drive is in the 'Up' state. You can use the Device Monitor.
5. Verify that the robot number and host in the storage unit configuration match those specified in the Media Manager device configuration.
6. Verify that the master server can communicate with the bpcd process on the server where the storage unit resides.

Troubleshoot using detailed debug logs.

When troubleshooting NetBackup issues, if the status code cannot resolve the issue or the information provided by the status code does not allow analysis of the cause, more detailed debug logs are required for reference. The steps to create detailed debug logs are as follows:

1. Create Debug Log Directory

On the Windows platform, execute the mklogdir.bat command under the install_path\NetBackup\logs\ directory to create the log directory.

Under the UNIX platform, execute the mklogdir command under the install_path/NetBackup/logs/ directory to create the debug log directory.

1. Change Debug Log Level

By changing the debug level, you can control the amount of debug logs written to the /usr/openv/netbackup/logs/ directory.

The larger the value, the more information is recorded in the log. Typically, the default value of 0 is sufficient. However, when analyzing issues, technical support personnel may request that you set a larger value. The debug level can be set to 0, 1, 2, 3, 4, or 5. Level 5 provides the most detailed information.

The method to change is as follows:

1. Enable detailed logging by adding the following line to the bp.conf file (for UNIX system platforms).

VERBOSE = 5

After modifying this parameter, you must restart the NetBackup service for it to take effect.

1. Modify via the NetBackup Java Console.

Open the NetBackup Java Console Host Properties Master Server (Clients) Select the corresponding host Select Enter Select Logging to configure OK Restart the service process.

Images localized into English for illustration; labels may vary by product version.