Executing robtest to test a tape drive installed on a media server, that is not the media server where the

con... Page 1 of 3

Document ID: 188520 http://support.veritas.com/docs/188520 E-Mail this document to a colleague Executing robtest to test a tape drive installed on a media server, that is not the media server where the controlling robot and the other tape drives controlled by the robot, are installed. Details: It is possible to test the functionality of a tape drive installed on a media server that is remote from the media server where the controlling robot is installed. Generally, this test consists of the following operations: loading a tape from a slot in the robot into a drive, unloading the tape from the drive, and finally, moving the tape back to the slot. In the following example robtest is executed from the master server, xenon. There are two robots installed on xenon. Robot TLD(0) controls seven tape drives. Six of these tape drives are configured for use by NetBackup and one is left out. Of the six NetBackup drives, four are physically attached, via scsi cable, to master/media server xenon. One drive is physically attached to media server harpo1. One drive is physically attached to media server harpo2. Notice that only the four drives physically attached to xenon appear in the argument list to tldtest when robtest is run: xenon:/usr/openv/volmgr/bin# ./robtest Configured robots with local control supporting test utilities: TLD(0) robotic path = /dev/sg/c2t0l0 TLD(1) robotic path = /dev/sg/c1t0l0 Robot Selection --------------1) TLD 0 2) TLD 1 3) none/quit Enter choice: 1 Robot selected: TLD(0) robotic path = /dev/sg/c2t0l0 Invoking robotic test utility: /usr/openv/volmgr/bin/tldtest -r /dev/sg/c2t0l0 -d1 /dev/rmt/0cbn -d2 /dev/rmt/1cbn -d3 /dev/rmt/2cbn -d4 /dev/rmt/3cbn The tape drive installed on the media server harpo1 does not appear in the argument list to tldtest and neither does the tape drive installed on harpo2. As it happens, each of the tape drives installed on the other media servers is accessed on the media server host via the device path /dev/rmt/0. This is known from running "xdevadm" on the master server, then clicking on hosts->monitor->"name of the media server host to monitor" ( in this example harpo1 and then harpo2). In the "Device Configuration" box, the device path to the drive appears to the right of the drive information as it is listed in the box, indented beneath the information for the robot that controls the drive. The device path information is necessary to execute the "mt" command on each of the media servers to unload the tape after a tape has been moved from a slot into the drive, under robtest control. In this example, even though the drives on harpo1 and harpo2 do not appear in the argument list to tldtest (and do not appear if the "s d" command is issued under robtest), they each can be accessed by

file://H:\study\netbackup\Upload_site_done\done\New Folder\Executing_Robtest_from a media server but n... 7/6/2010

Executing robtest to test a tape drive installed on a media server, that is not the media server where the con... Page 2 of 3

using the next two higher drive identifiers (i.e d5 and d6) above the highest drive identifier (i.e. d4) in the argument list to tldtest. To test these drives, first access the drive from robtest on xenon by moving a tape from a full slot to the drive: s s (show slots to see which has a tape in it) slot 1 (addr 1) contains Cartridge = yes Source address = 1 slot 2 (addr 2) contains Cartridge = yes Source address = 2 slot 3 (addr 3) contains Cartridge = yes Source address = 3 slot 4 (addr 4) contains Cartridge = yes Source address = 0 slot 5 (addr 5) contains Cartridge = yes Source address = 5 slot 6 (addr 6) contains Cartridge = yes Source address = 6 slot 7 (addr 7) contains Cartridge = yes Source address = 7 slot 8 (addr 8) contains Cartridge = yes Source address = 8 slot 9 (addr 9) contains Cartridge = yes Source address = 0 slot 10 (addr 10) contains Cartridge = yes Source address = 10 READ_ELEMENT_STATUS complete m s1 d5 (move a tape from slot 1 or any full slot to drive 5 or d6) Initiating MOVE_MEDIUM from address 1 to 4 MOVE_MEDIUM complete Which server, harpo1 or harpo2 ends up having a tape moved to the drive physically attached to it, is empirically determined by visual inspection of the drive on each media server. Whichever media server is found to have a tape loaded into its drive, log into that media server to execute the following magnetic tape command: mt -f /dev/rmt/0 rewoffl Remember that the device path to the tape drive will vary depending on what path, executing "xdevadm" on the master server, displayed for that media server. As a result of executing this command on the media server, one should observe that the tape rewinds in the drive, and then is put off line. For tape drives installed on media server hosts remote from the host where the controlling robot is installed, the tape rewind and unload must be performed from the remote media server and cannot be performed from the media server where the robot is installed and robtest is run. Once the tape is rewound and unloaded from the remote media server, it can then be moved back to its slot via robtest running on the media server where the robot is installed:

file://H:\study\netbackup\Upload_site_done\done\New Folder\Executing_Robtest_from a media server but n... 7/6/2010

Executing robtest to test a tape drive installed on a media server, that is not the media server where the con... Page 3 of 3

m d5 s1 Initiating MOVE_MEDIUM from address 4 to 1 MOVE_MEDIUM complete

Products Applied: NetBackup v3.2 and prior (UNIX Platforms) 3.1.1, 3.2 Last Updated: June 14 2000 07:13 PM GMT Expires on: 365 days from publish date Subscribe to receive critical updates about this document Subjects: NetBackup v3.2 and prior (UNIX Platforms) Application: Configuration, How To, Media Management, Verify Languages: English (US) Operating Systems: Solaris 2.4, 2.5, 2.5.1, 2.6, 7.0 (32-bit) Symantec World Headquarters: 20330 Stevens Creek Blvd. Cupertino, CA 95014 World Wide Web: http://www.symantec.com/, Tech Support Web: http://entsupport.symantec.com/, E-Mail Support: http://seer.entsupport.symantec.com/email_forms, FTP: ftp://ftp.entsupport.symantec.com/ or ftp://ftp.entsupport.symantec.com/
THE INFORMATION PROVIDED IN THE SYMANTEC SOFTWARE KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. SYMANTEC SOFTWARE DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SYMANTEC SOFTWARE OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,EVEN IF SYMANTEC SOFTWARE OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

file://H:\study\netbackup\Upload_site_done\done\New Folder\Executing_Robtest_from a media server but n... 7/6/2010

Sign up to vote on this title
UsefulNot useful