Tivoli Header
Administrator's Reference
Use this command to define a primary storage pool or a copy storage
pool. A primary storage pool provides a destination for backup files,
archive files, or files migrated from client nodes. A copy storage pool
provides a destination for backup copies of files that are in primary storage
pools.
All volumes in a storage pool belong to the same device class.
Random access storage pools use the DISK device type. After you define
a random access storage pool, you must define volumes for the pool to create
storage space.
Sequential access storage pools use device classes that you define for tape
devices, optical devices, files on disk (FILE device type), and storage on
another server (SERVER device type). To create storage space in a
sequential access storage pool, you must allow scratch volumes for the pool
when you define or update it, or define volumes for the pool after you define
the pool. You can also do both.
The DEFINE STGPOOL command takes three forms, depending on whether you are
defining a primary storage pool assigned to random access devices, defining a
primary storage pool assigned to sequential access devices, or defining a copy
storage pool (always assigned to sequential access devices). The syntax
and parameters for each form are defined separately.
Use this command to define a primary storage pool assigned to random access
devices.
Privilege Class
To issue this command, you must have system privilege.
Syntax
.-POoltype--=--PRimary-.
>>-DEFine STGpool--pool_name--DISK--+----------------------+---->
'-POoltype--=--PRimary-'
>--+-----------------------------+------------------------------>
'-DESCription--=--description-'
.-ACCess--=--READWrite-------.
>--+----------------------------+------------------------------->
'-ACCess--=--+-READWrite---+-'
+-READOnly----+
'-UNAVailable-'
.-MAXSIze--=--NOLimit-----------. .-CRCData--=--No------.
>--+-------------------------------+--+---------------------+--->
'-MAXSIze--=--maximum_file_size-' '-CRCData--=--+-Yes-+-'
'-No--'
.-HIghmig--=--90------.
>--+---------------------------+--+---------------------+------->
'-NEXTstgpool--=--pool_name-' '-HIghmig--=--percent-'
.-LOwmig--=--70------. .-CAChe--=--No------.
>--+--------------------+--+-------------------+---------------->
'-LOwmig--=--percent-' '-CAChe--=--+-Yes-+-'
'-No--'
.-MIGPRocess--=--1------. .-MIGDelay--=--0----.
>--+-----------------------+--+-------------------+------------->
'-MIGPRocess--=--number-' '-MIGDelay--=--days-'
.-MIGContinue--=--Yes-----.
>--+-------------------------+---------------------------------->
'-MIGContinue--=--+-Yes-+-'
'-No--'
>--+-----------------------------------------------------------------------+-><
| .-COPYContinue--=--Yes-----. |
'-+-------------------------------------+--+--------------------------+-'
| .-,--------------. | '-COPYContinue--=--+-Yes-+-'
| V | | '-No--'
'-COPYSTGpools--=----copy_pool_name-+-'
Parameters
- pool_name (Required)
- Specifies the name of the storage pool to be defined. The maximum
length of the name is 30 characters.
- DISK (Required)
- Specifies that you want to define a storage pool to the DISK device class
(the DISK device class is predefined during installation).
- POoltype=PRimary
- Specifies that you want to define a primary storage pool. This
parameter is optional. The default value is PRIMARY.
- 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.
- ACCess
- Specifies how client nodes and server processes (such as migration and
reclamation) can access files in the storage pool. This parameter is
optional. The default value is READWRITE. 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. The default value is NOLIMIT. 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.
- 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.
- 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.
If you do not specify 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. The default value is 90.
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. The default value is 70.
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. The default value is NO. 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 the server uses for migrating files
from this storage pool. This parameter is optional. You can
specify an integer from 1 to 999. The default value is 1.
During migration, the server runs this number of processes 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 default is 0, which means 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.
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. 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. The default value is YES. When
specifying the COPYCONTINUE parameter, you must also specify the COPYSTGPOOLS
parameter. 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
Define a primary storage pool, POOL1, to use the DISK device class, with
caching enabled. Limit the maximum file size to 5MB. Store any
files larger than 5MB in subordinate storage pools beginning with the PROG2
storage pool. Set the high migration threshold to 70 percent, and the
low migration threshold to 30 percent.
- Command:
-
define stgpool pool1 disk
description="main disk storage pool" maxsize=5m
highmig=70 lowmig=30 cache=yes
nextstgpool=prog2
Use this command to define a primary storage pool assigned to sequential
access devices.
Privilege Class
To issue this command, you must have system privilege.
Syntax
>>-DEFine STGpool--pool_name--device_class_name----------------->
.-POoltype--=--PRimary-.
>--+----------------------+--+-----------------------------+---->
'-POoltype--=--PRimary-' '-DESCription--=--description-'
.-ACCess--=--READWrite-------.
>--+----------------------------+------------------------------->
'-ACCess--=--+-READWrite---+-'
+-READOnly----+
'-UNAVailable-'
.-MAXSIze--=--NOLimit----------------.
>--+------------------------------------+----------------------->
| (1) |
'-MAXSIze--=--maximum_file_size------'
.-CRCData--=--No------.
>--+---------------------+-------------------------------------->
'-CRCData--=--+-Yes-+-'
'-No--'
>--+--------------------------------+--------------------------->
| (1) |
'-NEXTstgpool--=--pool_name------'
.-HIghmig--=--90-----------. .-LOwmig--=--70-----------.
>--+--------------------------+--+-------------------------+---->
| (1) | | (1) |
'-HIghmig--=--percent------' '-LOwmig--=--percent------'
.-REClaim--=--60-----------.
>--+--------------------------+--------------------------------->
| (1) |
'-REClaim--=--percent------'
>--+-----------------------------------+------------------------>
| (1) |
'-RECLAIMSTGpool--=--pool_name------'
.-COLlocate--=--No------------.
>--+-----------------------------+--MAXSCRatch--=--number------->
'-COLlocate--=--+-No--------+-'
+-Yes-------+
'-FILespace-'
.-REUsedelay--=--0----.
>--+---------------------+--+-------------------------------+--->
'-REUsedelay--=--days-' | (1) |
'-OVFLOcation--=--location------'
.-MIGDelay--=--0---------.
>--+------------------------+----------------------------------->
| (1) |
'-MIGDelay--=--days------'
.-MIGContinue--=--Yes----------.
>--+------------------------------+----------------------------->
| (1) |
'-MIGContinue--=--+-No--+------'
'-Yes-'
.-DATAFormat--=--NATive---------.
>--+-------------------------------+---------------------------->
'-DATAFormat--=--+-NATive-----+-'
+-NONblock---+
'-NETAPPDump-'
>--+-----------------------------------------------------------------------+-><
| .-COPYContinue--=--Yes-----. |
'-+-------------------------------------+--+--------------------------+-'
| .-,--------------. | '-COPYContinue--=--+-Yes-+-'
| V | | '-No--'
'-COPYSTGpools--=----copy_pool_name-+-'
Notes:
- For storage pools with DATAFORMAT=NETAPPDUMP this parameter is
unavailable.
Parameters
- pool_name (Required)
- Specifies the name of the storage pool to be defined. The maximum
length of the name is 30 characters.
- device_class_name (Required)
- Specifies the name of the device class to which this storage pool is
assigned. You can specify any device class except for the DISK device
class.
- POoltype=PRimary
- Specifies that you want to define a primary storage pool. This
parameter is optional. The default value is PRIMARY.
- DESCription
- Specifies a description of the storage pool. This parameter is
optional. The maximum length of the description is 255
characters. Enclose the description must in quotation marks if it
contains any blank characters.
- ACCess
- Specifies how client nodes and server processes (such as migration and
reclamation) can access files in the storage pool. This parameter is
optional. The default value is READWRITE. 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. The default value is NOLIMIT. 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.
- This parameter is not available for storage pools with the
NETAPPDUMP data format.
- 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.
If you do not specify 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.
- Note:
- This parameter is not available for storage pools with the
NETAPPDUMP data format.
- 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. The default
value is 90.
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
pool. You can set the high migration threshold to 100 to prevent
migration for the storage pool.
- Note:
- For storage pools with DATAFORMAT=NETAPPDUMP this parameter is
unavailable.
- 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
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 0 to 99. The default
value is 70.
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.
- Note:
- For storage pools with DATAFORMAT=NETAPPDUMP this parameter is
unavailable.
- 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. The default value is 60, except for storage pools that
use WORM devices.
For storage pools that use WORM devices, the default value is 100 to
prevent reclamation from occurring. This is the default because a WORM
volume is not reusable. If necessary, you can lower the value to allow
the server to consolidate data onto fewer volumes. Volumes emptied by
reclamation can be checked out of the library, freeing slots for new
volumes.
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.
- Note:
- For storage pools with DATAFORMAT=NETAPPDUMP this parameter is
unavailable.
- 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, the server moves unexpired data from
the volumes being reclaimed to the storage pool named with this
parameter.
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.
- Note:
- For storage pools with DATAFORMAT=NETAPPDUMP this parameter is
unavailable.
- 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. The default value is
NO.
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 (Required)
- Specifies the maximum number of scratch volumes that the server can
request for this storage pool. 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 default value is 0, which means that a volume can
be rewritten or returned to the scratch pool as soon as all the 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 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.
- OVFLOcation
- Specifies the overflow location for the storage pool. The server
assigns this location name to a volume that is ejected from the library by the
MOVE MEDIA command. This parameter is optional. The location
name can be a maximum length of 255 characters. Enclose the location
name in quotation marks if the location name contains any blank
characters.
- Note:
- For storage pools with DATAFORMAT=NETAPPDUMP this parameter is
unavailable.
- 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 default is 0, which means that you do not want to
delay migration.
- Note:
- For storage pools with DATAFORMAT=NETAPPDUMP, this parameter is
unavailable.
- MIGContinue
- Specifies whether you allow the server to migrate files that have not been
stored in the storage pool for the number of days required by the migration
delay. This parameter is optional. 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. 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.
- Note:
- For storage pools with DATAFORMAT=NETAPPDUMP, this parameter is
unavailable.
- DATAFormat
-
Specifies the data format to use to back up files to this storage pool and
restore files from this storage pool. The default format is the NATIVE
server format. Possible values are:
- 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.
- NETAPPDump
- Specifies the data is in a NetApp dump format. This data format
should be specified for file system images that are in a dump format and that
have been backed up from a Network Appliance file server using Tivoli Data
Protection for NDMP. The server will not perform storage pool backup,
migration, reclamation, MOVE DATA, and AUDIT VOLUME for a storage pool with
DATAFORMAT=NETAPPDUMP.
- 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 default is 0, which means 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.
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. 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. The default value is YES. When
specifying the COPYCONTINUE parameter, you must also specify the COPYSTGPOOLS
parameter. 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
Define a primary storage pool named 8MMPOOL to the 8MMTAPE device class
(with a device type of 8MM) with a maximum file size of 5MB. Store any
files larger than 5MB in subordinate pools, beginning with POOL1.
Enable collocation of files for client nodes. Allow as many as 5
scratch volumes for this storage pool.
- Command:
-
define stgpool 8mmpool 8mmtape maxsize=5m
nextstgpool=pool1 collocate=yes
maxscratch=5
Use this command to define a copy storage pool assigned to sequential access
devices.
Privilege Class
To issue this command, you must have system privilege.
Syntax
>>-DEFine STGpool--pool_name--device_class_name----------------->
>--POoltype--=--COpy--+-----------------------------+----------->
'-DESCription--=--description-'
.-ACCess--=--READWrite-------.
>--+----------------------------+------------------------------->
'-ACCess--=--+-READWrite---+-'
+-READOnly----+
'-UNAVailable-'
.-COLlocate--=--No------------. .-REClaim--=--100-----.
>--+-----------------------------+--+---------------------+----->
'-COLlocate--=--+-No--------+-' '-REClaim--=--percent-'
+-Yes-------+
'-FILespace-'
.-REUsedelay--=--0----.
>--MAXSCRatch--=--number--+---------------------+--------------->
'-REUsedelay--=--days-'
>--+--------------------------+--------------------------------->
'-OVFLOcation--=--location-'
.-DATAFormat--=--NATive-------. .-CRCData--=--No------.
>--+-----------------------------+--+---------------------+----><
'-DATAFormat--=--+-NATive---+-' '-CRCData--=--+-Yes-+-'
'-NONblock-' '-No--'
Parameters
- pool_name (Required)
- Specifies the name of the copy storage pool to be defined. The
maximum length of the name is 30 characters.
- device_class_name (Required)
- Specifies the name of the sequential access device class to which this
copy storage pool is assigned. You can specify any device class except
DISK.
- POoltype=COpy (Required)
- Specifies that you want to define a copy storage pool.
- 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.
- ACCess
- Specifies how client nodes and server processes (such as reclamation) can
access files in the copy storage pool. This parameter is
optional. The default value is READWRITE. 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. The default value is
NO.
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 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. The default value is 100, which means that reclamation
is not performed.
If you change the value from the default, 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 unexpired 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 (Required)
- Specifies the maximum number of scratch volumes that the server can
request for this storage pool. 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. The default value is 0, which means that a volume can
be rewritten or returned to the scratch pool as soon as all the 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.
- OVFLOcation
- Specifies the overflow location for the storage pool. The server
assigns this location name to a volume that is ejected from the library by the
MOVE MEDIA command. This parameter is optional. The location
name can be a maximum length of 255 characters. Enclose the location
name in quotation marks if the location name contains any blank
characters.
- DATAFormat
-
Specifies the data format to use to back up files to this storage pool and
restore files from this storage pool. The default format is the NATIVE
server format. Possible values are:
- 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.
- 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
Define a copy storage pool, TAPEPOOL2, to the DC480 device class.
Allow up to 50 scratch volumes for this pool. Delay the reuse of
volumes for 45 days.
- Command:
-
define stgpool tapepool2 dc480 pooltype=copy
maxscratch=50 reusedelay=45
Table 86. Commands Related to DEFINE STGPOOL
Command
| Description
|
BACKUP DB
| Backs up the Tivoli Storage Manager database to sequential access
volumes.
|
BACKUP STGPOOL
| Backs up a primary storage pool to a copy storage pool.
|
DEFINE DEVCLASS
| Defines a device class.
|
DEFINE VOLUME
| Assigns a volume to be used for storage within a specified storage
pool.
|
DELETE STGPOOL
| Deletes a storage pool from server storage.
|
MOVE MEDIA
| Moves storage pool volumes that are managed by an automated
library.
|
QUERY DEVCLASS
| Displays information about device classes.
|
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 DRMPRIMSTGPOOL
| Specifies that primary storage pools are managed by DRM.
|
UPDATE STGPOOL
| Changes the attributes of a storage pool.
|
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]