> Expert > Storage > Libraries > Tape Libraries > Tape Library Types > SAN-Attached Libraries

SAN-Attached Libraries - Troubleshooting

Updated

Unable to detect devices in Solaris

To attach the WA drivers when the library is attached to FC HBA

  1. Ensure that the tape devices are visible to the Solaris kernel.

    You can do this using the following commands:

    Run cfgadm -al
    

    grep/look for type as tape devices

    Note

    If (cfgadm \-al) displays all the devices configured on system, look for the word tape to identify tape devices.

    For example, the output of the cfgadm -al command may be as follows:

     
    Ap_Id                   Type          Receptacle          Occupant          Condition
    
    

    c0                     scsi-bus       connected           configured        unknown
    

    c0::dsk/c0t0d0         disk           connected          configured         unknown
    

    c0::dsk/c0t10d0        disk           connected          configured         unknown
    

    c0::dsk/c0t6d0         CD-ROM         connected          configured         unknown
    

    c0::dsk/c0t8d0         disk           connected          configured         unknown
    

    c0::dsk/c0t9d0         disk           connected          configured         unknown
    

    c3                     scsi-bus       connected          unconfigured       unknown
    

    c6                     fc-fabric      connected          configured         unknown
    

    c6::100000d08000167d   tape           connected          configured         unknown
    

    c6::100000d080001986   tape           connected          configured         unknown
    

    c6::100000e00221b69    array-ctrl     connected          unconfigured       unknown
    

    c6::100000e00221d909   disk           connected          unconfigured       unknown
    

    c6::2100002037194c51   disk           connected          configured         unknown
    

    c6::210000203719599e   disk           connected          configured         unknown
    

    c7                     fc             connected          unconfigured       unknown
    

    c8                     fc             connected          unconfigured       unknown

    If you do not see the devices as shown in the above example, make sure that the devices are visible to the Solaris kernel before proceeding any further.

  2. If you see the tape devices, as shown in the above example, run the following script:

    <software installation path>/WA/wa_sunqlc_add

    After running the script, you will be able detect the devices from the Expert Storage Configuration window.

To attach the WA drivers when the library is attached to FC HBA with a storage router

  1. Ensure that the tape devices are visible to the Solaris kernel.

    You can do this using the following commands: 

    Run cfgadm -al
    

    grep/look for type as array-ctrl

    For example, the output of the cfgadm -al command would be as follows:

    c6::100000e00221b691 array-ctrl  connected    unconfigured  unknown

    If you do not see the devices as shown in the above example, make sure that the devices are visible to the Solaris kernel before proceeding any further.

  2. If you see the array-ctrl as shown in the above example, you will have to add the necessary information in the following file: 

    /usr/kernel/drv/wa.conf

  3. Add the necessary entries using the following pattern to add each device. 

    name="wa" parent="fp" target=16 lun=0 fc-port-wwn="WWPN"

    Using the above example, it will be as follows: 

    name="wa" parent="fp" target=16 lun=0 fc-portwwn="100000e00221b691"

    Add 8 entries from lun=0-7

    Example:

    name="wa"   parent="fp"   target=16   lun=0   fc-port-wwn="100000e00221b691";
    

    name="wa"   parent="fp"   target=16   lun=1   fc-port-wwn="100000e00221b691";
    

    name="wa"   parent="fp"   target=16   lun=2   fc-port-wwn="100000e00221b691";
    

    name="wa"   parent="fp"   target=16   lun=3   fc-port-wwn="100000e00221b691";
    

    name="wa"   parent="fp"   target=16   lun=4   fc-port-wwn="100000e00221b691";
    

    name="wa"   parent="fp"   target=16   lun=5   fc-port-wwn="100000e00221b691";
    

    name="wa"   parent="fp"   target=16   lun=6   fc-port-wwn="100000e00221b691";
    

    name="wa"   parent="fp"   target=16   lun=7   fc-port-wwn="100000e00221b691";

  4. Save the changes.

  5. Stop the services on the MediaAgent in which the entries were added.

  6. Execute the following commands to create the device nodes: 

    rem_drv wa
    

    add_drv wa

  7. Start the services in the MediaAgent in which the entries were added.

    You will now be able detect the devices from the Expert Storage Configuration window.

To scan devices with LUNs greater than 7

By default the MediaAgent scans for devices with LUNs 0-7. If the devices are over these values they will not be detected. Perform the following steps to correct this problem:

  1. Edit the following file:

    \/usr\/kernel\/drv\/wa.conf

  2. Add an additional line across all targets to add a specific LUN. For example, to add LUN 8 and assuming that you have one target - Target 0 - you need the following line:

    name="wa" class="scsi" target=0 lun=8;

MA0004: Job or Drive Validation Failures in Solaris MediaAgents Using SCSI3 reservation for Native (st) or WA Drivers

Symptom

Backup or drive validation jobs might fail on Solaris MediaAgents when using st or WA drivers and SCSI3 reservations.

Native st driver is opened while using native or WA driver for data transfer to prevent possible corruption of data. By default, tape driver on Solaris uses SCSI-2 reserve/release. When the native drivers are utilized, they conflict with the SCSI-3 reserve/release done by the MediaAgent and the data protection operations wait indefinitely.

Resolution

To allow Commvault software to control tape device reservations, perform the following steps:

  1. Confirm that the st driver is bound to the connected drives through /var/adm/messages log.

    • If the drives are not bound to the st driver in the message log, go to step 2.

    • If the drives are bound to the st driver in the message log, go to step 6.

    Example of a library with two drives of like model type:

    Note: IBM ULTIUM-TD7 drives are bound to st27 and st28 in the image.

    lib_examples

  2. To configure st tape drive support on Solaris, the st device nodes should be added to /kernel/drv/st.conf and bound to all the tape drive LUNs which are to be used.

    Note: Create a copy of the st.conf file prior to any edits. Confirm this file retains its original permissions and owner/group definitions if copied back into place.

    lib_example01a

    If not already present, add the following lines in /kernel/drv/st.conf to bind tape drives with native st driver.

    name="st" class="scsi" target=0 lun=0;
name="st" class="scsi" target=1 lun=0;
name="st" class="scsi" target=2 lun=0;
name="st" class="scsi" target=3 lun=0;
name="st" class="scsi" target=4 lun=0;
name="st" class="scsi" target=5 lun=0;
name="st" class="scsi" target=6 lun=0;
name="st" class="scsi" target=7 lun=0;
#
#In case of wide tape drives, use these targets
#
name="st" class="scsi" target=8 lun=0;
name="st" class="scsi" target=9 lun=0;
name="st" class="scsi" target=10 lun=0;
name="st" class="scsi" target=11 lun=0;
name="st" class="scsi" target=12 lun=0;
name="st" class="scsi" target=13 lun=0;
name="st" class="scsi" target=14 lun=0;
name="st" class="scsi" target=15 lun=0;

  3. Reload the st driver using the following commands: 

    rem_drv st
add_drv st

  4. Confirm that the drives are bound to st driver in the /var/adm/messages log.

  5. Update the SCSI class information for each driver with the following commands: 

    update_drv -a -i "scsiclass,01" st 
 update_drv -a -i "scsiclass,08" sgen 
 add_drv -i "scsiclass,01 scsiclass,08" wa

  6. Run the following script to configure all the fibre channel devices using the WA driver.

    Note: The WA driver must be configured for all the devices, even if st driver is intended for tape device operations. Commvault software uses the WA driver to control the Medium Charger for libraries or Auto Loaders on Solaris MediaAgents. 

    software_installation_path/WA/wa_sunqlc_add

  7. Run the ScanScsiTool found in the <software installation path>/Base folder to obtain the native path for each drive type connected.

    Example of ScanScsitool output for a library and two like model drives:

    lib_example01

  8. Run ScanScsiTool with –T and [native path] of drive.

    For example:

    lib_example02

    Note: The output of the ScanScsiTool with –T and [native path] of each drive type will be required if the library has mixed drive types, or there are several libraries with different drive types attached to the Solaris MediaAgent.

  9. Use the output of the ScanScsiTool with –T and [native path] to create or update the tape-config-list in the st.conf file as described in the examples.

    Note: Create a copy of the /kernel/drive/st.conf file prior to any edits. Confirm this file retains its original permissions and owner/group properties if copied back into place.

    lib_example01a

    st.conf file format for a single drive model type environment:

    Note: Every entry in the st.conf file follows the below format. Any spaces in the Vendor field must be kept so that it is 8 characters long. Trailing spaces in the Product ID field can be removed. (Example: "|-VID--||-----PID------|")

    tape-config-list="VENDOR Product ID", "A Prettier Name to Display", "Config-Name";
Config-Name = config information;

    Take notice of the required semicolon (;) at end of each line.

    Example of values defined for single drive model type environment using output from Step 8: 

    VENDOR Product ID = IBM ULTRIUM-TD7 
A Prettier Name to Display = IBM ULTRIUM-TD7 
Config-Name = CFGIBMULTRIUMTD7
config information = 2,0x3B,0,0x1038619,4,0x5A,0x5A,0x5C,0x5C,3,60,1500,600,2040,780,780,24600

    Example of st.conf file entry:

    lib_example02a

    st.conf file format for a mixed drive type environment:

    tape-config-list="VENDOR Product ID1", "A Prettier Name to Display1", "Config-Name1", "VENDOR Product ID2", "A Prettier Name to Display2", "Config-Name2", "VENDOR Product ID3", "A Prettier Name to Display3", "Config-Name3", "VENDOR Product ID4", "A Prettier Name to Display4", "Config-Name4";
Config-Name1 = config information1;
Config-Name2 = config information2;
Config-Name3 = config information3;
Config-Name4 = config information4;

    Take notice of the required semicolon (;) at the very end of the tape-config-list as well as after each defined Config-Name with config information entry.

    Example of st.conf file example for mixed drive model type environment:

    lib_example03

  10. Reboot the Solaris OS.

Backup jobs from Windows 2003 computers fail in the SAN environment

Resolution

Create the AutoRunAlwaysDisable registry key on all Windows 2003 computers that have access to the library in the SAN environment. For a detailed description of this problem and the registry key refer to the following article published in the Microsoft web site:

http://support.microsoft.com/default.aspx?scid=kb;en-us;842411&Product=w

ScsiCmd tool

The ScsiCmd Tool is used to test whether the hardware supports SCSI-3 reservation. (SCSI-3 reservation is used when you enable the Use SCSI Reserve for contention resolution option in the Library Properties dialog box.) This tool is installed along with the MediaAgent software and available on all the MediaAgent computers.

For comprehensive information on using ScsiCmd Tool, see ScsiCmd Tool.