To define a copy storage pool, first complete the following fields and then click Finish, or click Cancel to end the task.
Enter the name of the storage pool to be defined. The maximum length of the name is 30 characters.
Select the name of the device class.
Enter the description of the storage pool to be defined.
Select how users and system processes (like migration and reclamation) can access files in the storage pool.
Readwrite | Specifies that users and system processes can read and write to files stored on volumes in the storage pool. The default is Readwrite. |
Readonly | Specifies that users can only read files from the volumes in the storage pool. |
Unavail able | Specifies that users cannot access files stored on volumes in the storage pool. |
Select whether ADSM attempts to keep data belonging to a single client node or to a single client node's filespace on as few volumes as possible.
Yes | Specifies that collocation is enabled. The server tries to put data for one node on as few volumes as possible. If the node has multiple filespaces, no attempt is made to collocate those filespaces. |
No | Specifies that collocation is disabled. The default is No. |
Filespace | Specifies that collocation is enabled at the filespace level for client nodes. The server tries to put data for one node and filespace on as few volumes as possible. If a node has multiple filespaces, the server attempts to put data for different filespaces on different volumes. |
Enter the percentage value of reclaimable space on a volume that specifies when to initiate reclamation of fragmented space on volumes in the storage pool.
Enter the maximum number of scratch volumes that can be requested by ADSM.
Enter the number of days that must elapse after all files have been deleted from a volume, before the volume can be rewritten or returned to the scratch pool.
Enter the overflow location for the storage pool being defined. This applies to storage pools associated with automated libraries only. This option is not for AS400.