Chapter 5. Setting Up Example 1 on Windows NT
5.5 Installing ADSM Support for the 3995 Optical Library
ANR0400I Session 2 started for node CLIENT <WinNT> <Named Pipe>.
5.5 Installing ADSM Support for the 3995 Optical Library
To use the optical library with ADSM, you must define the device and configure some parameters to Windows NT and to the ADSM server. Before doing these steps, be sure that the library is connected and ready to run.
Attention
The 3995 should be installed by qualified personnel who perform some basic tests to ensure it functions properly. Do not go further before they have done their job.
This section describes how to enable the optical support and define some ADSM objects. Then the optical library is tested to be sure it is working correctly with ADSM. Follow these steps:
1. Open the System Properties program in the Control Panel folder and make a copy of your current hardware profile.
2. Open the Devices program in the Control Panel folder and change the startup options for ADSMSCSI.SYS to BOOT.
3. Start the ADSM Server Utilities program, maximize the Services window, select the Device Driver tab, and click on Options....
4. In the ADSM Device Driver Options windows (Figure 48) check the Enable Optical Device Support option and click on OK.
Figure 48. ADSM Device Driver Options
5. Click on Yes in this warning message:
Figure 49. Enabling Optical Support
Close all programs and restart your system. Now the optical drivers should not show up under the folder My Computer.
Start the ADSM Utilities program and maximize the Services window. The ADSMSCSI service should be running. Start the ADSM server service and maximize the Diagnostics window (Figure 50 on page 69).
Figure 50. ADSM Server Utilities - Diagnostics Window
Remember the parameters of the optical and library ADSM device types.
You will need them later. Table 3 lists the types in our system:
6. Go to the ADSM for Windows NT folder and open the ADSM admin command line window (the user ID is admin) and enter these commands:
• To manage the optical library the ADSM server must have the license for Advanced Device Support. Type:
adsm> register license file(advdev.lic)
• Define the optical library. In our system, we assigned it the name c64lib.
You can choose a different name for your system. The lb6.0.0.2 parameter is from Table 3:
adsm> define library c64lib libtype=scsi device=lb6.0.0.2
• Define a new device class with name c64opt. The mountlimit parameter specifies the maximum number of files that can be simultaneously open for input/output. There are two optical drives in the library, so use a value of 2:
adsm> define devclass c64opt devtype=optical library=c64lib mountlimit=2
• Define the two optical drives. Use the arbitrary names drive1 and drive2.
The other device parameters are from Table 3. The element parameter Table 3. Information f r o m the A D S M Device Detector
Device Type ADSM Device Name ADSM Device Type
OpticalDiskPeripheral op1.0.0.2 OPTICAL
OpticalDiskPeripheral op2.0.0.2 OPTICAL
MediumChangerPeripheral lb6.0.0.2 LIBRARY
specifies the element address of the drive. You must use the values 1 and 2 for the 3995-C64.
adsm> define drive c64lib drive1 device=op1.0.0.2 element=1 adsm> define drive c64lib drive2 device=op2.0.0.2 element=2
• Define a new storage pool with the arbitrary name c64optpool and associated with the c64opt device class we defined before. The maxscratch parameter specifies the maximum number of scratch volumes that can be requested by ADSM. This value can be updated later, so use a value of 3 (for example).
>define stgpool c64optpool c64opt maxscratch=3
7. For the next command, start an MSDOS window, go to the\WIN32APP\IBM\ADSM\UTILS directory, and enter:
dsmlabel -drive=op1.0.0.2,1 -library=lb6.0.0.2 -overwrite -keep
You see this message:ADSTAR Distributed Storage Manager for Windows NT Volume Label Utility Program
Version 3, Release 1, Level 0.1 Licensed Materials - Property of IBM
5639-C59 (C) Copyright IBM Corporation 1994, 1997. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation.
ANR9739I Initializing library device ′LB6.0.0.2′ .
ANR9732I Insert a new volume in the entry/exit port of library ′LB6.0.0.2′ with side A facing up, then enter the name (1-32 characters) to be used for its label; or just press ENTER to quit this program:
This is an utility program to label volumes. Insert a new optical cartridge in the I/O port of the library and write the name you want to assign to this volume (SVT001 in this example):
SVT001
ANR9743I Attempting to label volume ′SVT001′ using drive ′OP1.0.0.2′ . . . ANR9720I Volume ′SVT001′ was labeled successfully using drive ′OP1.0.0.2′ . ANR9732I Insert a new volume in the entry/exit port of library ′LB6.0.0.2′ with side A facing up, then enter the name (1-32 characters) to be used for its label; or just press ENTER to quit this program:
C:\WIN32APP\IBM\ADSM\utils>
With this utility you label the disks to be used in the library. The parameters used are explained as follows:
• -drive=op1.0.0.2,1 is the device name of the optical drive we use to perform the operation.
• -library=lb6.0.0.2 is the device name of the optical library.
• -overwrite changes the label of already labeled volumes. If your cartridges are new, this parameter has no effect.
• With -keep, the inserted volumes stay in the jukebox.
8. After labeling the volumes, you must inform the ADSM server which volumes are available in a library by using the CHECKIN LIBVOLUME command. Go to the ADSM Admin Command prompt and type:
adsm >checkin libvolume c64lib status=scratch search=yes
where c64lib is the name of the optical library we defined before;status=scratch is used to define the volumes as scratch volumes so they can be dynamically added to the storage pools that need a new volume; and search=yes tells ADSM to search the library for all volumes.
ADSM starts a background process. When the process ends, you can verify which cartridges have been checked in by issuing the QUERY LIBVOLUME command, which displays the ADSM inventory of the library (see Figure 51):
adsm> query libvolume c64lib
Library Name Volume Name Status Last Use
--- -- ---
Figure 51. Volumes Checked i n to the Optical Library
9. To back up files directly to optical, you can redefine the BACKUPPOOL storage pool. Enter these commands:
adsm> update stgpool backuppool nextstgpool=c64optpool adsm> update stgpool backuppool access=unavailable
The standard BACKUPPOOL is not available, so the backups must be stored in the next storage pool, C64OPTPOOL.
10. Verify that the process has been successful. Start a backup client session and back up some files so that they are stored in the optical library.