To define a copy storage pool, first complete the following fields and then click Finish, or click Cancel to end the task.
Enter a name for the storage pool. The name is required. The maximum length of the name is 30 characters.
Select the device class that the storage pool will use.
Enter a description of the storage pool. The maximum length of the description is 255 characters.
Select how client nodes and server processes (such as migration and reclamation) can access files in the storage pool.
Readwrite | Specifies that both client nodes and server processes can read and write to files stored on volumes in the storage pool. |
Readonly | Specifies that client nodes can only read files from the volumes in the storage pool. Server processes can move files among volumes in the storage pool, but cannot write new files. The server can use files in the copy storage pool to restore files to primary storage pools |
Unavailable | Specifies that client nodes cannot access files stored on volumes in the storage pool. |
Select whether the server attempts to keep data belonging to a single client node or to a single client node's file space on as few volumes as possible. The default is No.
Yes | Specifies that collocation is enabled. The server tries to put data for one node on as few volumes as possible. The server does not try to collocate data by file space. |
No | Specifies that collocation is disabled. |
Filespace | Specifies that collocation is enabled at the file space level for client nodes. The server tries to put data for one node and file space on as few volumes as possible. If a node has multiple file spaces, the server attempts to put data for different file spaces on different volumes. |
Enter the percentage of reclaimable space on a volume to specify when the server starts reclamation of fragmented space on volumes in the storage pool. The default is 60.
Enter the maximum number of scratch volumes that can be requested by the server for this storage pool. The default is 0.
Enter the number of days (0 to 9999) that must elapse after all files have been deleted from a volume, before the volume can be rewritten or returned to the scratch pool. The default is 0.
Specifies whether a Cyclic Redundancy Check (CRC) validates storage pool data when audit volume processing occurs on the server. This parameter is optional. By setting CRC Data Validation to YES and scheduling audit volume processing you can continually ensure the integrity of data stored in your storage hierarchy. The default value is NO.
Yes | Specifies that data is stored containing CRC information, allowing for audit volume processing to validate storage pool data. |
No | Specifies that data is stored without CRC information. |
The format in which data will be stored. The data format used can determine which parameters are available and the corresponding options available for those parameters.
Native | Specifies the data format is the native Tivoli Storage Manager server format and includes block headers. |
Nonblock | Specifies the data format is the native Tivoli Storage Manager server format and does not include block headers. |
Enter the overflow location for the storage pool. This applies to storage pools associated with automated libraries only. The maximum length is 255 characters.