Veritas NetBackup™ Status Codes Reference Guide
- NetBackup status codes
- NetBackup status codes
- NetBackup KMS status codes
- NetBackup status codes
- Media Manager status codes
- Media Manager status codes
- Media Manager status codes
- Device configuration status codes
- Device configuration status codes
- Device configuration status codes
- Device management status codes
- Device management status codes
- Device management status codes
- Robotic status codes
- Robotic status codes
- Robotic status codes
- Robotic error codes
- Robotic error codes
- Robotic error codes
- Security services status codes
- Security services status codes
- Security services status codes
- NetBackup alert notification status codes
NetBackup status code: 90
Explanation: The tape manager (bptm) or disk manager (bpdm) received no data when it performed a backup, archive, or duplication. This error can occur for incremental backups where no data was backed up because no files have changed.
Recommended Action: Do the following, as appropriate:
Check the All Log Entries report.
For detailed debug information, create bpdm or bptm debug log directories on the server. If the client is Windows, also create a bpbkar debug log directory on the client. Retry the operation and check the resulting debug logs.
For additional information, check the following:
NetBackup Problems report to determine the device or media that caused the error
System and error logs for the system (UNIX)
Event Viewer Application log (Windows)
Verify the Media and Device Management and system configuration for the drive.
For example, on UNIX, the drive may not be set for variable mode in a case where NetBackup requires that mode.
Check the NetBackup Device Configuration Guide for drive configuration information.
Verify that the Media and Device Management configuration for the backup device matches what is specified for the storage unit in the NetBackup policy.
Verify that you use the correct media in the drive.
For detailed debug information, create a bpdm or bptm debug log directory (whichever applies) on the server. If the client is Windows, also create a bpbkar debug log directory on the client. Retry the operation and check the resulting debug logs.
If the error occurred during duplication or a Vault session that uses an Alternate Read Server to perform duplication, verify that the Alternate Read Server has access to the source media.
Click here to view technical notes and other information in the Veritas Knowledge Base about this status code.