Any administrator can query for information about a storage pool by viewing a standard or a detailed report. Use these reports to monitor storage pool usage, including:
Monitoring the space available in storage pools is important to ensure that client operations such as backup can complete successfully. To make more space available, you may need to define more volumes for disk storage pools, or add more volumes for sequential access storage pools such as tape. For more information on maintaining a supply of volumes in libraries, see Managing Volumes.
To request a standard report that shows all storage pools defined to the system, enter:
query stgpool
Figure 21 shows a standard report with all storage pools defined to the system. To monitor the use of storage pool space, review the Estimated Capacity and Pct Util columns.
Figure 21. Information about Storage Pools
+--------------------------------------------------------------------------------+ |Storage Device Estimated Pct Pct High Low Next | |Pool Name Class Name Capacity Util Migr Mig Mig Storage | | (MB) Pct Pct Pool | |----------- ---------- ---------- ----- ----- ---- ---- ----------- | |ARCHIVEPOOL DISK 0.0 0.0 0.0 90 70 | |BACKTAPE TAPE 180.0 85.0 100.0 90 70 | |BACKUPPOOL DISK 80.0 51.6 51.6 50 30 BACKTAPE | |COPYPOOL TAPE 300.0 42.0 | |ENGBACK1 DISK 0.0 0.0 0.0 85 40 BACKTAPE | | | +--------------------------------------------------------------------------------+
For a disk storage pool, this value reflects the total amount of available space in the storage pool, including any volumes that are varied offline.
For a sequential access storage pool, this value is an estimate of the total amount of available space on all volumes in the storage pool. The total includes volumes with any access mode (read-write, unavailable, read-only, offsite, or destroyed). The total includes scratch volumes that the storage pool can acquire only when the storage pool is using at least one scratch volume for data.
Volumes in a sequential access storage pool, unlike those in a disk storage pool, do not contain a precisely known amount of space. Data is written to a volume as necessary until the end of the volume is reached. For this reason, the estimated capacity is truly an estimate of the amount of available space in a sequential access storage pool.
For disk storage pools, this value reflects the total number of disk blocks currently allocated by TSM. Space is allocated for backed-up, archived, or space-managed files that are eligible for server migration, cached files that are copies of server-migrated files, and files that reside on any volumes that are varied offline.
Note: | The value for Pct Util can be higher than the value for Pct Migr if you query for storage pool information while a client transaction (such as a backup) is in progress. The value for Pct Util is determined by the amount of space actually allocated (while the transaction is in progress). The value for Pct Migr represents only the space occupied by committed files. At the end of the transaction, Pct Util and Pct Migr become synchronized. |
For sequential access storage pools, this value is the percentage of the total bytes of storage available that are currently being used to store active data (data that is not expired). Because the server can only estimate the available capacity of a sequential access storage pool, this percentage also reflects an estimate of the actual utilization of the storage pool.
Figure 21 shows that the estimated capacity for a disk storage pool named BACKUPPOOL is 80MB, which is the amount of available space on disk storage. More than half (51.6%) of the available space is occupied by either backup files or cached copies of backup files.
The estimated capacity for the tape storage pool named BACKTAPE is 180MB, which is the total estimated space available on all tape volumes in the storage pool. This report shows that 85% of the estimated space is currently being used to store workstation files.
Note: | This report also shows that volumes have not yet been defined to the ARCHIVEPOOL and ENGBACK1 storage pools, because the storage pools show an estimated capacity of 0.0MB. |
Task | Required Privilege Class |
---|---|
Display information about volumes | Any administrator |
You can query the server for information about storage pool volumes:
To request general information about all volumes defined to the server, enter:
query volume
Figure 22 shows an example of the output of this standard query. The example illustrates that data is being stored on the 8mm tape volume named WREN01, as well as on several other volumes in various storage pools.
Figure 22. Information about Storage Pool Volumes
+--------------------------------------------------------------------------------+ |Volume Name Storage Device Estimated Pct Volume | | Pool Name Class Name Capacity Util Status | | (MB) | |------------------------ ----------- ---------- --------- ----- -------- | |D:\STOR\AIXVOL.1 AIXPOOL1 DISK 240.0 26.3 On-Line | |D:\STOR\AIXVOL.2 AIXPOOL2 DISK 240.0 36.9 On-Line | |D:\STOR\DOSVOL.1 DOSPOOL1 DISK 240.0 72.2 On-Line | |D:\STOR\DOSVOL.2 DOSPOOL2 DISK 240.0 74.1 On-Line | |D:\STOR\OS2VOL.1 OS2POOL1 DISK 240.0 55.7 On-Line | |D:\STOR\OS2VOL.2 OS2POOL2 DISK 240.0 51.0 On-Line | |WREN00 TAPEPOOL TAPE8MM 2,472.0 0.0 Filling | |WREN01 TAPEPOOL TAPE8MM 2,472.0 2.2 Filling | +--------------------------------------------------------------------------------+
To query the server for a detailed report on volume WREN01 in the storage pool named TAPEPOOL, enter:
query volume wren01 format=detailed
Figure 23 shows the output of this detailed query. Table 18 gives some suggestions on how you can use the information.
Figure 23. Detailed Information for a Storage Pool Volume
+--------------------------------------------------------------------------------+ | Volume Name: WREN01 | | Storage Pool Name: TAPEPOOL | | Device Class Name: TAPE8MM | | Estimated Capacity (MB): 2,472.0 | | Pct Util: 26.3 | | Volume Status: Filling | | Access: Read/Write | | Pct. Reclaimable Space: 5.3 | | Scratch Volume?: No | | In Error State?: No | | Number of Writable Sides: 1 | | Number of Times Mounted: 4 | | Write Pass Number: 2 | | Approx. Date Last Written: 12/04/1996 11:33:26 | | Approx. Date Last Read: 12/03/1996 16:42:55 | | Date Became Pending: | | Number of Write Errors: 0 | | Number of Read Errors: 0 | | Volume Location: | |Last Update by (administrator): TANAGER | | Last Update Date/Time: 12/02/1996 13:20:14 | +--------------------------------------------------------------------------------+
Table 18. Using the Detailed Report for a Volume
Task | Fields and Description |
---|---|
Ensure the volume is available |
Volume Status Access |
Check the Volume Status to see if a disk volume has been
varied offline, or if a sequential access volume is currently being filled
with data.
Check the Access to determine whether files can be read from or written to this volume. | |
Monitor the use of storage space |
Estimated Capacity Pct Util |
The Estimated Capacity is determined by the device class associated with the storage pool to which this volume belongs. Based on the estimated capacity, the system tracks the percentage of space occupied by client files (Pct Util). In this example, 26.3% of the estimated capacity is currently in use. | |
Monitor the error status of the volume. |
Number of Write Errors Number of Read Errors |
The server reports when the volume is in an error state and automatically updates the access mode of the volume to read-only. The Number of Write Errors and Number of Read Errors indicate the type and severity of the problem. Audit a volume when it is placed in error state. See Auditing a Storage Pool Volume for information about auditing a volume. | |
Monitor the life of sequential access volumes that you have defined to the storage pool. |
Scratch Volume? Write Pass Number Number of Times Mounted Approx. Date Last Written Approx. Date Last Read |
The server maintains usage statistics on volumes that are defined to
storage pools. Statistics on a volume explicitly defined by an
administrator remain for as long as the volume is defined to the storage
pool. The server continues to maintain the statistics on defined
volumes even as the volume is reclaimed and reused. However, the server
deletes the statistics on the usage of a scratch volume when the volume
returns to scratch status (after reclamation or after all files are deleted
from the volume).
In this example, WREN01 is a volume defined to the server by an administrator, not a scratch volume (Scratch Volume? is No). The Write Pass Number indicates the number of times the volume has been written to, starting from the beginning of the volume. A value of one indicates that a volume is being used for the first time. In this example, WREN01 has a write pass number of two, which indicates space on this volume may have been reclaimed or deleted once before. Compare this value to the specifications provided with the media that you are using. The manufacturer may recommend a maximum number of write passes for some types of tape media. You may need to retire your tape volumes after reaching the maximum passes to better ensure the integrity of your data. To retire a volume, move the data off the volume by using the MOVE DATA command. See Moving Files from One Volume to Another Volume. Use the Number of Times Mounted, the Approx. Date Last Written, and the Approx. Date Last Read to help you estimate the life of the volume. For example, if more than six months have passed since the last time this volume has been written to or read from, audit the volume to ensure that files can still be accessed. See Auditing a Storage Pool Volume for information about auditing a volume. | |
Determine the location of a volume in a sequential access storage pool. | Location |
When you define or update a sequential access volume, you can give location information for the volume. The detailed query displays this location name. The location information can be useful to help you track volumes, for example, offsite volumes in copy storage pools. | |
Determine if a volume in a sequential access storage pool is waiting for the reuse delay period to expire. | Date Became Pending |
A sequential access volume is placed in the pending state after the last file is deleted or moved from the volume. All the files that the pending volume had contained were expired or deleted, or were moved from the volume. Volumes remain in the pending state for as long as specified with the REUSEDELAY parameter for the storage pool to which the volume belongs. |
Whether or not a volume is full, at times the Pct Util (percent of the volume utilized) plus the Pct Reclaimable Space (percent of the volume that can be reclaimed) may add up to more than 100 percent. This can happen when a volume contains aggregates that have empty space because of files in the aggregates that have expired or been deleted. The Pct Util field shows all space occupied by both non-aggregated files and aggregates, including empty space within aggregates. The Pct Reclaimable Space field includes any space that is reclaimable on the volume, also including empty space within aggregates. Because both fields include the empty space within aggregates, these values may add up to more than 100 percent. For more information about aggregates, see How the Server Groups Files before Storing and Requesting Information on the Use of Storage Space.
Any administrator can request information about the contents of a storage pool volume. Viewing the contents of a storage volume is useful when a volume is damaged or before you do the following:
Because the server tracks the contents of a storage volume through its database, the server does not need to access the requested volume to determine its contents.
The report generated by a QUERY CONTENT command shows the contents of a volume. This report can be extremely large and may take a long time to produce. To reduce the size of this report, narrow your search by selecting one or all of the following search criteria:
To view the first seven backup files on volume WREN01 from file space /usr on client node TOMC, for example, enter:
query content wren01 node=tomc filespace=/usr count=7 type=backup
Figure 24 displays a standard report which shows the first seven files from file space /usr on TOMC stored in WREN01.
Figure 24. A Standard Report on the Contents of a Volume
+--------------------------------------------------------------------------------+ |Node Name Type Filespace Client's Name for File | | Name | |------------------------ ---- ---------- -------------------------------------- | |TOMC Bkup /usr /bin/ acctcom | |TOMC Bkup /usr /bin/ acledit | |TOMC Bkup /usr /bin/ aclput | |TOMC Bkup /usr /bin/ admin | |TOMC Bkup /usr /bin/ ar | |TOMC Bkup /usr /bin/ arcv | |TOMC Bkup /usr /bin/ banner | +--------------------------------------------------------------------------------+
The report lists logical files on the volume. If a file on the volume is an aggregate of logical files (backed-up or archived client files), all logical files that are part of the aggregate are included in the report. An aggregate file can be stored on more than one volume, and therefore not all of the logical files in the report may actually be stored on the volume being queried.
To display detailed information about the files stored on volume VOL1, enter:
query content vol1 format=detailed
Figure 25 displays a detailed report that shows the files stored on VOL1. The report lists logical files and shows whether each file is part of an aggregate file. If a logical file is stored as part of an aggregate file, the information in the Segment Number, Stored Size, and Cached Copy? fields apply to the aggregate, not to the individual logical file.
If a logical file is part of an aggregate file, the Aggregated? field shows the sequence number of the logical file within the aggregate file. For example, the Aggregated? field contains the value 2/4 for the file AB0CTGLO.IDE, meaning that this file is the second of four files in the aggregate. All logical files that are part of an aggregate are included in the report. An aggregate file can be stored on more than one volume, and therefore not all of the logical files in the report may actually be stored on the volume being queried.
For disk volumes, the Cached Copy? field identifies whether the file is a cached copy of a file that has been migrated to the next storage pool in the hierarchy.
Figure 25. Viewing a Detailed Report of the Contents of a Volume
+--------------------------------------------------------------------------------+ | Node Name: DWE | | Type: Bkup | | Filespace Name: OS2 | |Client's Name for File: \ README | | Aggregated?: No | | Stored Size: 27,089 | | Segment Number: 1/1 | | Cached Copy?: No | | | | Node Name: DWE | | Type: Bkup | | Filespace Name: DRIVE_L_K: | |Client's Name for File: \COMMON\DSMCOMMN\ AB0CTCOM.ENT | | Aggregated?: 1/4 | | Stored Size: 202,927 | | Segment Number: 1/1 | | Cached Copy?: No | | | | Node Name: DWE | | Type: Bkup | | Filespace Name: DRIVE_L_K: | |Client's Name for File: \COMMON\DSMCOMMN\ AB0CTGLO.IDE | | Aggregated?: 2/4 | | Stored Size: 202,927 | | Segment Number: 1/1 | | Cached Copy?: No | | | | Node Name: DWE | | Type: Bkup | | Filespace Name: DRIVE_L_K: | |Client's Name for File: \COMMON\DSMCOMMN\ AB0CTTRD.IDE | | Aggregated?: 3/4 | | Stored Size: 202,927 | | Segment Number: 1/1 | | Cached Copy?: No | | | | Node Name: DWE | | Type: Bkup | | Filespace Name: DRIVE_L_K: | |Client's Name for File: \COMMON\DSMCOMMN\ AB0CTSYM.ENT | | Aggregated?: 4/4 | | Stored Size: 202,927 | | Segment Number: 1/1 | | Cached Copy?: No | +--------------------------------------------------------------------------------+
You can use the server's SELECT command to find the sequential volumes used by a client node. Use SELECT to perform an SQL query of the VOLUMEUSAGE table in the TSM database. For example, to get a list of volumes used by the EXCH1 client node in the TAPEPOOL storage pool, enter the following command:
select volume_name from volumeusage where node_name='EXCH1' and stgpool_name='TAPEPOOL'
The results are something like the following:
VOLUME_NAME ------------------ TAPE01 TAPE08 TAPE13 TAPE21
For more information about using the SELECT command, see Administrator's Reference.
Four fields on the standard storage pool report provide you with information about the migration process. They include:
For disk storage pools, this value represents the amount of disk space occupied by backed-up, archived, or space-managed files that can be migrated to another storage pool, including files on volumes that are varied offline. Cached data are excluded in the Pct Migr value.
For sequential access storage pools, this value is the percentage of the total volumes in the storage pool that actually contain data at the moment. For example, assume a storage pool has four explicitly defined volumes, and a maximum scratch value of six volumes. If only two volumes actually contain data at the moment, then Pct Migr will be 20%.
This field is blank for copy storage pools.
Figure 21 shows that the migration thresholds for BACKUPPOOL storage pool are set to 50% for the high migration threshold and 30% for the low migration threshold.
When the amount of migratable data stored in the BACKUPPOOL storage pool reaches 50%, the server can begin to migrate files to BACKTAPE.
To monitor the migration of files from BACKUPPOOL to BACKTAPE, enter:
query stgpool back*
See Figure 26 for an example of the results of this command.
If caching is on for a disk storage pool and files are migrated, the Pct Util value does not change because the cached files still occupy space in the disk storage pool. However, the Pct Migr value decreases because the space occupied by cached files is no longer migratable.
Figure 26. Information on Backup Storage Pools
+--------------------------------------------------------------------------------+ |Storage Device Estimated Pct Pct High Low Next | |Pool Name Class Name Capacity Util Migr Mig Mig Storage | | (MB) Pct Pct Pool | |----------- ---------- ---------- ----- ----- ---- ---- ----------- | |BACKTAPE TAPE 180.0 95.2 100.0 90 70 | |BACKUPPOOL DISK 80.0 51.6 28.8 50 30 BACKTAPE | +--------------------------------------------------------------------------------+
You can query the server to monitor the migration process by entering:
query process
A message similar to Figure 27 is displayed:
Figure 27. Information on the Migration Process
+--------------------------------------------------------------------------------+ | Process Process Description Status | | Number | |-------- ------------------------ --------------------------------------------- | | 2 Migration Disk Storage Pool BACKUPPOOL, Moved Files: | | 1086, Moved Bytes: 25555579, Unreadable | | Files: 0, Unreadable Bytes: 0 | +--------------------------------------------------------------------------------+
When migration is finished, the server displays the following message:
+--------------------------------------------------------------------------------+ |ANR1101I Migration ended for storage pool BACKUPPOOL. | +--------------------------------------------------------------------------------+
A problem can occur that causes the migration process to be suspended. For example, there may not be sufficient space in the storage pool to which data is being migrated. When migration is suspended, the process might be retried.
At this point, a system administrator can:
The server attempts to restart the migration process every 60 seconds for several minutes and if not successful will terminate the migration process.
To stop server migration when a problem occurs or when you need the resources the process is using, you can cancel the migration.
First determine the identification number of the migration process by entering:
query process
A message similar to Figure 28 is displayed:
Figure 28. Getting the Identification Number of the Migration Process
+--------------------------------------------------------------------------------+ | Process Process Description Status | | Number | |-------- ------------------------ --------------------------------------------- | | 1 Migration ANR1113W Migration suspended for storage pool | | BACKUPPOOL - insufficient space in | | subordinate storage pool. | +--------------------------------------------------------------------------------+
Then you can cancel the migration process by entering:
cancel process 1
Some errors cause the server to continue attempting to restart the migration process after 60 seconds. (If the problem still exists after several minutes, the migration process will end.) To stop the repeated attempts at restart, you can change some characteristics of the storage pool from which data is being migrated. Depending on your environment, you can:
In the example in Example: Monitoring the Migration of Data Between Storage Pools, you could update the disk storage pool BACKUPPOOL.
In the example in Example: Monitoring the Migration of Data Between Storage Pools, you could add volumes to the disk storage pool BACKUPPOOL to increase its storage capacity.
Note: | Do this only if you received an out-of-space message for the storage pool to which data is being migrated. |
A migration process can be suspended because of insufficient space in the storage pool to which data is being migrated. To allow the migration process to complete, you can provide additional storage volumes for that storage pool.
In the example in Example: Monitoring the Migration of Data Between Storage Pools, you could add volumes to the BACKTAPE storage pool or increase the maximum number of scratch tapes allowed for it. Either way, you increase the storage capacity of BACKTAPE.
The Pct Util value includes cached data on a volume (when cache is enabled) and the Pct Migr value excludes cached data. Therefore, when cache is enabled and migration occurs, the Pct Migr value decreases while the Pct Util value remains the same. The Pct Util value remains the same because the migrated data remains on the volume as cached data. In this case, the Pct Util value only decreases when the cached data expires.
If you update a storage pool from CACHE=YES to CACHE=NO, the cached files will not disappear immediately. The Pct Util value will be unchanged. The cache space will be reclaimed over time as the server needs the space, and no additional cached files will be created.
To determine whether cache is being used on disk storage and to monitor how much space is being used by cached copies, query the server for a detailed storage pool report. For example, to request a detailed report for BACKUPPOOL, enter:
query stgpool backuppool format=detailed
Figure 29 displays a detailed report for the storage pool.
Figure 29. Detailed Storage Pool Report
+--------------------------------------------------------------------------------+ | Storage Pool Name: BACKUPPOOL | | Storage Pool Type: PRIMARY | | Device Class Name: DISK | | Estimated Capacity (MB): 80.0 | | Pct Util: 42.0 | | Pct Migr: 29.6 | | Pct Logical: 82.1 | | High Mig Pct: 50 | | Low Mig Pct: 30 | | Migration Processes: | | Next Storage Pool: BACKTAPE | | Reclaim Storage Pool: | | Maximum Size Threshold: No Limit | | Access: Read/Write | | Description: | | Overflow Location: | | Cache Migrated Files?: Yes | | Collocate?: | | Reclamation Threshold: | | Maximum Scratch Volumes Allowed: | | Delay Period for Volume Reuse: 0 Day(s) | | Migration in Progress?: Yes | | Amount Migrated (MB): 0.10 | |Elapsed Migration Time (seconds): 5 | | Reclamation in Progress?: | | Volume Being Migrated/Reclaimed: | | Last Update by (administrator): SERVER_CONSOLE | | Last Update Date/Time: 04/07/1997 16:47:49 | +--------------------------------------------------------------------------------+
When Cache Migrated Files? is set to Yes, the value for Pct Util should not change because of migration, because cached copies of files migrated to the next storage pool remain in disk storage.
This example shows that utilization remains at 42%, even after files have been migrated to the BACKTAPE storage pool, and the current amount of data eligible for migration is 29.6%.
When Cache Migrated Files? is set to No, the value for Pct Util more closely matches the value for Pct Migr because cached copies are not retained in disk storage.
Task | Required Privilege Class |
---|---|
Query the server for information about server storage | Any administrator |
Any administrator can request information about server storage occupancy. Use the QUERY OCCUPANCY command for reports with information broken out by node or file space. Use this report to determine the amount of space used by:
Each report gives two measures of the space in use by a storage pool:
The amount of space used for logical files. A logical file is a client file. A logical file is stored either as a single physical file, or in an aggregate with other logical files.
The amount of space used for physical files. A physical file is either a single logical file, or an aggregate file composed of logical files.
An aggregate file may contain empty space that had been used by logical files that are now expired or deleted. Therefore, the amount of space used by physical files is equal to or greater than the space used by logical files. The difference gives you a measure of how much unused space any aggregate files may have. The unused space can be reclaimed in sequential storage pools.
You can also use this report to evaluate the average size of workstation files stored in server storage.
Any administrator can request information about the space used by each client node and file space:
To determine the amount of server storage space used by the /home file space belonging to the client node MIKE, for example, enter:
query occupancy mike /home
Remember that file space names are case-sensitive and must be entered exactly as they are known to the server. Use the QUERY FILESPACE command to determine the correct capitalization. For more information, see Managing File Spaces.
Figure 30 shows the results of the query. The report shows the number of files backed up, archived, or migrated from the /home file space belonging to MIKE. The report also shows how much space is occupied in each storage pool.
If you back up the ENGBACK1 storage pool to a copy storage pool, the copy storage pool would also be listed in the report. To determine how many of the client node's files in the primary storage pool have been backed up to a copy storage pool, compare the number of files in each pool type for the client node.
Figure 30. A Report of the Occupancy of Storage Pools by Client Node
+--------------------------------------------------------------------------------+ | Physical Logical| |Node Name Type Filespace Storage Number of Space Space| | Name Pool Name Files Occupied Occupied| | (MB) (MB)| |--------------- ---- ----------- ----------- --------- ---------- --------| |MIKE Bkup /home ENGBACK1 513 3.52 3.01| +--------------------------------------------------------------------------------+
You can monitor the amount of space being used by an individual storage pool, a group of storage pools, or storage pools categorized by a particular device class. Creating occupancy reports on a regular basis can help you with capacity planning.
To query the server for the amount of data stored in backup tape storage pools belonging to the TAPECLASS device class, for example, enter:
query occupancy devclass=tapeclass
Figure 31 displays a report on the occupancy of tape storage pools assigned to the TAPECLASS device class.
Figure 31. A Report on the Occupancy of Storage Pools by Device Class
+--------------------------------------------------------------------------------+ |Node Name Type Filespace Storage Number of Physical Logical| | Name Pool Name Files Space Space| | Occupied Occupied| | (MB) (MB)| |--------------- ---- ----------- ----------- --------- ---------- --------| |CAROL Arch OS2C ARCHTAPE 5 .92 .89| |CAROL Bkup OS2C BACKTAPE 21 1.02 1.02| |PEASE Arch /home/peas- ARCHTAPE 492 18.40 18.40| | e/dir | |PEASE Bkup /home/peas- BACKTAPE 33 7.60 7.38| | e/dir | |PEASE Bkup /home/peas- BACKTAPE 2 .80 .80| | e/dir1 | |TOMC Arch /home/tomc ARCHTAPE 573 20.85 19.27| | /driver5 | |TOMC Bkup /home BACKTAPE 13 2.02 1.88| +--------------------------------------------------------------------------------+
Note: | For archived data, you may see "(archive)" in the Filespace Name column instead of a file space name. This means that the data was archived before collocation by file space was supported by the server. |
You can query the server for the amount of space used by backed-up, archived, and space-managed files. By determining the average size of workstation files stored in server storage, you can estimate how much storage capacity you might need when registering new client nodes to the server. See Estimating Space Needs for Storage Pools and Estimating Space for Archived Files in a Random Access Storage Pool for information about planning storage space.
To request a report about backup versions stored in the disk storage pool named BACKUPPOOL, for example, enter:
query occupancy stgpool=backuppool type=backup
Figure 32 displays a report on the amount of server storage used for backed-up files.
Figure 32. A Report of the Occupancy of Backed-Up Files in Storage Pools
+--------------------------------------------------------------------------------+ |Node Name Type Filespace Storage Number of Physical Logical| | Name Pool Name Files Space Space| | Occupied Occupied| | (MB) (MB)| |--------------- ---- ----------- ----------- --------- ---------- --------| |CAROL Bkup OS2C BACKUPPOOL 513 23.52 23.52| |CAROL Bkup OS2D BACKUPPOOL 573 20.85 20.85| |PEASE Bkup /marketing BACKUPPOOL 132 12.90 9.01| |PEASE Bkup /business BACKUPPOOL 365 13.68 6.18| |TOMC Bkup / BACKUPPOOL 177 21.27 21.27| +--------------------------------------------------------------------------------+
To determine the average size of backup versions stored in BACKUPPOOL, complete the following steps using the data provided in Figure 32:
In this example, backup versions occupy 92.22MB of space in BACKUPPOOL.
In this example, 1760 backup versions reside in BACKUPPOOL.
In this example, the average size of each workstation file backed up to BACKUPPOOL is about 0.05MB, or approximately 50KB.
You can use this average to estimate the capacity required for additional storage pools that are defined to the server.