wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Viewing IBM Spectrum Protect data deduplication statistics ======

===== Summary =====

You can query data deduplication statistics for all types of storage pools.

Steps
Use the following methods to query data deduplication statistics for all types of storage pools:
  * QUERY OCCUPANCY
  * SELECT * from OCCUPANCY
  * SELECT * from SUMMARY


=== QUERY OCCUPANCY ===

Use the QUERY OCCUPANCY command to show how much space client file spaces occupy. Use this command when you want to issue a command from the command line. You can specify a storage pool to query for files from a specified file space.

Restriction: For container storage pools, you cannot view statistics for the node and file space by using the QUERY OCCUPANCY command. You must use the following commands to display node and file space statistics for container storage pools:
<cli prompt='>'>
    GENERATE DEDUPSTATS
    QUERY DEDUPSTATS
    DELETE DEDUPSTATS
</cli>
   
**Example**
<cli prompt='>'>
SELECT * from OCCUPANCY
</cli>
Use the SELECT * from OCCUPANCY command as part of report generation and automation.

Tip: In the following examples, the REPORTING_MB field value represents the total amount of data that is backed up to the container storage pool. The REPORTING_MB field value is equivalent to the Logical Space Occupied (MB) field on the QUERY OCCUPANCY command.

Example 1
<cli prompt='>'>
Protect: ISPSRV1>select * from DEDUPSTATS

       DATE_TIME: 2019-10-24 10:32:15.000000
    STGPOOL_NAME: CONTAINER2
       NODE_NAME: LNX142L
  FILESPACE_NAME: /
    FILESPACE_ID: 1
            TYPE: Bkup
    PROTECTED_MB: 33
     PHYSICAL_MB: 14
  TOTAL_SAVED_MB: 19
 TOTAL_SAVED_PCT: 56.79
DEDUP_SAVED_SIZE: 5735827
       DEDUP_PCT: 16.58
 NON_DEDUP_COUNT: 2297
  NON_DEDUP_SIZE: 1695643
    UNIQUE_COUNT: 840
     UNIQUE_SIZE: 11601969
    SHARED_COUNT: 33
  SHARED_LOGSIZE: 10221908
  SHARED_PHYSIZE: 1648370
 COMP_SAVED_SIZE: 13910836
  COMP_SAVED_PCT: 48.21
      COMP_COUNT: 639
    UNCOMP_COUNT: 2531
    ENCRYPT_SIZE: 14945982
     ENCRYPT_PCT: 100.00
   ENCRYPT_COUNT: 3170
 UNENCRYPT_COUNT: 0
       REPORT_ID: 1
            DESC:
</cli>

<cli prompt='>'>
Protect: ISPSRV1>q DEDUPSTATS CONTAINER1 LNX142L 

Date/Time               Storage        Node Name      Filespace      FSID     Type     Total Savin-        Total Data
                        Pool Name                     Name                             g Percentage     Protected (MB)
-------------------     ----------     ----------     ----------     ----     ----     ------------     --------------
06/28/2021 12:23:16     CONTAINER1     LNX142L       /                 1     Bkup            93.17                 41
06/28/2021 12:23:16     CONTAINER1     LNX142L       /opt/mqm          3     Bkup            74.82              1,836
</cli>

===== Container too big on replica, using node replication =====

Cache on target storage pool using container is growing abnormally, there are 2 cache on a container
  * Space Used for Protected Data: used for process **protect stgpool**
  * Total Pending Space: used for process **replicate node**

<cli prompt='>'>
Protect: TSM02>q stg f=d
                     Storage Pool Name: CONTAINER01
                     Storage Pool Type: Primary
                     Device Class Name:
                          Storage Type: DIRECTORY                      
                    Estimated Capacity: 80,531 G
         Space Used for Protected Data: 4,671 G
                   Total Pending Space: 300 G
</cli>

To purge these caches, use the associated command.

**Also on source and target you can purge cache**
<cli prompt='>'>
Protect: TSM01>remove stgprotection localstgpool=container01 remoteserver=tsm02  remotestg=container01
</cli>
wiki

User Tools

Site Tools

Page Tools
