STK Libraries Attached to ACSLS Server

Topics | Configure | How To | Related Topics

Overview

• Supported Software Versions
• Firewall Considerations

Configuring STK Libraries Attached to ACSLS Server

Configuring STK Libraries with Multiple Library Storage Modules (LSM)

Best Practices for STK Libraries Attached to ACSLS Server

License Requirement

Overview

StorageTek libraries controlled by an ACSLS Server can be configured. Such ACSLS controlled StorageTek libraries can be shared between:

• Multiple MediaAgents in a CommCell^® group
• Multiple CommCell groups, or
• CommCell groups and others applications like Vault 98, etc.

Note that the ACSLS server computer can also be a component (either a MediaAgent or an agent) of the CommCell group. The system can share a StorageTek (STK) library with Vault98 or other applications that are accessing the STK library via ACSLS server.

Supported Software Versions

The following software versions are supported in the various components:

Firewall Considerations

If the ACSLS Server and the MediaAgent computer are located on the opposite sides of firewall(s), additional ports required by the ACSLS Server, may have to be opened on the firewall(s). For more information on the necessary software and required ports, refer to STK -ACSLS documentation.

On Windows, the firewall should be configured using the Library Attach for Windows software. On Solaris install the ACSLS Client Service as described in Install ACSLS Client Service on Solaris. Follow the steps described in the Post-Install Considerations section of the above procedure to configure communication across a firewall.

Configuring STK Libraries Attached to ACSLS Server

Within a CommCell, depending on the environment, the MediaAgents can be configured to access the StorageTek library controlled by an ACSLS Server using one of the following configurations:

• Direct-attached library configuration
• Dynamic Drive Sharing (DDS) configuration in the SAN environment

In both the cases you can also have storage virtualization hardware, such as StorageTek SN6000.

The following links provide step-by-step instructions on configuring the STK library attached to an ACSLS server.

• Direct-attached Library Configuration (with or without SN6000)
• DDS Configuration (with or without SN6000)

Configuring STK Libraries with Multiple Library Storage Modules (LSM)

Libraries, such as STK SL 8500 have Library Storage Modules (LSMs). Each of these LSMs have robots on rails. Tape cartridges can be passed between each of these LSMs through pass through ports or elevators. (For detailed information on this library refer to STK documentation for the library.)

Although the entire library can be configured as a single library, to obtain optimal benefits it is recommended that each of these LSMs be configured as a logical library. This would avoid performance issues due to elevator traffic, allow for parallel robot activity and minimize the impact of a single robot failure.

The following link provides step-by-step instructions on configuring an STK library with multiple LSMs:

• Configuring STK Libraries with Multiple LSMs

Best Practices for STK Libraries Attached to ACSLS Server

• All regular library operations are supported.
• Shared ACSLS library configuration, with or without library controllers, is supported for multiple MediaAgents using different drive pools.
• During configuration, make sure to map the drive serial number to its corresponding drive ID.

  If necessary, use the following command on the ACSLS Console to display the drives and its corresponding serial number:

  display drive * -f serial_num

  This would display results similar to the following:

  2007-01-27 13:57:01 Display Drive

  Acs   Lsm   Panel    Drive Serial_num

  0     0     2        0     CX803S1909

  0     0     2        1     CX803S1939

  0     0     2        2     CX803S1959

  0     0     2        3     CX803S1979

  0     0     2        4     CX803S2259

• It is recommended that you use the exhaustive detection operation during library and drive configuration process. This will ensure that the drive serial numbers and the corresponding drive IDs are accurately mapped in the MediaAgent.
• It is recommended that the media used by the MediaAgent in the library has a specific prefix in the barcode. (e.g., SL0001, SL0002, etc.) This way you can add the entire Volume Range (SL0001-SL9999) to the scratch pool.

  If this is not possible, and if media is imported directly into the library, without using the CommCell Console, you must specify the volume range in the Library and Drive Configuration window. (See Add Volume Ranges for step-by-step instructions.)

  Whenever you import media verify and ensure that the media barcodes are within the volume range specified in the Library and Drive Configuration window. If they are outside the specified volume range, include them as described in Add Volume Ranges. If this is not done, the media available in the library will not be synchronized with the CommServe database and at some point such media may appear as exported in the CommCell Console. In such a situation, you can either add the appropriate media into the scratch pool or perform a Full Scan on the library.

• If you have multiple mail slots in the library, specify the CAP ID associated with the mail slot that will be used for importing and exporting media used by the MediaAgent. If necessary, you can also change the CAP ID if the specified CAP is busy. (See Specify the CAP ID for Importing and Exporting Media for step-by-step instructions.)
• If you notice that the library did not perform a certain operation for a long time, check the ACSSA to verify that a pending user action is completed. For example, while importing media from the CommCell Console, ensure that the media is promptly inserted and the mail slot closed.
• Avoid performing library and drive operations concurrently from both the CommCell Console and ACSSA. If you notice that a command requested by the CommCell Console did not queue successfully in ACSSA, or if you encounter problems with the subsequent operations, reset the library from the CommCell Console.

• If you have configured a library using SN6000, it is recommended that you allocate the number of drives in the Drive Allocation Policy to the number of physical drives in the library. For example, if you have 5 physical drives in the library, and you have virtualized it using SN6000 to 10 drives, set the number of drives in the Drive Allocation Policy to 5. For step-by-step instructions on how to allocate drives in a drive allocation policy, see Set the Maximum Number of Drives for each Drive Pool in a Master Drive Pool.

• Considering the following tips when you want to manage drive cleaning jobs from the CommCell Console:
  • Verify and ensure that the drive cleaning function is OFF in the STK library configuration. (not in the CommCell Console)
  • Do Not use STK cleaning barcode labels (e.g., CLNxxx) if the library does not accept them as scratch tapes. Instead they should be included in the ACSLS working pool.

    You can then Import, Discover, or Move them into Cleaning Media pool from the CommCell Console, in the same way that it is done for regular tape libraries.

• If the media is available in the library and for some reason shown as exported in the CommCell Console, use the Set Scratch command to move it back to the appropriate media pool. This may happen, if you performed a stuck tape recovery operation (without using the CommCell Console) or re-imported a media without using the Import command from the CommCell Console. (See Move a Media using the Set Scratch option for step-by-step instructions.)
• To detect the cleaning media in the library enable the List ACSLS Clean Media option in the Library Properties dialog box. (See Display Cleaning Media in the CommCell Console for step-by-step instructions.) Once enabled the cleaning cartridge available for the library's own cleaning function will be displayed in the Media in Library pool in the CommCell Console.

  Note that when you enable this option the library must be reset  for the cleaning media to appear in the CommCell Console.

  Also this option should be enabled  only in one of the configured libraries. For example, you have configured each scratch pool (from one physical library ) as a CommCell library. Enable this option in any one of the configured libraries.

  To automatically detects new drives if they were swapped or replaced, enable the Use Drive ID for Drive Replacement in the Library Properties dialog box. (See Automatically Detect Replaced Drives for step-by-step instructions.)  Enable this option in ACSLS Server / libraries that support a serial number for each drive ID. Type the following command in the ACSLS Console to show the serial number for all drives:

  display drive * -f serial_num

  The system will display both the drive ID  and the serial number if it is supported. If it is not supported only the drive ID will be displayed.

License Requirement

This feature requires a Feature License to be available in the CommServe^® Server.

Review general license requirements included in License Administration. Also, View All Licenses provides step-by-step instructions on how to view the license information.

Back to Top