Tivoli Header

Administrator's Guide


Configuring Devices

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

Device Device Types Required Definitions
Library Drive Device Class
Magnetic disk DISK -- -- Yes 1
FILE -- -- Yes
Tape 3570
3590
4MM
8MM
CARTRIDGE 23
DLT
DTF
ECARTRIDGE 3
GENERICTAPE
LTO
QIC
Yes Yes Yes
Optical OPTICAL
WORM
WORM12
WORM14
Yes Yes Yes
Removable media (file system) REMOVABLEMEDIA Yes Yes Yes
Virtual volumes SERVER -- -- Yes

1
The DISK device class exists at installation and cannot be changed.

2
The CARTRIDGE device type is for IBM 3480, 3490, and 3490E tape drives.

3
The ECARTRIDGE device type is for cartridge tape drives such as the StorageTek SD-3, 9480, 9890, and 9940 drives.

Mapping Devices to Device Classes

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.

Mapping Storage Pools to Device Classes and Devices

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:

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
Note:
Tivoli Storage Manager has default disk storage pools named BACKUPPOOL, ARCHIVEPOOL, and SPACEMGPOOL. For more information, see Configuring Random Access Volumes on Disk Devices.


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