TSM stores data on magnetic disks in two ways:
Task | Required Privilege Class |
---|---|
"Configuring Random Access Volumes on Disk Devices" | System |
"Configuring FILE Sequential Volumes on Disk Devices" | System |
For disk devices, TSM provides a defined DISK device class that is used with all disk devices.
Note: | For performance reasons, allocate storage pool volumes on disk drives that reside on the TSM server machine, not on remotely mounted file systems. |
Do the following to use random access volumes on a disk device:
For example, enter the following command on the command line of a TSM administrative client:
define stgpool engback1 disk maxsize=5m highmig=85 lowmig=40
This command defines storage pool ENGBACK1.
See Example: Defining Storage Pools for details.
define volume engback1 /opt/adsmserv/bin/stgvol.002 formatsize=21
If you do not specify a full path name, the command uses the current path. See Defining Storage Pool Volumes for details.
Tip: | Define storage pool volumes on disk drives that reside on the TSM server machine, not on remotely mounted file systems. |
Note: | This one-step process replaces the former two-step process of first formatting a volume (using DSMFMT) and then defining the volume. If you choose to use the two-step process, the DSMFMT utility is available from the operating system command line. See Administrator's Reference for details. |
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 TSM.
Note: | The server cannot detect if data already exists on a raw logical volume. Existing data can be destroyed if you define a TSM volume to that raw logical volume. |
Another way to use magnetic disk storage is to use files as volumes that store data sequentially (as on tape volumes). FILE sequential volumes are often useful when transferring data for purposes such as electronic vaulting.
To use files as volumes that store data sequentially, do the following:
For example, enter the following command on the command line of a TSM administrative client:
define devclass fileclass devtype=file mountlimit=2
This command defines device class FILECLASS with a device type of FILE.
See Defining and Updating FILE Device Classes.
To store TSM database backups or exports on FILE volumes, this step is all you need to do to prepare the volumes. For more information, see Defining Device Classes for Backups and Planning for Sequential Media Used to Export Data.
For example, enter the following command on the command line of a TSM administrative client:
define stgpool engback2 fileclass maxscratch=100 mountlimit=2
This command defines storage pool ENGBACK2 with device class FILECLASS.
See Defining or Updating Primary Storage Pools for details.
To allow the server to use scratch volumes for this device class, specify a value greater than zero for the number of maximum scratch volumes when you define the device class. If you do set MAXSCRATCH=0 to not allow scratch volumes, you must define each volume to be used in this device class. See Preparing Volumes for Sequential Access Storage Pools for details.