96Troubleshooting
Troubleshooting operational issues
Backup jobs fail
If backup jobs fail with an Error 800: Disk Volume is Down message, examine the disk error logs to determine why the volume was marked DOWN.
If the storage server is busy with jobs, it may not respond to master server disk polling requests in a timely manner. A busy load balancing server also may cause this error. Consequently, the query times out and the master server marks the volume DOWN.
If the error occurs for an optimized duplication job: verify that source storage server is configured as a load balancing server for the target storage server. Also verify that the target storage server is configured as a load balancing server for the source storage server.
See “Viewing disk errors and events” on page 97.
Volume state changes to DOWN when volume is unmounted
If a volume becomes unmounted, NetBackup changes the volume state to DOWN. NetBackup jobs that require that volume fail.
To determine the volume state
◆Invoke the following command on the master server or the media server that functions as the deduplication storage server:
The following example output shows that the DiskPoolVolume is UP:
Disk Pool Name | : PD_Disk_Pool |
Disk Type | : PureDisk |
Disk Volume Name | : PureDiskVolume |
Disk Media ID | : @aaaab |
Total Capacity (GB) | : 49.98 |
Free Space (GB) | : 43.66 |
Use% | : 12 |
Status | : UP |
Flag | : ReadOnWrite |
Flag | : AdminUp |
Flag | : InternalUp |
Num Read Mounts | : 0 |
Num Write Mounts | : 1 |
Cur Read Streams | : 0 |
Cur Write Streams | : 0 |
