Tivoli Storage Manager for Windows: Administrator's Guide


|Replacing Tape or Optical Drives

| | | | | | |

|If you replace a drive in a tape or optical library that is defined to |Tivoli Storage Manager, you must delete the drive definition for the old drive |and define the new drive. This is required even if you are exchanging |one drive for another of the same type, using the same logical address, |physical address, SCSI ID, and port number. Device alias names can |change when you change your drive connections.

|If the new drive is an upgrade that supports a new media format, you might |also need to define a new logical library, device class, and storage |pool. Procedures for setting up policy for a new drive in a |multiple-drive library will vary, depending on the types of drives and media |in the library.

|This section provides a general overview of media compatibility and |describes how to replace a drive, set up policy to handle multiple media |formats in the same library, and migrate previously stored data to new |media.

|Overview of Media Compatibility Issues

|Sometimes a new drive has a limited ability to use media formats supported |by a previous version of the drive. Often, a new drive can read but not |write to the old media. By default, existing volumes with a status of |FILLING will remain in that state after a drive upgrade. In some cases, |you might want to continue using an older drive to fill these volumes. |This will preserve read/write capability for the existing volumes until they |have been reclaimed. If you choose to upgrade all of the drives in a |library, pay attention to the media formats supported by the new |hardware. Unless you are planning to use only the latest media with |your new drive, you will need to be aware of any compatibility issues. |For migration instructions, see Migrating to Upgraded Drives.

|To use a new drive with media it can read but not write to, you should use |the UPDATE VOLUME command to set the access for those volumes to |read-only. This will prevent errors caused by read/write |incompatibility. For example, a new drive may eject media written in a |density format it does not support as soon as the media is loaded into the |drive. Or a new drive may fail the first write command to media |partially written in a format it does not support.

|When data on the read-only media expires and the volume is reclaimed, you |should replace it with media that is fully compatible with the new |drive.

|Errors can be generated if a new drive is unable to correctly calibrate a |volume written using an older format. To avoid this problem, ensure |that the original drive is in good working order and at current microcode |levels.

|Removing a Drive

|

|Remove the old drive and install the new one
|Stop the TSM server and shut down the operating system. Remove the |old drive and follow the manufacturer's instructions to install the new |drive.

|Delete the current drive definition

|Restart the operating system and the TSM server. You must use |commands to delete and redefine drive definitions. The Device |Configuration Wizard does not support this task.

|For example, to delete a drive named DLT1 from a library device named LIB1, |enter:

|delete drive lib1 dlt1

|You must then define the new drive. This procedure will vary, |depending on the configuration of drives in your library. See Defining a New Drive. |

|Defining a New Drive

|How you define a new drive depends on several factors, including: |

|Replacing a Drive With Another of the Same Type

|Perform the following task to add a drive that supports the same media |formats as the drive it replaces: |

|Define the new drive
|For example, to define a new drive and name it DRIVE1, enter:
|define drive lib1 drive1 device=mt3.0.0.1

|You can use your existing library, device class, and storage pool |definitions. |

|Upgrading All of the Drives in a Library That Contained Only One Type of Drive

|You must decide how to handle any new types of media supported by the new |drives. See Overview of Media Compatibility Issues for more information.

|The following scenario assumes you already have a library device defined as |follows:

|+--------------------------------------------------------------------------------+
||                                                                                |
||Library  Library  Device         Private   Scratch   External                   |
||Name              Type           Category  Category  Manager                    |
||-------  -------  -------------  --------  --------  --------                   |
||LIB1     349X     \\.\lb3.0.0.0  200       201                                  |
|+--------------------------------------------------------------------------------+
|

|Define each new drive
|For example, to define a new drive and name it DRIVE1, enter:
|define drive lib1 drive1 device=mt3.0.0.1

|Update device class and storage pool definitions
| |

|Upgrading Some of the Drives in a Library That Contained Only One Type of Drive

|Each type of drive requires a separately defined logical library. If |a library contains only one type of drive and you upgrade only a subset of |those drives, you must define an additional logical library.

|The following scenario assumes you already have a library device defined as |follows:

|+--------------------------------------------------------------------------------+
||                                                                                |
||Library  Library  Device         Private   Scratch   External                   |
||Name              Type           Category  Category  Manager                    |
||-------  -------  -------------  --------  --------  --------                   |
||LIB1     349X     \\.\lb3.0.0.0  200       201                                  |
|+--------------------------------------------------------------------------------+
|

|Define a new logical library for each new type of drive
|For example, to add a logical library named LIB2 for the same physical |device already defined as LIB1, enter:
|define library lib2 libtype=349X device=lb3.0.0.0 scratchcategory=401 privatecategory=400

|Define each new drive to the new library
|To define a new drive named DRIVE2 to the logical library named LIB2, |enter:
|define drive lib2 drive2 device=mt3.0.0.1

|Update device class and storage pool definitions

|To define a new device class, enter:

|define devclass new_dev_class devtype=3590 format=drive library=lib2 estcapacity=40G
| 

|For accurate reporting of capacity information, you must specify the |ESTCAPACITY parameter.

|To define a new storage pool, enter:

|define stgpool new_stg_pool new_dev_class maxscratch=number_of_new_tapes

|You can then use the CHECKIN LIBVOLUME command to check the new media into |the logical library LIB2. |

|Upgrading All of the Drives in a Library That Contained More than One Type of Drive

|The following scenario assumes you already have two logical libraries |defined, for example:

|+--------------------------------------------------------------------------------+
||                                                                                |
||Library  Library  Device         Private   Scratch   External                   |
||Name              Type           Category  Category  Manager                    |
||-------  -------  -------------  --------  --------  --------                   |
||LIB1     349X     \\.\lb3.0.0.0  200       201                                  |
||LIB2     349X     \\.\lb3.0.0.0  300       301                                  |
|+--------------------------------------------------------------------------------+
|

|Update drive definitions for each logical library
|For each library, follow the guidelines in Upgrading All of the Drives in a Library That Contained Only One Type of Drive. For accurate reporting of capacity information, you |cannot use a global scratch pool with this configuration. |

|Upgrading Some of the Drives in a Library That Contained More than One Type of Drive

|The following scenario assumes you already have two logical libraries |defined, for example:

|+--------------------------------------------------------------------------------+
||                                                                                |
||Library  Library  Device         Private   Scratch   External                   |
||Name              Type           Category  Category  Manager                    |
||-------  -------  -------------  --------  --------  --------                   |
||LIB1     349X     \\.\lb3.0.0.0  200       201                                  |
||LIB2     349X     \\.\lb3.0.0.0  300       301                                  |
|+--------------------------------------------------------------------------------+
|

|Update drive definitions for each logical library
|For each library, follow the guidelines in Upgrading Some of the Drives in a Library That Contained Only One Type of Drive. For accurate reporting of capacity information, you |cannot use a global scratch pool with this configuration. |

|Migrating to Upgraded Drives

|If you upgrade all of the drives in a library, you can define a new DISK |storage pool and set it up to migrate its data to a storage pool created for |the new drives. You can then update your existing management class |definitions to begin storing data in the new DISK storage pool. This |allows you to preserve your existing policy definitions to migrate and expire |existing data, while using the new drives to store new data.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]