About plug and play – HP StoreEver Ultrium Tape Drives User Manual
Page 15
3.
Click on the Command View TL TapeAssure Drives Health tab and verify that the drive serial
number appears in the list.
If the backup application does not unload the tape at the end of the backup, you may need to wait
until the first timed ticket is pulled. This could be up to six hours, depending on the
POLLING_INTERVAL
specified in the TapeAssure service configuration.
Another option is to check for the initial tape drive ticket entry in a Command View TL das_0.log
lo file:
1.
Open the file C:\Program Files\Hewlett-Packard\Command View TL\log\das_0.log
in a text editor, such as Notepad.
2.
When a drive first connects to a server running the TapeAssure service, or the service is first
started with a drive connected, a ticket is immediately pulled from that drive and sent to the
Command View TL IP address as specified in the configuration file. Because there was not a tape
loaded, that ticket will not have a full set of data, and so Command View TL will not use it.
Command View TL does record the receipt of the initial ticket in the das_0.log file, which you
can view:
NOTE:
For a full set of installation checks, see
About plug and play
If a drive is connected or removed, it can take about five minutes for TapeAssure to readjust the list
of drives that it is monitoring. System behavior depends on the type of drive interface:
•
SCSI drives do not always respond correctly in a plug and play environment. When you make
changes, perform a rescan in Windows Device Manager.
•
SAS and Fibre Channel drives often respond more promptly. TapeAssure monitoring should adjust
quickly within one to two minutes.
Generally speaking, if the backup application or L&TT can communicate with the drive, the TapeAssure
service will be monitoring it.
User guide
15