Please enter search query. Search <book_title>...
Veritas NetBackup™ Troubleshooting Guide
Last Published: 2021-01-01
Product(s): NetBackup (184.108.40.206, 9.0)
- Troubleshooting procedures
- Troubleshooting NetBackup problems
- Troubleshooting vnetd proxy connections
- Troubleshooting security certificate revocation
- Verifying host name and service entries in NetBackup
- Frozen media troubleshooting considerations
- Troubleshooting problems with the NetBackup web services
- Resolving PBX problems
- Troubleshooting problems with validation of the remote host
- Troubleshooting Auto Image Replication
- Using NetBackup utilities
- About the NetBackup support utility (nbsu)
- About the NetBackup consistency check utility (NBCC)
- About the robotic test utilities
- Disaster recovery
- About disk recovery procedures for UNIX and Linux
- About clustered NetBackup server recovery for UNIX and Linux
- About disk recovery procedures for Windows
- About clustered NetBackup server recovery for Windows
- About recovering the NetBackup catalog
- About NetBackup catalog recovery and OpsCenter
- About recovering the entire NetBackup catalog
- About recovering the NetBackup catalog image files
- About recovering the NetBackup relational database
Frozen media troubleshooting considerations
Frozen media can cause a number of problems including one of the following status codes: 84, 85, 86, 87 and 96.
When troubleshooting frozen media, be aware of the following:
Use the bpmedialist command to access the
MediaDBinformation including the media status (Frozen, Full, or Active).
To unfreeze the media, use the bpmedia command. Specify the media server that contains that frozen record in the command syntax. Unfreeze the media one at a time.
Frozen media does not necessarily mean that the media is defective. NetBackup may freeze media as a safety measure to prevent further errors, drive damage, or data loss.
Investigate any patterns to the media IDs, tape drives, or media servers that are involved when media is frozen.