To define a primary storage pool on disk, complete the following fields and then click Finish, or click Cancel to end this task.
Note for Sun Solaris servers: Raw partitions generally provide the best performance.
Enter a name for the storage pool. The name is required. The maximum length of the name is 30 characters.
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 the files in the storage pool. The default is Readwrite.
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. |
Unavailable | Specifies that client nodes cannot access files stored on volumes in the storage pool. Server processes can move files among volumes in the storage pool, but cannot write new files. Server processes can also move or copy files from this storage pool to another storage pool. |
Enter the maximum size for a physical file that the server can store in the storage pool during a session with a client node. Enter a number (1 to 999999) followed by a scale factor, or enter NOLIMIT. The default is NOLIMIT. Scale factors and their meanings are:
K | Kilobyte |
M | Megabyte |
G | Gigabyte |
T | Terabyte |
For example, enter 5G to set the maximum file size to 5 gigabytes.
Select a primary storage pool to which the server can migrate files from this storage pool.
Enter the percentage of storage pool occupancy that specifies when the server can start migration for this storage pool. The default is 90.
Enter the percentage of storage pool occupancy to determine when the server can stop migration for this storage pool. The default is 70.
Select an option to determine whether a cached copy of a file that has been migrated remains in the disk storage pool. The default is No.
Yes | Specifies that caching is enabled. A cached copy of a migrated file remains in the disk storage pool. |
No | Specifies that caching is disabled. No cached copy of a migrated file remains in the disk storage pool. |
Enter the number of processes that the server uses for migrating files from this storage pool. The default is 1. This value can be a number from 1 to 999.
Note: This note only applies to migrating files on disk storage pools. The number of migration processes is dependent upon the setting of the MIGPROCESS parameter and the number of nodes with data on the migrating storage pool. For example, if the MIGPROCESS parameter is equal to six, but there are only two nodes with data on the storage pool, migration processing only consists of two processes, not six.
Enter the number of days that a file must remain in a storage pool before the file is eligible for migration from the storage pool. The number of days is counted from the day the file was last stored in the storage pool or retrieved by a client, whichever is more recent. The default is 0, which means migration will not be delayed. The number must be an integer from 0 to 9999.
Select whether to allow the server to migrate files that do not satisfy the migration delay time. The default is Yes.
Because you can require that files remain in the storage pool for a minimum number of days, the server may migrate all eligible files to the next storage pool yet not meet the low migration threshold. Selecting yes or no determines if the server is allowed to continue migrating files that do not satisfy the migration delay time.
Yes | Specifies that when necessary to meet the low migration threshold, the server continues to migrate files that do not satisfy the migration delay time. |
No | Specifies that the server stops migration when no eligible files remain to be migrated, even before reaching the low migration threshold. The server does not migrate files unless the files satisfy the migration delay time. |