Configuring random access volumes on disk devices

Tivoli® Storage Manager provides a predefined DISK device class that is used with all disk devices.

Complete the following steps to use random access volumes on a disk device:

1. Define a storage pool that is associated with the DISK device class, or use one of the default storage pools that Tivoli Storage Manager provides: ARCHIVEPOOL, BACKUPPOOL, and SPACEMGPOOL.
   For example, enter the following command on the command line of an administrative client:

   define stgpool engback1 disk maxsize=5G highmig=85 lowmig=40

   This command defines storage pool ENGBACK1.

   See Example: Defining storage pools for details.

2. Prepare a volume for use in a random access storage pool by defining the volume. If you do not specify a full path name, the command uses the current path. For example:
   Define a 21 MB volume for the ENGBACK1 storage pool in the path /opt/tivoli/tsm/server/bin and named stgvol.002. Enter the following command:

   define volume engback1 /opt/tivoli/tsm/server/bin/stgvol.002 formatsize=21

   Another option for preparing a volume is to create a raw logical volume by using SMIT.

   Another option for preparing a volume is to create a raw logical volume on a formatted disk. For details, see the format command for the operating system. After you create the logical volume, you define the volume to Tivoli Storage Manager.

   Note: The server cannot detect if data exists on a raw logical volume. Existing data can be destroyed if you define a Tivoli Storage Manager volume to that raw logical volume.

   Tivoli Storage Manager does not support raw logical volumes on Linux.

   Another option for preparing a volume is to create a raw partition on a formatted disk. Raw partitions generally provide the best performance, however a IBM® Tivoli Storage Manager server that is running Solaris 10 does not support ZFS raw partitions. For details, see the format command for the operating system. When creating the partition with the /etc/format utility, do not include cylinder 0 (zero) in the partition that is intended for use as a raw partition. After you create the partition, define the volume to Tivoli Storage Manager.

   Note: The server cannot detect if data exists on a raw partition. Existing data can be destroyed if you define a volume to that partition.
3. Do one of the following:
   • Specify the new storage pool as the destination for client files that are backed up, archived, or migrated, by modifying existing policy or creating new policy.
   • Place the new storage pool in the storage pool migration hierarchy by updating an already defined storage pool. See Example: Updating storage pools.