Skip Navigation Links | |
Exit Print View | |
Sun Storage Archive Manager 5.3 Configuration and Administration Guide Sun QFS and Sun Storage Archive Manager 5.3 Information Library |
2. Configuring Storage Devices for Archiving
Task Map: Configuring Storage Devices for Archiving
Adding Tape Devices for Archiving
Files that Contain Configuration Information
How to Add Tape Devices for Archiving (Command Line)
How to Add Tape Drive Interface Target IDs and LUNs for Archiving (Command Line)
How to Add Tape Devices for Archiving (SAM-QFS Manager)
Adding Libraries or Magneto-Optical Drives for Archiving
How to Configure Device Support in SCSI or FC Environments Using SAM-QFS Manager
How to Configure Device Support for a Direct-Attached Library
Recovering After a Direct-Attached Library Fails to Initialize
Verifying and Implementing Configurations
How to Verify That All Devices Are Configured and Implement the Changes
Handling Errors in the st.conf File
3. Performing Additional SAM-QFS Configuration
4. Creating Parameters Files for Network-Attached Automated Libraries
5. Checking the Drive Order in Libraries
7. Managing Automated Libraries and Manually Loaded Drives
8. Managing Vendor-Specific Libraries
11. Archive Directives (archiver.cmd)
12. Archive Set Directives (archiver.cmd)
The inquiry.conf file lists all of the supported devices.
The /kernel/drv/samst.conf file contains a list of SCSI and FC entries and works with the /opt/SUNWsamfs/examples/inquiry.conf file to define the devices that can be included in a SAM-QFS environment.
The following procedures show how to verify the entries in the samst.conf file and to update the file, if necessary.
Update the samst.conf file as follows:
If you have only network-attached automated libraries, you do not need to verify device support or update it.
If you use a SCSI or FC interface to attach a tape library to the server, see How to Configure Device Support in SCSI or FC Environments Using SAM-QFS Manager to discover the tape libraries with the current drive information.
If you have a direct-attached library with a target number larger than 6 or a LUN identifier larger than 1, see How to Configure Device Support for a Direct-Attached Library.
Repeat this procedure for each device in your environment.
The File Systems Summary page appears.
The Tape Library Summary page appears.
When you complete the wizard steps, the samst.conf file is automatically updated.
# cp /kernel/drv/samst.conf /kernel/drv/samst.conf.orig
name="samst" class="scsi" target=target lun=lun;
target is the target ID for each SCSI drive found and lun is the corresponding LUN for each SCSI drive found.
For example, the StorageTek 9730 automated library is attached to target 0 and LUN 0. The following line corresponds to that interface:
name="samst" class="scsi" target=0 lun=0;
Note that some entries might extend over two lines if it includes return characters.
If an entry starts with a hash character (#), remove the character. A hash (#) character marks a line as a comment.
If an entry is missing, create an entry for the SCSI target and LUN line. Follow the format shown in Step 3a and use the information in your hardware inventory list.
Use the following format:
name="samst" parent="fp" lun=lun fc-port-wwn="world-wide-name"
lun specifies the LUN for the drive and world-wide-name specifies the WWN for the drive.
The following example shows the line added to support the StorageTek L700 tape drive in Table 2-1.
name="samst" parent="fp" lun=0 fc-port-wwn="500104f00041182b"
A direct-attached library may fail to initialize after an ENOENT error while trying to open a samst device. The example below shows how to exclude a STK SL500 library so that the samstsamst device binds as needed at mount time. Add lines similar to the following to the /kernel/drv/scsi_vhci.conf file, replacing STK SL500 with the string for the type of library that you are using:
# device-type-scsi-options-list = "STK SL500", "disable-option"; disable-option = 0x7000000;
For more information, see the scsi_vhci(7D) man page.