Updating a Disk Storage Pool

To change a disk storage pool, complete the following fields and then click Finish, or click Cancel to end this task.

Description

Enter the description of the storage pool. The maximum length of the description is 255 characters.

Media Access Status

Select how client nodes and server processes (such as migration and reclamation) can access the 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.
Unavail able 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.

Maximum Size Threshold

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. 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.

Next Storage Pool

Select a primary storage pool to which the server can migrate files from this storage pool.

High Migration Threshold

Enter the percentage of storage pool occupancy that specifies when the server can start migration for this storage pool.

Low Migration Threshold

Enter the percentage of storage pool occupancy to determine when the server can stop migration for this storage pool.

Cache Migrated Files

Select an option to determine whether a cached copy of a file that has been migrated remains in the disk storage pool.

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.

Migration Process

Enter the number of processes that the server uses for migrating files from this storage pool. This value can be a number from 1 to 999.

Migration Delay

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. Entering the value 0 means migration will not be delayed. The number must be an integer from 0 to 9999.

Migration Continue

Select whether to allow the server to migrate files that do not satisfy the migration delay time.

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.

Copy Storage Pools

Enter the names of copy storage pools where copies of files being stored in the primary storage pool, during a client backup, archive or HSM stores are also simultaneously written to all listed copy storage pools. You can specify a maximum of 10 copy pool names. This option is restricted to only primary storage pools using NATIVE or NONBLOCK data format. When using this field you may also use the Continue Copy on Error field. For additional information see the Continue Copy on Error description.

Note: 

  1. The function provided by the Copy Storage Pools option is not intended to replace the Backup Storage Pool function. If you use the Copy Storage Pools option, you must also verify that all copies are made by invoking the BACKUP STGPOOL command. There are cases when a copy may not be created, for more information see the Continue Copy on Error parameter description.
  2. Simultaneous write to copy storage pools is not supported when the operation is using LAN-free data movement. Data is stored into the primary storage pool, but the copy storage pools are ignored.

Continue Copy on Error

Select how the server should react to a copy storage pool write failure for any of the copy pools listed in the Copy Storage Pools entry field. The default is Yes. When selecting this field you must either have an existing Copy Storage Pools list or create a list using the Copy Storage Pools field.

Yes Specifies that during a write failure, the server will exclude the failing copy storage pool from any further writes while that specific client session is active. That is, any further writes will not include the failing copy storage pool while that client session is active. The simultaneous writes to the failing copy storage pool will resume after the client session has ended and a new session is started. Therefore, it is possible that other nodes will attempt to write to the failing copy storage pool even though it may have failed for another node.
No Specifies that during a write failure, the server will fail the entire transaction including the write to the primary storage pool. Any further attempt to write to the primary storage pool will include all copy storage pools in the list. If the failing copy storage pool has not recovered this will probably result in failed transactions. An example of a transaction is a single backup or an archive operation.

CRC Data

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.