Use this command to display information about one or more storage pools. You can also use this command to monitor migration processes for the storage pool.
Privilege class
Any administrator can issue this command.
Syntax
.-*---------. .-Format--=--Standard-----. >>-Query STGpool--+-----------+--+-------------------------+----> '-pool_name-' '-Format--=--+-Standard-+-' '-Detailed-' .-POoltype--=--ANY------------. >--+-----------------------------+----------------------------->< '-POoltype--=--+-ANY--------+-' +-PRimary----+ +-COpy-------+ '-ACTIVEdata-'
Parameters
- pool_name
- Specifies the storage pool to query. This parameter is optional. You can use wildcard characters to specify this name. If you do not specify a value for this parameter, all storage pools are displayed.
- Format
- Specifies how the information is displayed. This parameter is
optional. The default value is STANDARD. Possible values are:
- Standard
- Specifies that partial information is displayed.
- Detailed
- Specifies that complete information is displayed.
- POoltype
- Specifies the type of storage pool to query. This parameter is
optional. The default value is ANY. Possible values are:
- ANY
- Query primary storage pools, copy storage pools, and active-data pools.
- PRimary
- Query only primary storage pools.
- COpy
- Query only copy storage pools.
- ACTIVEdata
- Query only active-data pools.
Example: Display detailed random-access disk storage pool information
Display details for the storage pool named DISKPOOL. See Field descriptions for field descriptions.query stgpool diskpool format=detailed Storage Pool Name: DISKPOOL
Storage Pool Type: Primary
Device Class Name: DISK
Estimated Capacity: 66 G
Space Trigger Util: 0.0
Pct Util: 0.0
Pct Migr: 3.1
Pct Logical: 100.0
High Mig Pct: 90
Low Mig Pct: 70
Migration Delay: 0
Migration Continue: Yes
Migration Processes: 1
Reclamation Processes: 1
Next Storage Pool:
Reclaim Storage Pool:
Maximum Size Threshold: No Limit
Access: Read/Write
Description:
Overflow Location:
Cache Migrated Files?:
Collocate?: Group
Reclamation Threshold: 60
Offsite Reclamation Limit:
Maximum Scratch Volumes Allowed: 32
Number of Scratch Volumes Used: 1
Delay Period for Volume Reuse: 0 Day(s)
Migration in Progress?: No
Amount Migrated (MB): 0.00
Elapsed Migration Time (seconds): 0
Reclamation in Progress?: No
Last Update by (administrator): SERVER_CONSOLE
Last Update Date/Time: 02/24/2005 13:57:16
Storage Pool Data Format: Native
Copy Storage Pool(s):
Active-data Pool(s):
Continue Copy on Error?: No
CRC Data: Yes
Reclamation Type: Threshold
Overwrite Data when Deleted: 2 Time(s)
Deduplicate Data: No
Processes for Identifying Duplicates:
Duplicate Data Not Stored:
Autocopy Mode: Client
Contains data deduplicated by clients?: NoExample: Display detailed sequential-access disk storage pool information
Display details for the storage pool named FILEPOOL. See Field descriptions for field descriptions.query stgpool filepool format=detailed Storage Pool Name: FILEPOOL
Storage Pool Type: Primary
Device Class Name: FILEC
Estimated Capacity: 66 G
Space Trigger Util: 0.0
Pct Util: 0.0
Pct Migr: 3.1
Pct Logical: 100.0
High Mig Pct: 90
Low Mig Pct: 70
Migration Delay: 0
Migration Continue: Yes
Migration Processes: 1
Reclamation Processes: 1
Next Storage Pool:
Reclaim Storage Pool:
Maximum Size Threshold: No Limit
Access: Read/Write
Description:
Overflow Location:
Cache Migrated Files?:
Collocate?: Group
Reclamation Threshold: 60
Offsite Reclamation Limit:
Maximum Scratch Volumes Allowed: 32
Number of Scratch Volumes Used: 1
Delay Period for Volume Reuse: 0 Day(s)
Migration in Progress?: No
Amount Migrated (MB): 0.00
Elapsed Migration Time (seconds): 0
Reclamation in Progress?: No
Last Update by (administrator): SERVER_CONSOLE
Last Update Date/Time: 02/24/2005 13:57:16
Storage Pool Data Format: Native
Copy Storage Pool(s):
Active-data Pool(s):
Continue Copy on Error?: No
CRC Data: Yes
Reclamation Type: Threshold
Overwrite Data when Deleted: 2 Time(s)
Deduplicate Data: Yes
Processes for Identifying Duplicates: 2
Duplicate Data Not Stored: 1 GB
Autocopy Mode: Client
Contains data deduplicated by clients?: YesExample: Display detailed sequential storage pool information
Display details for the active-data sequential storage pool named FILEPOOL that uses a FILE-type device class. See Field descriptions for field descriptions.query stgpool filepool format=detailed Storage Pool Name: FILEPOOL
Storage Pool Type: Active-data
Device Class Name: FILEC
Estimated Capacity: 0.0 M
Space Trigger Util: 0.0
Pct Util: 0.0
Pct Migr: 0.0
Pct Logical: 0.0
High Mig Pct: 90
Low Mig Pct: 70
Migration Delay: 0
Migration Continue: Yes
Migration Processes: 1
Reclamation Processes: 1
Next Storage Pool:
Reclaim Storage Pool:
Maximum Size Threshold: No Limit
Access: Read/Write
Description:
Overflow Location:
Cache Migrated Files?:
Collocate?: Group
Reclamation Threshold: 60
Offsite Reclamation Limit:
Maximum Scratch Volumes Allowed: 99
Number of Scratch Volumes Used: 0
Delay Period for Volume Reuse: 0 Day(s)
Migration in Progress?: No
Amount Migrated (MB): 0.00
Elapsed Migration Time (seconds): 0
Reclamation in Progress?: No
Last Update by (administrator): SERVER_CONSOLE
Last Update Date/Time: 05/03/2004 11:37:57
Storage Pool Data Format: Native
Copy Storage Pool(s):
Active-data Pool(s):
Continue Copy on Error:
CRC Data: Yes
Reclamation Type: Threshold
Deduplicate Data: No
Processes for Identifying Duplicates:
Duplicate Data Not Stored:
Contains data deduplicated by clients?: NoExample: Display summary information for a specific storage pool
Display information for the storage pool named POOL1. See Field descriptions for field descriptions.query stgpool pool1Storage Device Estimated Pct Pct High Low Next
Pool Name Class Name Capacity Util Migr Mig Mig Storage
Pct Pct Pool
---------- ---------- --------- ----- ----- ---- ---- --------
POOL1 DISK 58.5 M 0.8 0.7 90 70 POOL2Example: Display detailed 8 mm tape storage pool information
Display details for the storage pool named 8MMPOOL. See Field descriptions for field descriptions.query stgpool 8mmpool format=detailed Storage Pool Name: 8MMPOOL
Storage Pool Type: Primary
Device Class Name: 8MMTAPE
Estimated Capacity: 0.0 M
Space Trigger Util: 0.0
Pct Util: 0.0
Pct Migr:
Pct Logical: 0.0
High Mig Pct: 90
Low Mig Pct: 70
Migration Delay: 0
Migration Continue: Yes
Migration Processes: 1
Reclamation Processes: 1
Next Storage Pool:
Reclaim Storage Pool:
Maximum Size Threshold: 5 M
Access: Read/Write
Description: Main storage pool
Overflow Location: Room1234/Bldg31
Cache Migrated Files?:
Collocate?: No
Reclamation Threshold: 60
Offsite Reclamation Limit:
Maximum Scratch Volumes Allowed: 5
Number of Scratch Volumes Used: 3
Delay Period for Volume Reuse: 0 Day(s)
Migration in Progress?: No
Amount Migrated (MB): 0.00
Elapsed Migration Time (seconds): 0
Reclamation in Progress?: No
Last Update by (administrator): ADMIN
Last Update Date/Time: 03/22/2002 06:55:45
Storage Pool Data Format: Native
Copy Storage Pool(s): COPYPOOL1
Active-data Pools: ACTIVEPOOL1 ACTIVEPOOL2
Continue Copy on Error: Yes
CRC Data: Yes
Reclamation Type: Threshold
Deduplicate Data: No
Processes for Identifying Duplicates:
Duplicate Data Not Stored:
Autocopy Mode: Client
Contains data deduplicated by clients?: NoExample: Display detailed NAS2CLASS storage pool information
Display details for a storage pool, NAS2LIBPOOL. When you set up this storage pool, you set the data format to NETAPPDUMP. See Field descriptions for field descriptions.query stgpool nas2libpool format=detailed Storage Pool Name: NAS2
Storage Pool Name: NAS2LIBPOOL
Storage Pool Type: Primary
Device Class Name: NAS2CLASS
Estimated Capacity: 0.0 M
Space Trigger Util:
Pct Util: 0.0
Pct Migr:
Pct Logical: 0.0
High Mig Pct:
Low Mig Pct:
Migration Delay:
Migration Continue:
Migration Processes:
Reclamation Processes:
Next Storage Pool:
Reclaim Storage Pool:
Maximum Size Threshold:
Access: Read/Write
Description:
Overflow Location:
Cache Migrated Files?:
Collocate?: Group
Reclamation Threshold:
Offsite Reclamation Limit:
Maximum Scratch Volumes Allowed: 50
Number of Scratch Volumes Used: 0
Delay Period for Volume Reuse: 0 Day(s)
Migration in Progress?:
Amount Migrated (MB):
Elapsed Migration Time (seconds):
Reclamation in Progress?:
Last Update by (administrator): SERVER_CONSOLE
Last Update Date/Time: 07/08/2004 16:24:43
Storage Pool Data Format: NetApp Dump
Copy Storage Pool(s):
Active-data Pool(s):
Continue Copy on Error?: No
CRC Data: No
Reclamation Type:
Deduplicate Data: No
Processes for Identifying Duplicates:
Duplicate Data Not Stored:
Autocopy Mode: Client
Contains data deduplicated by clients?: NoField descriptions
- Storage Pool Name
- The name of the storage pool.
- Storage Pool Type
- The type of storage pool.
- Device Class Name
- The name of the device class that is assigned to the storage pool.
- Estimated Capacity
- The estimated capacity of the storage pool in megabytes (M)
or gigabytes (G).
For DISK devices, estimated capacity is the capacity of all volumes in the storage pool, including any volumes that are varied offline.
For sequential-access storage pools, estimated capacity is the total estimated space of all the sequential-access volumes in the storage pool, regardless of their access mode. At least one volume must be used in a sequential-access storage pool (either a scratch volume or a private volume) to calculate estimated capacity.
For tape and FILE, the estimated capacity for the storage pool includes the following factors:- The capacity of all the scratch volumes that the storage pool already acquired or can acquire. The number of scratch volumes is defined by the MAXSCRATCH parameter on the DEFINE STGPOOL or UPDATE STGPOOL command.
- The capacity of all the private volumes that are defined to the storage pool when using the DEFINE VOLUME command.
- The estimated capacity of the storage pool cannot be more than the capacity of the total file systems that are used by the device class.
For Centera, this represents the total capacity of the Centera storage device that is being queried.
- Space Trigger Util
- Utilization of the storage pool, as calculated by the storage
pool space trigger, if any, for this storage pool. You can define
space triggers for storage pools that are associated with DISK or
FILE device types only.
For sequential access devices, space trigger utilization is expressed as a percentage of the number of used bytes on each sequential access volume relative to the size of the volume, and the estimated capacity of all existing volumes in the storage pool. It does not include potential scratch volumes. Unlike the calculation for percent utilization (Pct Util), the calculation for space trigger utilization favors creation of new private file volumes by the space trigger over usage of additional scratch volumes.
For disk devices, space trigger utilization is expressed as a percentage of the estimated capacity, including cached data. However, it excludes data that resides on any volumes that are varied offline. The value for space trigger utilization can be higher than the value for percent migration (Pct Migr) if you issue QUERY STGPOOL while a file creation is in progress. The value for space trigger utilization is determined by the amount of space that is allocated while the transaction is in progress. The value for percent migration represents only the space that is occupied by committed files. At the end of the transaction, these values are synchronized.
The value for space trigger utilization includes cached data on disk volumes. Therefore, when cache is enabled and migration occurs, the value remains the same because the migrated data remains on the volume as cached data. The value decreases only when the cached data expires or when the space that cached files occupy must be used for no-cached files.
- Pct Util
- An estimate of the utilization of the storage pool, as a percentage.
For sequential access devices, this is expressed as a percentage of the number of active bytes on each sequential access volume and the estimated capacity of all volumes in the storage pool, including the number of potential scratch volumes that might be allocated.
For disk devices, this is expressed as a percentage of the estimated capacity, including cached data and data that resides on any volumes that are varied offline. The value for Pct Util can be higher than the value for Pct Migr if you issue this command while a file creation transaction is in progress. The value for Pct Util is determined by the amount of space allocated (while the transaction is in progress). The value for Pct Migr represents only the space that is occupied by committed files. At the end of the transaction, these values become synchronized.
The Pct Util value includes cached data on disk volumes. Therefore, when cache is enabled and migration occurs, the Pct Util value remains the same because the migrated data remains on the volume as cached data. The Pct Util value decreases only when the cached data expires or when the space that cached files occupy must be used for noncached files.
For Centera, this represents an estimate of the utilization of the entire Centera storage device, not the storage pool that is being queried.
- Pct Migr (primary storage pools only)
- An estimate of the percentage of data in the storage pool that
can be migrated. The server uses this value and the high and low migration
thresholds to determine when to start and stop migration.
For random-access disk devices, this value is specified as a percentage of the value for the estimated capacity, excluding cached data, but including data on any volumes varied offline.
For sequential-access disk devices, this value is specified as a percentage of the value for the estimated capacity, including the capacity of all the scratch volumes that are specified for the pool. For other types of sequential-access devices, this value is the percentage of the total number of volumes in the pool that contain at least one byte of active data. The total number of volumes includes the maximum number of scratch volumes.
The Pct Util value includes cached data on a volume; the Pct Migr value excludes cached data. Therefore, when cache is enabled and migration occurs, the Pct Migr value decreases but the Pct Util value remains the same because the migrated data remains on the volume as cached data. The Pct Util value decreases only when the cached data expires or when the space that cached files occupy must be used for noncached files.
- Pct Logical
- The logical occupancy of the storage pool as a percentage of the total occupancy. Logical occupancy is space that is occupied by client files that might or might not be part of an aggregate. A Pct Logical value less than 100% indicates that there is vacant space within aggregates in the storage pool.
- High Mig Pct (primary storage pools only)
- The high migration threshold, which specifies when the server can begin migration for the storage pool. The server starts migration processes when capacity utilization reaches this threshold.
- Low Mig Pct (primary storage pools only)
- The low migration threshold, which specifies when the server can stop migration for the storage pool. The server stops migration processes when capacity utilization reaches this threshold.
- Migration Delay (primary storage pools only)
- The minimum number of days that a file must remain in a storage pool before the server can migrate the file to the next storage pool. For a disk storage pool, the days are counted from the time that the file was stored in the storage pool or last retrieved by a client. For a sequential access storage pool, the days are counted from the time that the file was stored in the storage pool.
- Migration Continue (primary storage pools only)
- Whether the server continues to migrate files to the next storage pool even if the files have not been in the pool for the number of days specified by the migration delay.
- Migration Processes
- The number of parallel processes that are used for migrating files from a random or sequential access primary storage pool.
- Reclamation Processes
- The number of parallel processes that are used for reclaiming the volumes in a sequential access primary or copy storage pool.
- Next Storage Pool (primary storage pools only)
- The storage pool that is the destination for data that is migrated from this storage pool.
- Reclaim Storage Pool (primary, sequential access storage pools only)
- If specified, the storage pool that is the destination for data that is moved from volumes during reclamation processing. If no pool is specified, by default reclamation processing moves data only among volumes within the same storage pool.
- Maximum Size Threshold (primary storage pools only)
- The maximum size of files that might be stored in the storage pool.
- Access
- How the data in the storage pool can be accessed.
- Description
- The description of the storage pool.
- Overflow Location (sequential access storage pools only)
- The location where volumes in the storage pool are stored when they are ejected from an automated library with the MOVE MEDIA command.
- Cache Migrated Files? (random access storage pools only)
- Whether caching is enabled for files that are migrated to the next storage pool.
- Collocate? (sequential access storage pools only)
- Whether collocation is disabled or enabled. If collocation is disabled, the value of this field is No. If collocation is enabled, the possible values are Group, Node, and Filespace.
- Reclamation Threshold (sequential access storage pools only)
- The threshold that determines when volumes in a storage pool are reclaimed. The server compares the percentage of reclaimable space on a volume to this value to determine if reclamation is necessary.
- Offsite Reclamation Limit
- The number of offsite volumes having their space reclaimed during reclamation for this storage pool. This field applies only when POOLTYPE=COPY.
- Maximum Scratch Volumes Allowed (sequential access storage pools only)
- The maximum number of scratch volumes that the server can request for the storage pool.
- Number of Scratch Volumes Used (sequential access storage pools only)
- The number of scratch volumes that are used in the storage pool.
- Delay Period for Volume Reuse (sequential access storage pools only)
- The number of days that must elapse after all files have been deleted from a volume before the server returns the volume to scratch or reuses the volume.
- Migration in Progress? (primary storage pools only)
- Whether at least one migration process is active for the storage pool.
- Amount Migrated (MB) (primary storage pools only)
- The amount of data, in megabytes, that has been migrated, if migration is in progress. If migration is not in progress, this value indicates the amount of data that was migrated during the last migration. When multiple, parallel migration processes are used for the storage pool, this value indicates the total amount of data migrated by all processes.
- Elapsed Migration Time (seconds) (primary storage pools only)
- The amount of time that has elapsed since migration began, if migration is active. If migration is not active, this value indicates the amount of time that is required to complete the last migration. When multiple, parallel migration processes are used for the storage pool, this value indicates the total time from the beginning of the first process until the completion of the last process.
- Reclamation in Progress? (sequential access storage pools only)
- Whether a reclamation process is active for the storage pool.
- Last Update by (administrator)
- The name of the administrator that has defined or most recently updated the storage pool.
- Last Update Date/Time
- The date and time that an administrator defined or most recently updated the storage pool.
- Storage Pool Data Format
- The type of data format used to write data to this storage pool (for example NATIVE, NETAPPDUMP, CELERRADUMP, or NDMPDUMP).
- Copy Storage Pool (s)
- The copy storage pools that are listed here have data simultaneously written to them when data is backed up or archived to the primary storage pool queried by this command.
- Active-data Pool(s)
- The active-data pools that are listed here have data simultaneously written to them when data is backed up to the primary storage pool queried by this command.
- Continue Copy on Error?
- Whether a server should continue writing data to other copy storage pools in the list or terminate the entire transaction when a write failure occurs to one of the copy pools in the list. This field applies only to primary random-access and primary sequential-access storage pools.
- CRC Data
- Whether data is validated by a cyclic redundancy check (CRC) when data is transferred during data storage and retrieval on a device.
- Reclamation Type
- Whether volumes in this storage pool are reclaimed by threshold or by SnapLock retention date.
- Overwrite Data when Deleted
- The number of times data will be physically overwritten after it is deleted from the database.
- Deduplicate Data
- Whether data in the storage pool is deduplicated.
- Processes for Identifying Duplicates
- The number of duplicate-identification processes that are specified as the default for the storage pool. The number of duplicate-identification processes that are specified in this field might not equal the number of duplicate-identification processes that are running.
- Duplicate Data Not Stored
- Represents the amount of data that was removed from the storage pool by reclamation processing. The value of this field also represents the amount of storage space that was saved in this storage pool as a result of server-side data deduplication.
- Autocopy Mode
- Indicates whether data
is written simultaneously to copy storage pools or active-data pools
during client store sessions, server import processes, server data
migration processes, or all three operations. The value CLIENT indicates
either client store or server import operations. The value ALL indicates
that simultaneous-write operations occur whenever this pool is a target
for any of the eligible operations.
If the storage pool is a copy storage pool or an active-data pool or if the simultaneous-write function is disabled, this field is blank.
- Contains data deduplicated by clients?
- Indicates whether the storage pool contains data that was deduplicated by clients. Storage pools that contain data that is deduplicated by clients are not accessible for LAN-free data movement by storage agents V6.1 or earlier.
Related commands
| Command | Description |
|---|---|
| COPY ACTIVEDATA | Copies active backup data. |
| DEFINE STGPOOL | Defines a storage pool as a named collection of server storage media. |
| DELETE STGPOOL | Deletes a storage pool from server storage. |
| UPDATE STGPOOL | Changes the attributes of a storage pool. |