HP LTO Ultrium 4 drives technical reference manual, volume 2: software integration 89
HP restricted
5. Optionally, automate the recommended recovery actions if there are multiple tape drives or
autoloaders present.
For example, the application could perform a cleaning cycle in response to flags 20 (Clean
Now) and 21 (Clean Periodic). It could perform a tape copy for flags 4 (Media performance
degraded) and 7 (Media life expired), and then retire the suspect tape cartridge.
This provides an opportunity for applications to add value to the TapeAlert capability of the
drives.
NOTE: An application must not fail a backup job as a result of TapeAlert information. It should use
the information as a preventative measure, taking action to avoid failure, or encouraging the user to
take action. It should also retain the log information to help in diagnosis if a job does eventually fail.
One-Button Disaster Recovery (OBDR)
NOTE: FC drives and drives in libraries do not support OBDR.
All HP Ultrium parallel-SCSI products support HP’s One-Button Disaster Recovery (OBDR)
technology. This provides the fastest possible, one-step approach to regenerating a single server
without using additional floppy disks or CD-ROMs.
For a general overview, see “OBDR and CD-ROM Emulation” in Chapter 1, “Ultrium Features”, of
Background to Ultrium Drives, Volume 6 of the HP Ultrium Technical Manual. For details of the SCSI
implementation, see “CD-ROM Emulation” in Chapter 1, “Interface Implementation”, of SCSI
Interface, Volume 3 of the HP Ultrium Technical Manual.
For details of how to use OBDR see the appropriate User’s Guide.
To identify whether the firmware supports OBDR, look for the string “$DR-10” in bytes 43–48 of
the Inquiry data.
Supporting OBDR
The OBDR implementation in HP Ultrium drives is functionally identical to that in DAT/DDS, so no
additional design or coding should be required in order to support it. The only effort needed should
be in software testing.
Responding to the ‘Clean’ LED
NOTE: HP recommends that software applications use the TapeAlert log, which should mean that
potential tape or cleaning problems are flagged and corrected before the drive ever reaches the
point of displaying the ‘Clean’ LED.
If during normal operation, the drive detects an excessive number of RWW retries, the ‘Clean’ LED
is lit. If this happens, a user should follow this procedure:
