Defining a Sequential Access Storage Pool

To define a sequential access primary storage pool, complete the following fields and then click Finish, or click Cancel to end the task.

Storage Pool Name

Enter a name for the storage pool. The name is required. The maximum length of the name is 30 characters.

Device Class

Select the device class that the storage pool will use.

Description

Enter a 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 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.
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 physical size of a file to be stored 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.

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. The default is 90.

Low Migration Threshold

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

Collocate

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 tries to put data for different file spaces on different volumes.

Reclamation Threshold

Enter the percentage (1 to 100) 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.

Maximum Scratch Volumes Allowed

Enter the maximum number of scratch volumes that can be requested by the server for this storage pool. The default is 0.

Delay Period for Volume Reuse

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.

Reclaim to Storage Pool

Select another storage pool as a target for data from reclaimed storage pool volumes. By default, the server moves data from reclaimed volumes to other volumes in the same storage pool.

You may want to select a storage pool for reclaiming data if the library for the storage pool has only one drive.

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

Migration Continue

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.

Copy Storage Pools

Enter the names of copy storage pools where the server simultaneously writes data when a client backup, archive, or migration operation stores data to the primary storage pool. The server writes the data simultaneously to all listed copy storage pools.

You can specify a maximum of 10 copy pool names, separated with commas. This option is restricted to primary storage pools using NATIVE or NONBLOCK data format. When using this field you may also use the Continue Copy on Error field.

Note: There are cases when simultaneous write does not create the copies in the copy storage pools.  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, continue to back up the primary storage pool to ensure that the copy storage pools are complete copies of the primary storage pool. For more information, see the Continue Copy on Error parameter description.

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

Storage Pool Data Format

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.