![]() |
![]() |
Before the Tivoli Storage Manager server can used a device, the device must
be configured to the operating system as well as to the server. Table 4 summarizes the definitions that are required for different
device types.
Table 4. Required Definitions for Storage Devices
As an example of mapping devices to device classes, assume that you have the following devices to use for server storage:
You can map storage devices to device classes as shown in Table 5.
Table 5. Mapping Storage Devices to Device Classes
Device Class | Description |
---|---|
DISK | Storage volumes that reside on the internal disk drive
Tivoli Storage Manager provides one DISK device class that is already defined. You do not need and cannot define another device class for disk storage. |
8MM_CLASS | Storage volumes that are 8mm tapes, used with the drives in the automated library |
DLT_CLASS | Storage volumes that are DLT tapes, used on the DLT drive |
You must define any device classes that you need for your removable media devices such as tape drives. See Chapter 8, Defining Device Classes for information on defining device classes to support your physical storage environment.
After you have categorized your storage devices, identify availability, space, and performance requirements for client data that is stored in server storage. These requirements help you determine where to store data for different groups of clients and different types of data. You can then create storage pools that are storage destinations for backed-up, archived, or space-managed files to match requirements.
For example, you determine that users in the business department have three requirements:
These files should be stored on disk. However, you need to ensure that data is moved from the disk to prevent it from becoming full. You can set up a storage hierarchy so that files can migrate automatically from disk to the automated tape library.
These files can be stored on 8mm tapes, using the automated library.
These files can be stored using the DLT drive.
To match user requirements to storage devices, you define storage pools,
device classes, and, for device types that require them, libraries and
drives. For example, to set up the storage hierarchy so that data
migrates from the BACKUPPOOL to 8mm tapes, you specify BACKTAPE1 as the next
storage pool for BACKUPPOOL. See Table 6.
Table 6. Mapping Storage Pools to Device Classes, Libraries, and Drives
Storage Pool | Device Class | Library (Hardware) | Drives | Volume Type | Storage Destination |
---|---|---|---|---|---|
BACKUPPOOL | DISK | -- | -- | Storage volumes on the internal disk drive | For a backup copy group for files requiring immediate access |
BACKTAPE1 | 8MM_CLASS | AUTO_8MM (Exabyte EXB-210) | DRIVE01, DRIVE02 | 8mm tapes | For overflow from the BACKUPPOOL and for archived data that is periodically accessed |
BACKTAPE2 | DLT_CLASS | MANUAL_LIB (Manually mounted) | DRIVE03 | DLT tapes | For backup copy groups for files that are occasionally accessed |
|