ACSLS 8. This is an issue for Solaris zoned environments. Because such device drivers are attached to the system kernel, they must reside in the global zone. The product has been successfully installed to execute in the below ascribed operating environment. It has been demonstrated to provide its basic functionality without detriment to either the product or the associated execution environment. Swap: Today's systems with Solaris
|Country:||Turks & Caicos Islands|
|Published (Last):||10 September 2014|
|PDF File Size:||18.81 Mb|
|ePub File Size:||14.67 Mb|
|Price:||Free* [*Free Regsitration Required]|
Direct-attached Library Configuration with or without SN Make sure that the designated scratch pool contains all the media that will be used by the MediaAgent. Move the necessary tapes into this scratch pool or use the Volume Range in the Library Properties to add the necessary tapes.
Volume Range is explained in the following procedure. This service can be installed in one of the following ways: During the MediaAgent software installation on the Solaris computer. Review general license requirements included in License Administration. Also, View All Licenses provides step-by-step instructions on how to view the license information. Display the Library and Drive Configuration window. Detect the devices that are controlled by MediaAgents that will access the library as described in Detect Devices.
The system detects the drives and displays them as a standalone library in the Library and Drive Configuration window. If you have SN attached, the host name of SN Volume Range : The ascending barcode range s of volumes available in the specified work pool.
Use a dash to specify range and commas to delimit ranges. For example: ,, Description : An optional field into which you can enter a description for the library.
The system detects the library and displays the library information in the Library and Drive Configuration window. If you want to modify the library properties, right-click the library and select Properties. From the Library Properties dialog box, you can change the following properties: Alias : The user-defined name for the library. This name is displayed in the CommCell Console for the library.
We recommend that you give each library a descriptive name as its Alias, for easier system administration. When you are satisfied with your changes, click OK. The devices are displayed in the library tree with detection status not configured, detect success in the Library and Drive Configuration window. This will ensure that the drives are mapped to the appropriate serial number. If necessary, use the following command on the ACSLS Console to display the drives and its corresponding serial number:.
NOTES As this process attempts to mount a media in each of the selected drives to determine the drive numbers to its correct serial number, depending on the number of drives selected, this operation may take some time to complete. Right-click the drive and then click Properties. Configure the library as described in Configure Devices.
The devices are displayed as configured, detect success. NOTES :You can validate the physical drive configuration by selecting Validate, from the drive, drive pool or library level. The Data Paths tab provides a logical view of the data path used to access the devices - library, master drive pool, drive pool, drive. Post Configuration Considerations If you have multiple mail slots in the library, you must specify the CAP ID associated with the mail slot that will be used for importing and exporting media.
If you have configured a library using SN, 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 SN to 10 drives, set the number of drives in the Drive Allocation Policy to 5.
This MediaAgent is referred to as the primary MediaAgent in this section. Follow steps in Direct-attached Library Configuration with or without SN to configure the library and drives in the primary MediaAgent. Once the library is configured, the Library and Drive Configuration window will display a setup similar to the following: 4.
Select the following MediaAgents:. Due to the unique nature of this library, the goal of this configuration is to eliminate the sharing of resources across LSMs. In order to do this, each LSM is configured as a logical library. The following procedure describes the steps involved in configuring a LSM as a virtual library. Repeat this procedure to configure all the LSMs in the library.
If the system detects the drives and displays them as a standalone library in the Library and Drive Configuration window, perform the steps described in Configuring Drives Displayed as Stand-Alone Drives. Alias : The user-defined name for the library. When a library is configured, the system automatically creates a storage policy.
In the case of libraries with multiple LSMs, a storage policy will be created for each of the LSMs configured as a library. The advantages to this configuration method is that when there is failure in any one of the LSMs , data protection operations will automatically use the resources in the other LSM.
Thus this configuration minimizes the impact of a robot failure in any one of the LSMs. In addition only one storage policy must be configured and maintained resulting in easier administration. Note that data may get scattered across several tape cartridges within the library. However, the system can keep track of all the data and automatically restore data from the appropriate tape cartridge.
In addition the MediaAgent software provides several methods to reconsolidate the data. However, keep in mind that you must configure and maintain multiple storage policies in this method.
As we are configuring a library for each LSM, make sure to specify the appropriate work pool number associated with the LSM. Verify the drive serial number and obtain the corresponding drive ID, before selecting the drive ID in this dialog box. As this process attempts to mount a media in each of the selected drives to determine the drive numbers to its correct serial number, depending on the number of drives selected, this operation may take several minutes to complete.
Solaris Pre-configuration tasks in SN if available Ensure the following using the SN interface: Verify that the drives in the library are visible and configured. Mount Queuing is disabled. Install one of the following software on a Windows or Solaris MediaAgent that will act as the library controller. To configure failover library controllers, install the following software on multiple MediaAgents that will act as failover library controllers.
Library Type : The IP library type. Vendor : The manufacturer of the library. STK Model : The library model. When you are finished, click OK.
Select the most likely drives or all the available drives in the Select Drive IDs dialog box. If you have multiple mail slots in the library, you must specify the CAP ID associated with the mail slot that will be used for importing and exporting media. Once the library is configured, the Library and Drive Configuration window will display a setup similar to the following:. The system detects the drives and automatically displays them with the DDS setup in the Library and Drive Configuration window.
Configure the Master Drive Pool. Make sure that the drive pool and drives are configured. Ensure that all volumes moved into each scratch pool reside in their respective LSMs. Detect the devices as described in Detect Devices. Do not perform an Exhaustive Detection now. Perform the following steps, if you are configuring the library with DDS. Consider the following after configuring all the LSMs as a virtual library: Creating Storage Policies Recommended Method When a library is configured, the system automatically creates a storage policy.
Use one of these storage policies and associate all the subclients using the library to this storage policy. Add the data paths for each LSM in the library as alternate data paths in this storage policy. Also, Configure Multiple Data Paths for a Storage Policy Copy provides step-by-step instructions on how to configure alternate data paths. Other Methods Configure all the storage policies associated with each of the LSMs with alternate data paths in each of these storage policies.
These alternate data paths must point to all other MediaAgents that have visibility to the drives in that LSM. Make sure to set the criteria for selecting alternate data paths as When resources are busy or offline. Load balance Spill and fill between Data Paths is applicable only in the case of load balancing. The advantage to this method is that data associated with each storage policy will be limited to the LSM to which the storage policy is associated.
Data is less scattered than in the previous method. Configure all the storage policies associated with each of the LSMs with no alternate data paths. Perform the following steps if the system detects the drives and displays them as a standalone library in the Library and Drive Configuration window, as shown in the sample image.
In the Move to the Empty Drive Slot dialog box click the drive number to which you wish to move the standalone drive. Click Yes in the confirmation prompt for moving the drive to the empty slot. Repeat steps 8 to 11 to move all other associated stand-alone drives to the appropriate drive slots in the library tree.
Repeat steps 14 to 15 for all the drives within each LSM in the library. If you are not sure of the drive serial number and drive ID mapping, then perform an exhaustive detection of the devices at the Library Controller level. NOTES As this process attempts to mount a media in each of the selected drives to determine the drive numbers to its correct serial number, depending on the number of drives selected, this operation may take several minutes to complete.
STK Libraries Attached to ACSLS Server - Configure
ACSLS 8. Other operating systems, including virtual environments, are not tested or supported. This is an issue for Solaris zoned environments. Because such device drivers are attached to the system kernel, they must reside in the global zone. Logical libraries are not supported on the Linux operating system.
Automated Cartridge System Library Software 8.2