This section contains procedures for configuring devices with the Device
Configuration Wizard, where applicable. While it is recommended that
you use the wizard whenever possible, some devices, such as IBM 3494 Tape
Library Dataservers, must be added using TSM commands.
Task | Required Privilege Class |
---|---|
Adding Devices | System |
This section describes the procedure for configuring manually operated, stand-alone tape and optical devices that are supported by the TSM device driver. See Devices Supported by Tivoli Storage Manager.
For devices not yet supported by the TSM device driver, the Windows device driver can be used. See Adding Devices Not Supported by the Tivoli Storage Manager Device Driver.
Follow the manufacturer's instructions to attach the device to the system.
See Selecting the Appropriate Device Driver for Tivoli Storage Manager Devices.
Determine which device TSM backs up client data to, and whether client data is backed up to disk, and then migrated to tape, or if it is backed up directly to tape. See "Planning for Devices".
This section describes the procedure for adding automated library devices with the Device Configuration Wizard.
Follow the manufacturer's instructions to attach the device to the system.
See Selecting the Appropriate Device Driver for Tivoli Storage Manager Devices.
Determine which device TSM backs up client data to, and whether client data is backed up to disk, and then migrated to tape, or if it is backed up directly to tape. See "Planning for Devices".
Add volumes to an automated device by checking the volumes into library. Scratch volumes are checked in differently than private volumes.
Adding volumes depends on the presence of scratch volumes or private volumes in the library device:
IBM 3494 Tape Library Dataserver devices can only be added using TSM commands. See Adding Devices Using TSM Commands for detailed instructions and examples. The following guidelines must be followed:
3494 devices support only 3590 tape drives. You must always specify the ENABLE3590LIBRARY server option. When you enable support for 3590 drives for the server, the server reserves three different categories in the 3494 library. The categories are: private, unused, and scratch.
When you define 3494 libraries, you can specify the category numbers for volumes that TSM owns in that library by using the PRIVATECATEGORY and SCRATCHCATEGORY parameters. TSM automatically creates a scratch category for 3590 drives, by adding one to the SCRATCHCATEGORY parameter specified by the administrator. For example:
define library MY3494 libtype=349x device=3494a privatecategory=400 scratchcategory=401
TSM then uses the following categories in the new MY3494 library:
To avoid overlapping categories, do not specify a number that is equal to the scratch category plus 1.
Attention: The default values for the categories are acceptable in most cases. However, if you connect other systems or TSM servers to a single 3494 library device, ensure that each uses unique category numbers. Otherwise, two or more systems may try to use the same volume, and cause a corruption or loss of data.
For information on the ENABLE3590LIBRARY server option, see Administrator's Reference.
To set up the device, as for other sequential access devices, use the following steps:
Follow the manufacturer's instructions to attach the device to the system.
See Selecting the Appropriate Device Driver for Tivoli Storage Manager Devices.
See Using Commands to Define TSM Storage Objects for instructions on using TSM commands to configure the device.
Determine which device TSM backs up client data to, and whether client data is backed up to disk, and then migrated to tape, or if it is backed up directly to tape. See "Planning for Devices".
Define the TSM policy that links client data with media for the device. For an example, see Defining and Updating a Policy Domain.
See Labeling Media for use with an Automated Library Device or Labeling Media for use in a Manual Library Device.
Add volumes to an automated device by checking the volumes into library. Scratch volumes are checked in differently than private volumes.
Adding volumes depends on the presence of scratch volumes or private volumes in the library device:
Unsupported devices can be added using TSM commands. See Adding Devices Using TSM Commands for detailed instructions and examples.
You can configure devices that run with their own or Windows device drivers as long as the devices meet TSM requirements. See Determine if Devices Meet Requirements for Using Windows Device Drivers with Tivoli Storage Manager.
Follow the manufacturer's instructions to attach the device to the system.
See Selecting the Appropriate Device Driver for Tivoli Storage Manager Devices.
See Using Commands to Define TSM Storage Objects for instructions on using TSM commands to configure the device. The following guidelines must be followed:
Determine which device TSM backs up client data to, and whether client data is backed up to disk, and then migrated to tape, or if it is backed up directly to tape. See "Planning for Devices".
Define the TSM policy that links client data with media for the device. For an example, see Defining and Updating a Policy Domain.
See Labeling Media for use with an Automated Library Device or Labeling Media for use in a Manual Library Device.
This section describes the procedure for configuring optical disk devices that are supported by the TSM device driver.
Follow the manufacturer's instructions to attach the device to the system.
See Selecting the Appropriate Device Driver for Tivoli Storage Manager Devices.
Removable media devices can be added using TSM commands. See Adding Devices Using TSM Commands for detailed instructions and examples. The following guidelines must be followed:
If a file system can be backed up to a removable media device, TSM may be able to use that device. TSM recognizes the device as a device with type REMOVABLEFILE. To use device type REMOVABLEFILE for a device, the device:
The operating system treats some optical drives as fixed drives after data is written to them and until the system reboots. TSM cannot use these drives as removable file devices.
You can use the CD-ROM media as input media on a target TSM server by using the REMOVABLEFILE device class for input. Using REMOVABLEFILE device class for input allows TSM to distinguish media volumes by a "volume label", to prompt for additional media, and to dismount media.
With CD-ROM support for Windows, you can also use CD-ROM media as an output device class. Using CD-ROM media as output requires other software which uses a file system on top of the CD-ROM media. ADAPTEC Direct CD software is the most common package for this application. This media allows other software to write to a CD by using a drive letter and file names. The media can be either CD-R (read) or CD-RW (read/write).
If a data cartridge that is associated with a REMOVABLEFILE device class has two sides, TSM treats each side as a separate TSM volume.
To set up the device, as for other sequential access devices, use the following steps.
Follow the manufacturer's instructions to attach the device to the system.
See Selecting the Appropriate Device Driver for Tivoli Storage Manager Devices.
See Using Commands to Define TSM Storage Objects for instructions on using TSM commands to configure the device. The following parameters must be specified:
Determine which device TSM backs up client data to, and whether client data is backed up to disk, and then migrated to tape, or if it is backed up directly to tape. See "Planning for Devices" and Defining and Updating a Policy Domain.
TSM does not supply utilities to format or label CD-ROMs. Use the utilities that are supplied with the device or operating system. See Labeling Media for Devices not Supported by the TSM Device Driver.
Use these steps as an example of TSM REMOVABLEFILE support. This example takes an export object and moves it from one server to another.
define devclass expfile devtype=file directory=c:\data\move
export node user1 filedata=all devclass=expfile vol=CDR03
You can use software for writing CD-ROMs to create a CD with volume label CDR03 that contains the file named CDR03.
define library manual define devclass cdrom devtype=removablefile library=manual define drive manual cddrive device=e: import node user1 filedata=all devclass=cdrom vol=CDR03