Tivoli Header
Administrator's Reference
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-----------'
>--+---------------------+--+---------------------------+------->
'-CRCData--=--+-Yes-+-' '-NEXTstgpool--=--pool_name-'
'-No--'
>--+---------------------+--+--------------------+-------------->
'-HIghmig--=--percent-' '-LOwmig--=--percent-'
>--+-------------------+--+-----------------------+------------->
'-CAChe--=--+-Yes-+-' '-MIGPRocess--=--number-'
'-No--'
>--+-------------------+--+-------------------------+----------->
'-MIGDelay--=--days-' '-MIGContinue--=--+-Yes-+-'
'-No--'
>--+-----------------------------------+------------------------>
| .-,------------. |
| V | |
'-COPYSTGpools--=----copypoolname-+-'
>--+--------------------------+--------------------------------><
'-COPYContinue--=--+-Yes-+-'
'-No--'
Parameters
- pool_name (Required)
- Specifies the storage pool to update. This parameter is
required.
- DESCription
- Specifies a description of the storage pool. This parameter is
optional. The maximum length of the description is 255
characters. Enclose the description in quotation marks if it contains
any blank characters. To remove an existing description, specify a null
string ("").
- ACCess
- Specifies how client nodes and server processes (such as migration and
reclamation) can access files in the storage pool. This parameter is
optional. Possible values are:
- READWrite
- Specifies that 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 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.
- UNAVailable
- Specifies that client nodes cannot access files stored on volumes in 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.
- MAXSIze
-
Specifies the maximum size for a physical file that the server can store in
the storage pool. This parameter is optional. Possible values
are:
- NOLimit
- Specifies that there is no maximum size limit for physical files stored in
the storage pool.
- maximum_file_size
- Limits the maximum physical file size. Specify an integer from 1 to
999999, followed by a scale factor. For example, MAXSIZE=5G
specifies that the maximum file size for this storage pool is 5
gigabytes. Scale factors are:
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.
- CRCData
-
Specifies whether a cyclic redundancy check (CRC) validates storage pool data
when audit volume processing occurs on the server. This parameter is
optional. The default value is NO. By setting CRCDATA to YES and
scheduling an AUDIT VOLUME command you can continually ensure the integrity of
data stored in your storage hierarchy. Possible values are:
- Yes
- Specifies that data is stored containing CRC information, allowing for
audit volume processing to validate storage pool data. This mode
impacts performance because additional overhead is required to calculate and
compare CRC values between the storage pool and the server.
- No
- Specifies that data is stored without CRC information.
- NEXTstgpool
-
Specifies a primary storage pool to which files are migrated. This
parameter is optional. The next storage pool must be a primary storage
pool.
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.
- HIghmig
-
Specifies that the server starts migration for this storage pool when the
amount of data in the pool reaches this percentage of the pool's
estimated capacity. This parameter is optional. You can specify
an integer from 0 to 100.
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.
- LOwmig
-
Specifies that the server stops migration for this storage pool when the
amount of data in the pool reaches this percentage of the pool's
estimated capacity. This parameter is optional. You can specify
an integer from 0 to 99.
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.
- CAChe
-
Specifies whether the migration process leaves a cached copy of a file in this
storage pool after migrating the file to the next storage pool. This
parameter is optional. Possible values are:
- Yes
- Specifies that caching is enabled.
- No
- Specifies that caching is disabled.
Using cache may improve the retrievability of files, but may affect the
performance of other processes. See Administrator's
Guide for details.
- MIGPRocess
-
Specifies the number of processes that are used for migrating files from this
storage pool. This parameter is optional. You can specify an
integer from 1 to 999.
During migration, these processes are performed in parallel to provide the
potential for improved migration rates.
- Note:
- 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.
- MIGDelay
- Specifies the minimum number of days that a file must remain in a storage
pool before the file becomes eligible for migration from the storage
pool. The server counts the number of days from the day that the file
was stored in the storage pool or retrieved by a client, whichever is more
recent. This parameter is optional. You can specify an integer
from 0 to 9999. The value 0 specifies that you do not want to delay
migration.
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.
- MIGContinue
- Specifies whether you allow the server to migrate files that do not
satisfy the migration delay time. This parameter is optional.
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:
- 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.
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.
- 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.
- COPYSTGpools
-
Specifies 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. This
parameter is optional. The maximum length of the copy pool name is 30
characters. You can specify a maximum of 10 copy pool names separated
by commas and no intervening spaces. This option is restricted to only
primary storage pools using NATIVE or NONBLOCK data format. When
specifying the COPYSTGPOOLS parameter, you may also specify the COPYCONTINUE
parameter. For additional information, see the COPYCONTINUE
parameter.
- Note:
- The function provided by the COPYSTGPOOLS parameter is not intended to
replace the BACKUP STGPOOL command. If you use the COPYSTGPOOLS
parameter, continue to use the BACKUP STGPOOL command to ensure that the copy
storage pools are complete copies of the primary storage pool. There
are cases when a copy may not be created. For more information, see the
COPYCONTINUE parameter description.
- COPYContinue
-
Specifies how the server should react to a copy storage pool write failure for
any of the copy storage pools listed in the COPYSTGPOOLS parameter.
This parameter is optional. When specifying the COPYCONTINUE parameter
and either a COPYSTGPOOLS list must already exist or the COPYSTGPOOLS
parameter must also be specified. Possible values are:
- 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
pools in the list. If the failing copy pool has not recovered, this
will probably result in failed transactions. An example of a
transaction is a single backup or archive operation.
Examples
Task
Update the random access storage pool named BACKUPPOOL to permit caching
when the server migrates files to the next storage pool.
- Command:
- update stgpool backuppool cache=yes
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-----------'
>--+---------------------+--+---------------------------+------->
'-CRCData--=--+-Yes-+-' '-NEXTstgpool--=--pool_name-'
'-No--'
>--+---------------------+--+--------------------+-------------->
'-HIghmig--=--percent-' '-LOwmig--=--percent-'
>--+---------------------+--+------------------------------+---->
'-REClaim--=--percent-' '-RECLAIMSTGpool--=--pool_name-'
>--+-----------------------------+--+-----------------------+--->
'-COLlocate--=--+-No--------+-' '-MAXSCRatch--=--number-'
+-Yes-------+
'-FILespace-'
>--+---------------------+--+-------------------+--------------->
'-REUsedelay--=--days-' '-MIGDelay--=--days-'
>--+-------------------------+---------------------------------->
'-MIGContinue--=--+-Yes-+-'
'-No--'
>--+-----------------------------------+------------------------>
| .-,------------. |
| V | |
'-COPYSTGpools--=----copypoolname-+-'
>--+--------------------------+--------------------------------><
'-COPYContinue--=--+-Yes-+-'
'-No--'
Parameters
- pool_name (Required)
- Specifies the name of the storage pool to be updated.
- DESCription
- Specifies a description of the storage pool. This parameter is
optional. The maximum length of the description is 255
characters. Enclose the description in quotation marks if it contains
any blank characters. To remove an existing description, specify a null
string ("").
- ACCess
- Specifies how client nodes and server processes (such as migration and
reclamation) can access files in the storage pool. This parameter is
optional. Possible values are:
- READWrite
- Specifies that 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 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.
- UNAVailable
- Specifies that client nodes cannot access files stored on volumes in 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.
- MAXSIze
-
Specifies the maximum size for a physical file that the server can store in
the storage pool during a session with a client. This parameter is
optional. Possible values are:
- NOLimit
- Specifies that there is no maximum size limit for physical files stored in
the storage pool.
- maximum_file_size
- Limits the maximum physical file size. Specify an integer from 1 to
999999, followed by a scale factor. For example, MAXSIZE=5G
specifies that the maximum file size for this storage pool is 5
gigabytes. Scale factors are:
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.
Notes:
- 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.
- CRCData
-
Specifies whether a cyclic redundancy check (CRC) validates storage pool data
when audit volume processing occurs on the server. This parameter is
only valid for NATIVE data format storage pools. This parameter is
optional. The default value is NO. By setting CRCDATA to YES and
scheduling an AUDIT VOLUME command you can continually ensure the integrity of
data stored in your storage hierarchy. Possible values are:
- Yes
- Specifies that data is stored containing CRC information, allowing for
audit volume processing to validate storage pool data. This mode
impacts performance because additional overhead is required to calculate and
compare CRC values between the storage pool and the server.
- No
- Specifies that data is stored without CRC information.
- NEXTstgpool
-
Specifies a primary storage pool to which files are migrated. This
parameter is optional. The next storage pool must be a primary storage
pool.
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.
- HIghmig
-
Specifies that the server starts migration for this storage pool when the
number of volumes containing data reaches this percentage of the total number
of volumes in the storage pool. The total number of volumes includes
the maximum number of scratch volumes. This parameter is
optional. You can specify an integer from 1 to 100.
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 to 100 to
prevent migration for the storage pool.
- LOwmig
-
Specifies that the server stops migration for this storage pool when the
number of volumes containing data reaches this percentage of the total number
volumes in the storage pool. The total number of volumes includes the
maximum number of scratch volumes. This parameter is optional.
You can specify an integer from 0 to 99.
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.
- REClaim
-
Specifies when the server reclaims a volume, based on the percentage of
reclaimable space on a volume. Reclamation makes the fragmented space
on volumes usable again by moving any remaining unexpired files from one
volume to another volume, thus making the original volume available for
reuse. This parameter is optional. You can specify an integer
from 1 to 100.
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.
- RECLAIMSTGpool
- Specifies another primary storage pool as a target for reclaimed data from
this storage pool. This parameter is optional. When the server
reclaims volumes for the storage pool, unexpired data is moved from the
volumes being reclaimed to the storage pool named with this parameter.
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.
- COLlocate
-
Specifies whether the server attempts to keep data belonging to a single
client node or client file space assigned to as few volumes as
possible. This parameter is optional.
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:
- Yes
- Specifies that collocation is enabled at the client node level. The
server tries to put data for one node on as few volumes as possible. If
the node has multiple file spaces, no attempt is made to collocate those file
spaces.
- 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
attempts to put data for different file spaces on different volumes.
- MAXSCRatch
- Specifies the maximum number of scratch volumes that the server can
request. This parameter is optional. You can specify an integer
from 0 to 100000000. By allowing the server to request scratch volumes,
you avoid having to define each volume to be used.
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.
- REUsedelay
-
Specifies the number of days that must elapse after all files are deleted from
a volume before the volume can be rewritten or returned to the scratch
pool. This parameter is optional. You can specify an integer
from 0 to 9999. The value 0 means that a volume can be rewritten or
returned to the scratch pool as soon as all files are deleted from the
volume.
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.
- MIGDelay
- Specifies the minimum number of days since a file was stored in the
storage pool before the file becomes eligible for migration from the storage
pool. This parameter is optional. You can specify an integer
from 0 to 9999. The value 0 specifies that migration is not
delayed.
- MIGContinue
- Specifies whether you allow the server to migrate files that do not
satisfy the migration delay time. This parameter is optional.
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:
- Yes
- Specifies that, when necessary to meet the low migration threshold, the
server continues to migrate files that have not been stored in the storage
pool for the number of days specified by the migration delay period.
- 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 have been stored in the storage
pool for the number of days specified by the migration delay period.
- COPYSTGpools
-
Specifies 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. This
parameter is optional. The maximum length of the copy pool name is 30
characters. You can specify a maximum of 10 copy pool names separated
by commas and no intervening spaces. This option is restricted to only
primary storage pools using NATIVE or NONBLOCK data format. When
specifying the COPYSTGPOOLS parameter, you may also specify the COPYCONTINUE
parameter. For additional information, see the COPYCONTINUE
parameter.
- Note:
- The function provided by the COPYSTGPOOLS parameter is not intended to
replace the BACKUP STGPOOL command. If you use the COPYSTGPOOLS
parameter, continue to use the BACKUP STGPOOL command to ensure that the copy
storage pools are complete copies of the primary storage pool. There
are cases when a copy may not be created. For more information, see the
COPYCONTINUE parameter description.
- COPYContinue
-
Specifies how the server should react to a copy storage pool write failure for
any of the copy storage pools listed in the COPYSTGPOOLS parameter.
This parameter is optional. The default is YES. When specifying
the COPYCONTINUE parameter and either a COPYSTGPOOLS list must already exist
or the COPYSTGPOOLS parameter must also be specified. Possible values
are:
- 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
pools in the list. If the failing copy pool has not recovered, this
will probably result in failed transactions. An example of a
transaction is a single backup or archive operation.
Examples
Task
Update the primary sequential storage pool named TAPEPOOL1 to permit as
many as 10 scratch volumes to be mounted.
- Command:
- update stgpool tapepool1 maxscratch=10
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--------+-' '-REClaim--=--percent-'
+-Yes-------+
'-FILespace-'
>--+-----------------------+--+---------------------+----------->
'-MAXSCRatch--=--number-' '-REUsedelay--=--days-'
>--+---------------------+-------------------------------------><
'-CRCData--=--+-Yes-+-'
'-No--'
Parameters
- pool_name (Required)
- Specifies the name of the copy storage pool to be updated.
- DESCription
- Specifies a description of the copy storage pool. This parameter is
optional. The maximum length of the description is 255
characters. Enclose the description in quotation marks if it contains
any blank characters. To remove an existing description, specify a null
string ("").
- ACCess
- Specifies how client nodes and server processes (such as reclamation) can
access files in the copy storage pool. This parameter is
optional. Possible values are:
- READWrite
- Specifies that files can be read from and written to the volumes in the
copy storage pool.
- READOnly
- Specifies that client nodes can only read files stored on the volumes in
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.
- UNAVailable
- Specifies that client nodes cannot access files stored on volumes in 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.
- COLlocate
-
Specifies whether the server attempts to keep data belonging to a single
client node or client file space assigned to as few volumes as
possible. This parameter is optional.
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:
- Yes
- Specifies that collocation is enabled at the client node level. The
server tries to put data for one node on as few volumes as possible. If
the node has multiple file spaces, no attempt is made to collocate those file
spaces.
- 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
attempts to put data for different file spaces on different volumes.
- REClaim
- Specifies when the server reclaims a volume, based on the percentage of
reclaimable space on a volume. Reclamation makes the fragmented space
on volumes usable again by moving any remaining active files from one volume
to another volume, thus making the original volume available for reuse.
This parameter is optional. You can specify an integer from 1 to
100. The value 100 means that reclamation is not performed.
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.
- MAXSCRatch
- Specifies the maximum number of scratch volumes that the server can
request for this storage pool. This parameter is optional. You
can specify an integer from 0 to 100000000. By allowing the server to
request scratch volumes as needed, you avoid having to define each volume to
be used.
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.
- REUsedelay
-
Specifies the number of days that must elapse after all files are deleted from
a volume before the volume can be rewritten or returned to the scratch
pool. This parameter is optional. You can specify an integer
from 0 to 9999. A value of 0 means that a volume can be rewritten or
returned to the scratch pool as soon as all files are deleted from the
volume.
- 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.
- CRCData
-
Specifies whether a cyclic redundancy check (CRC) validates storage pool data
when audit volume processing occurs on the server. This parameter is
only valid for NATIVE data format storage pools. This parameter is
optional. The default value is NO. By setting CRCDATA to YES and
scheduling an AUDIT VOLUME command you can continually ensure the integrity of
data stored in your storage hierarchy. Possible values are:
- Yes
- Specifies that data is stored containing CRC information, allowing for
audit volume processing to validate storage pool data. This mode
impacts performance because additional overhead is required to calculate and
compare CRC values between the storage pool and the server.
- No
- Specifies that data is stored without CRC information.
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.
- Command:
- update stgpool tapepool2 reusedelay=30 collocate=yes
Table 279. 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.
|
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.
|
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]