Use this command to change a storage pool.
The UPDATE STGPOOL command takes three forms, depending on whether the update is for a primary storage pool assigned to random access devices, a primary storage pool assigned to sequential access devices, or a copy storage pool. The syntax and parameters for each form are defined separately.
Use this command to update a random access storage pool.
Privilege Class
To issue this command, you must have system privilege, unrestricted storage privilege, or restricted storage privilege for the storage pool to be updated.
Syntax
>>-UPDate STGpool---pool_name-----------------------------------> >-----+------------------------------+--------------------------> '-DESCription--=--description--' >-----+-----------------------------+---------------------------> '-ACCess--=--+-READWrite---+--' +-READOnly----+ '-UNAVailable-' >-----+------------------------------------+--------------------> '-MAXSIze--=--+-maximum_file_size-+--' '-NOLimit-----------' >-----+----------------------------+---+----------------------+-> '-NEXTstgpool--=--pool_name--' '-HIghmig--=--percent--' >-----+---------------------+---+--------------------+----------> '-LOwmig--=--percent--' '-CAChe--=--+-Yes-+--' '-No--' >-----+------------------------+---+--------------------+-------> '-MIGPRocess--=--number--' '-MIGDelay--=--days--' >-----+--------------------------+----------------------------->< '-MIGContinue--=--+-No--+--' '-Yes-'
Parameters
Server processes can move files within the volumes in the storage pool. However, no new writes are permitted to volumes in the storage pool from volumes outside the storage pool.
If this storage pool has been specified as a subordinate storage pool (with the NEXTSTGPOOL parameter) and is defined as readonly, the storage pool is skipped when server processes attempt to write files to the storage pool.
Server processes can move files within the volumes in the storage pool and can also move or copy files from this storage pool to another storage pool. However, no new writes are permitted to volumes in the storage pool from volumes outside the storage pool.
If this storage pool has been specified as a subordinate storage pool (with the NEXTSTGPOOL parameter) and is defined as unavailable, the storage pool is skipped when server processes attempt to write files to the storage pool.
Scale factor | Meaning |
K | kilobyte |
M | megabyte |
G | gigabyte |
T | terabyte |
If a file exceeds the maximum size and no pool is specified as the next storage pool in the hierarchy, the server does not store the file. If a file exceeds the maximum size and a pool is specified as the next storage pool, the server stores the file in the next storage pool that can accept the file size. If you specify the next storage pool parameter, at least one storage pool in your hierarchy should have no limit on the maximum size of a file. By having no limit on the size for at least one pool, you ensure that no matter what its size, the server can store the file.
For logical files that are part of an aggregate, the server considers the size of the aggregate to be the file size. Therefore, the server does not store logical files that are smaller than the maximum size limit if the files are part of an aggregate that is larger than the maximum size limit.
To remove an existing storage pool from the storage hierarchy, specify a null string ("") for this value.
If this storage pool does not have a next storage pool, the server cannot migrate files from this storage pool and cannot store in another storage pool files that exceed the maximum size for this storage pool.
You cannot create a chain of storage pools that leads to an endless loop through the NEXTSTGPOOL parameter. At least one storage pool in the hierarchy must have no value specified for NEXTSTGPOOL.
When the storage pool exceeds the high migration threshold, the server can start migration of files by node to the next storage pool, as defined with the NEXTSTGPOOL parameter. You can specify HIGHMIG=100 to prevent migration for this storage pool.
When the storage pool reaches the low migration threshold, the server does not start migration of another node's files. Because all file spaces that belong to a node are migrated together, the occupancy of the storage pool can fall below the value you specified for this parameter. You can set LOWMIG=0 to permit migration to empty the storage pool.
Using cache may improve the retrievability of files, but may affect the performance of other processes. See Administrator's Guide for details.
During migration, these processes are performed in parallel to provide the potential for improved migration rates.
If you want the server to count the number of days based only on when a file was stored and not when it was retrieved, use the NORETRIEVEDATE server option.
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. This parameter allows you to specify whether the server is allowed to continue the migration process by migrating files that do not satisfy the migration delay time.
Possible values are:
If you allow more than one migration process for the storage pool, some files that do not satisfy the migration delay time may be migrated unnecessarily. As one process migrates files that satisfy the migration delay time, a second process could begin migrating files that do not satisfy the migration delay time to meet the low migration threshold. The first process that is still migrating files that satisfy the migration delay time might have, by itself, caused the low migration threshold to be met.
Examples
Task
Update the random access storage pool named BACKUPPOOL to permit caching when the server migrates files to the next storage pool.
Use this command to update a primary sequential access storage pool.
Privilege Class
To issue this command, you must have system privilege, unrestricted storage privilege, or restricted storage privilege for the storage pool to be updated.
Syntax
>>-UPDate STGpool---pool_name-----------------------------------> >-----+------------------------------+--------------------------> '-DESCription--=--description--' >-----+-----------------------------+---------------------------> '-ACCess--=--+-READWrite---+--' +-READOnly----+ '-UNAVailable-' >-----+------------------------------------+--------------------> '-MAXSIze--=--+-maximum_file_size-+--' '-NOLimit-----------' >-----+----------------------------+---+----------------------+-> '-NEXTstgpool--=--pool_name--' '-HIghmig--=--percent--' >-----+---------------------+---+----------------------+--------> '-LOwmig--=--percent--' '-REClaim--=--percent--' >-----+-------------------------------+-------------------------> '-RECLAIMSTGpool--=--pool_name--' >-----+------------------------------+--------------------------> '-COLlocate--=--+-No--------+--' +-Yes-------+ '-FILespace-' >-----+------------------------+---+----------------------+-----> '-MAXSCRatch--=--number--' '-REUsedelay--=--days--' >-----+---------------------------+---+--------------------+----> '-OVFLOcation--=--location--' '-MIGDelay--=--days--' >-----+--------------------------+----------------------------->< '-MIGContinue--=--+-No--+--' '-Yes-'
Parameters
Server processes can move files within the volumes in the storage pool. However, no new writes are permitted to volumes in the storage pool from volumes outside the storage pool.
If this storage pool has been specified as a subordinate storage pool (with the NEXTSTGPOOL parameter) and is defined as readonly, the storage pool is skipped when server processes attempt to write files to the storage pool.
Server processes can move files within the volumes in the storage pool and can also move or copy files from this storage pool to another storage pool. However, no new writes are permitted to volumes in the storage pool from volumes outside the storage pool.
If this storage pool has been specified as a subordinate storage pool (with the NEXTSTGPOOL parameter) and is defined as unavailable, the storage pool is skipped when server processes attempt to write files to the storage pool.
Scale factor | Meaning |
K | kilobyte |
M | megabyte |
G | gigabyte |
T | terabyte |
If a file exceeds the maximum size and no pool is specified as the next storage pool in the hierarchy, the server does not store the file. If a file exceeds the maximum size and a pool is specified as the next storage pool, the server stores the file in the next storage pool that can accept the file size. If you specify the next storage pool parameter, at least one storage pool in your hierarchy should have no limit on the maximum size of a file. By having no limit on the size for at least one pool, you ensure that no matter what its size, the server can store the file.
For logical files that are part of an aggregate, the server considers the size of the aggregate to be the file size. Therefore, the server does not store logical files that are smaller than the maximum size limit if the files are part of an aggregate that is larger than the maximum size limit.
Note: | This size limit applies only when the server is storing files during a session with a client. The limit does not apply when you move data from one pool to another, either manually or automatically through storage pool migration. |
To remove an existing value, specify a null string ("").
If this storage pool does not have a next storage pool, the server cannot migrate files from this storage pool and cannot store in another storage pool files that exceed the maximum size for this storage pool.
You cannot create a chain of storage pools that leads to an endless loop through the NEXTSTGPOOL parameter. At least one storage pool in the hierarchy must have no value specified for NEXTSTGPOOL.
When the storage pool exceeds the high migration threshold, the server can start migration of files by volume to the next storage pool defined for the storage pool. You can set the high migration threshold to100 to prevent migration for the storage pool.
When the storage pool reaches the low migration threshold, the server does not start migration of files from another volume. You can set the low migration threshold to 0 to permit migration to empty the storage pool.
Specify a value of 50 percent or greater for this parameter so that files stored on two volumes can be combined onto a single output volume.
For storage pools that use WORM devices, you can lower the value from the default of 100. Lowering the value allows the server to consolidate data onto fewer volumes when needed. Volumes emptied by reclamation can be checked out of the library, freeing slots for new volumes. Because the volumes are write-once, the volumes cannot be reused.
To remove an existing value, specify a null string ("").
A reclaim storage pool is most useful for a storage pool that has only one drive in its library. When you specify this parameter, the server moves all data from reclaimed volumes to the reclaim storage pool regardless of the number of drives in the library.
To move data from the reclaim storage pool back to the original storage pool, use the storage pool hierarchy. Specify the original storage pool as the next storage pool for the reclaim storage pool.
Collocation reduces the number of sequential access media mounts for restore, retrieve, and recall operations. However, collocation increases both the amount of server time needed to collocate files for storing and the number of volumes required. For details, see Administrator's Guide.
Possible values are:
The value specified for this parameter is used to estimate the total number of volumes available in the storage pool and the corresponding estimated capacity for the storage pool.
Scratch volumes are automatically deleted from the storage pool when they become empty. When scratch volumes with the device type of FILE are deleted, the space that the volumes occupied is freed by the server and returned to the file system.
By specifying this parameter, you can ensure that the database could be restored to an earlier level and database references to files in the storage pool would still be valid.
To remove an existing value, specify a null string ("").
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. This parameter allows you to specify whether the server is allowed to continue migration by migrating files that do not satisfy the migration delay time.
Possible values are:
Examples
Task
Update the primary sequential storage pool named TAPEPOOL1 to permit as many as 10 scratch volumes to be mounted.
Use this command to update a copy sequential access storage pool.
Privilege Class
To issue this command, you must have system privilege, unrestricted storage privilege, or restricted storage privilege for the storage pool to be updated.
Syntax
>>-UPDate STGpool---pool_name-----------------------------------> >-----+------------------------------+--------------------------> '-DESCription--=--description--' >-----+-----------------------------+---------------------------> '-ACCess--=--+-READWrite---+--' +-READOnly----+ '-UNAVailable-' >-----+------------------------------+--------------------------> '-COLlocate--=--+-No--------+--' +-Yes-------+ '-FILespace-' >-----+----------------------+---+------------------------+-----> '-REClaim--=--percent--' '-MAXSCRatch--=--number--' >-----+----------------------+---+---------------------------+->< '-REUsedelay--=--days--' '-OVFLOcation--=--location--'
Parameters
Server processes can move files within the volumes in the storage pool. The server can use files in the copy storage pool to restore files to primary storage pools. However, no new writes are permitted to volumes in the copy storage pool from volumes outside the storage pool. A storage pool cannot be backed up to the copy storage pool.
Server processes can move files within the volumes in the storage pool. The server can use files in the copy storage pool to restore files to primary storage pools. However, no new writes are permitted to volumes in the copy storage pool from volumes outside the storage pool. A storage pool cannot be backed up to the copy storage pool.
Collocation reduces the number of sequential access media mounts for restore, retrieve, and recall operations. However, collocation increases both the amount of server time needed to collocate files for storing and the number of volumes required. For details, see Administrator's Guide.
Possible values are:
If you change the value from the default of 100, specify a value of 50 percent or greater so that files stored on two volumes can be combined onto a single output volume.
When a copy pool volume that is offsite becomes eligible for reclamation, the reclamation process attempts to obtain the active files on the reclaimable volume from a primary or copy storage pool that is onsite. The process then writes these files to an available volume in the original copy storage pool. Effectively, these files are moved back to the onsite location. However, the files could be obtained from the offsite volume after a disaster if a database backup is used that references the files on the offsite volume. Because of the way reclamation works with offsite volumes, use it carefully with copy storage pools.
The value specified for this parameter is used to estimate the total number of volumes available in the copy storage pool and the corresponding estimated capacity for the copy storage pool.
Scratch volumes are automatically deleted from the storage pool when they become empty. However, if the access mode for a scratch volume is OFFSITE, the volume is not deleted from the copy storage pool until the access mode is changed. This allows an administrator to query the server for empty, offsite scratch volumes and return these to the onsite location.
When scratch volumes with the device type of FILE become empty and are deleted, the space that the volumes occupied is freed by the server and returned to the file system.
Important: | Use this parameter to help ensure that when you restore the database to an earlier level, database references to files in the copy storage pool are still valid. You must set this parameter to a value greater than the number of days you plan to retain the oldest database backup. The number of days specified for this parameter should be the same as the number specified for the SET DRMDBBACKUPEXPIREDAYS command. For more information, see Administrator's Guide. |
To remove an existing value, specify a null string ("").
Examples
Task
Update the copy storage pool named TAPEPOOL2 to change the delay for volume reuse to 30 days and to collocate files by client node.
Table 311. Commands Related to UPDATE STGPOOL
Command | Description |
---|---|
BACKUP STGPOOL | Backs up a primary storage pool to a copy storage pool. |
DEFINE STGPOOL | Defines a storage pool as a named collection of server storage media. |
DELETE STGPOOL | Deletes a storage pool from server storage. |
MOVE DRMEDIA | Moves DRM media onsite and offsite. |
MOVE MEDIA | Moves storage pool volumes that are managed by an automated library. |
QUERY DRMEDIA | Displays information about disaster recovery volumes. |
QUERY STGPOOL | Displays information about storage pools. |
RESTORE STGPOOL | Restores files to a primary storage pool from copy storage pools. |
RESTORE VOLUME | Restores files stored on specified volumes in a primary storage pool from copy storage pools. |
SET DRMDBBACKUPEXPIREDAYS | Specifies criteria for database backup series expiration. |