Drive Status

The following list describes the current drive status field descriptions for drives within a Veritas NetBackup (tm) configuration.

---

Details:

Manual:
Veritas NetBackup (tm) 6.5 Troubleshooting Guide for UNIX, Linux, and Windows
Veritas NetBackup (tm) 6.0 Media Manager System Administrator's Guide for UNIX, Page: 240-242
Veritas NetBackup (tm) 6.0 Media Manager System Administrator's Guide for Windows, Page: 223-225

Modification Type: Supplement

Modification:
The following NetBackup Drive statuses can appear in command line output or in the Device Monitor in the NetBackup Administration Console.

Column Description Note for the Administration Console:
Drive Name - Drive name assigned to the drive during configuration.
Control -  Control mode for the drive can be any of the following: robot_designation. For example, TLD.
The robotic daemon managing the drive has connected to LTID (the device daemon and Device Manager service) and is running. The drive is in the usable state. AVR is assumed to be active for the drive, as all robotic drives must be in automatic volume recognition (AVR) mode (not OPR mode).
Applies only to robotic drives.

DOWN-

For example, DOWN-TLD.

The drive is in an usable state because it was downed by an operator or by NetBackup; or when the drive was configured, it was added as a down drive. Applies only to robotic drives.

DOWN

In this mode, the drive is not available to Media Manager.

Applies only to standalone drives.

A drive can be in a DOWN mode because of problems or because it was set to that mode using Actions | Down Drive.

PEND-

For example, PEND-TLD.

The drive is in a pending status.  Applies only to robotic drives.

PEND

The drive is in a pending status.  Applies only to standalone drives.

If the drive reports a SCSI RESERVATION CONFLICT status, this column will show PEND. This status means that the drive is reserved when it should not be reserved. Some server operating systems (Windows, Tru64, and HP-UX) may report PEND if the drive reports Busy when opened. You can use the AVRD_PEND_DELAY entry in the Media Manager configuration file to filter out these reports.

AVR

The drive is running with automatic volume recognition enabled.

The drive is in a usable state with automatic volume recognition enabled, but the robotic daemon managing the drive is not connected or is not  working. Automated media mounts do not occur with a drive in this state (unless the media is in a drive on the system, or, this is a standalone tape drive), but the operator can physically mount a tape in the drive or use robtest to cause a tape mount as needed.

OPR

The drive is running in a secure mode where operators must manually assign mount requests to the drive. AVRD is not scanning

this drive when in this mode. This mode gives operators control over which mount requests can be satisfied.

Applies only to standalone drives.

NO-SCAN

A drive is configured for shared storage option (SSO), but has no available scan host (to be considered available, a host must register with a SSO_SCAN_ABILITY factor of non-zero and have the drive in the UP state). NO-SCAN may be caused if all available scan hosts have the drive in the DOWN state. Other hosts (that are not scan hosts) may want to use the drive, but they registered with a scan factor of zero. The drive is unusable by NetBackup until a scan host can be assigned.

Mixed

The control mode for a shared drive may not be the same on all hosts sharing the drive. For shared drives, each host can have a

different status for the drive. If the control modes are all the same, that mode is displayed.

RESTART

The control mode for a shared drive may not be the same on all hosts sharing the drive. This status indicates that ltid needs to be restarted. To determine what server need to be restarted, right-click the drive in the device monitor and select up. This will tell you what servers that ltid needs to be restarted.