IBM E16RMLL-I Implementation Guide - Page 269
Storage pool volumes
![]() |
View all IBM E16RMLL-I manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 269 highlights
In 1.1.1, "Our support material" on page 5, we show how to load a predefined macro into the Tivoli Storage Manager. The macro mac.stgdelete, which we provide to delete the default storage pools, is shown in "Delete default storage pools" on page 739. The macro deletes the four default storage pools automatically set up by the Windows installation, including an additional storage pool named DISKPOOL. Note that a Tivoli Storage Manager installation on a UNIX platform does not create DISKPOOL. You must remove the line deleting DISKPOOL before running the macro. 6.4 Storage pool volumes Now that our storage pools are defined, we must perform one final task for each of them. Storage pools must contain volumes to be able to store data. For disk storage pools, volumes are simply files (usually large) located on the server's file systems. For tape storage pools (both primary and copy), volumes are physical tape cartridges. In order to write to or read from the tapes, they must be mountable, that is, present in a library. Tape volumes are still regarded as part of a storage pool even though they might no longer be inside a tape library (that is, not-mountable or off-site). This section provides examples of assigning volumes to storage pools. You can add or remove volumes to and from storage pools without interrupting server operations. For example, if you install a new disk drive for a disk pool, the Tivoli Storage Manager administrator can move the storage pool data from the old pool to the new pool without shutting down the server. Or, if you have to add space to a storage pool, you can easily define new volumes and expand the size of the storage pool without disrupting service. 6.4.1 Defining random access disk volumes Disk volumes can be defined to a Tivoli Storage Manager storage pool in two ways. Described here is the more efficient one-step process using the define volume command with the FORMATSIZE option. The other method has two steps: prepare the disk volume using the dsmfmt utility and then define the volume to the storage pool using the define volume command. By now you will have decided on your disk storage pool volume numbers and sizes. Remember that it is better to have a number of smaller volumes than a single large volume in your disk storage pools. Although they take up the same amount of space, having more smaller volumes is more efficient. With a single volume in the pool, only a single server thread can write to it at any given time. With more volumes, more server threads can write to them simultaneously. Multiple volumes can be spread over more physical disks, enhancing Chapter 6. Data storage 239
![](/manual_guide/products/ibm-e16rmlli-implementation-guide-3588123/269.png)