IT12864: IDENTIFY DUPLICATES FAILS TO SCAN NEW INGEST IF IDENTIFYPROCESS SET TO 0

7.1.7.000-TIV-TSMSRV-SolarisSPARC
7.1.7.000-TIV-TSMSRV-Linuxs390x
7.1.7.000-TIV-TSMSRV-Linuxppc64
7.1.7.000-TIV-TSMSRV-WIN
7.1.7.000-TIV-TSMSRV-Linuxx86_64
7.1.7.000-TIV-TSMSRV-HP-UX
7.1.7.000-TIV-TSMSRV-AIX
IBM Spectrum Protect Server V7.1 Fix Pack 7 (7.1.7.000) Downloads

APAR status

• Closed as program error.

Error description

• Tivoli Storage Manager server IDENTIFY DUPLICATES process(es)
  will not scan data ingested after the processes were started if
  the IDENTIFYPROCESS parameter on the storage pool definition is
  set to 0.  This issue becomes especially apparent if IDENTIFY
  DUPLICATE processing is running with an infinite duration.
  
  Administrators affected by this issue are likely to notice that
  their IDENTIFY DUPLICATES process(es) initially scanned data,
  but then went IDLE and remain in that state indefinitely,
  despite new data being ingested into the storage pool.
  
  If the IDENTIFY DUPLICATES process(es) are not analyzing newly
  ingested data, then the server-side deduplication ratio will
  likely be lower than expected.
  
  Customer/L2 Diagnostics:
  None.
  
  Initial Impact:
  Medium
  
  Tivoli Storage Manager Versions Affected:
  All supported Tivoli Storage Manager server users of file-
  pool based server data deduplication.
  
  Additional Keywords:
  TSM DEDUP DEDUPE DEDUPLICATION RATIO IDENTIFY ID PERCENT
  IDENTIFYPROCESS STG STGPOOL STGP SPECTRUM PROTECT DUPLICATE
  

Local fix

• To mitigate this issue, the IDENTIFYPROCESS parameter on the
  storage pool definition should be updated to match the
  NUMPROCESS parameter value used on the IDENTIFY DUPLICATES
  command.  Once this update is made, recycle all existing
  IDENTIFY DUPLICATES processes (cancel the existing processes,
  and restart them).
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Tivoli Storage Manager server users.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See error description.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in level 7.1.7. Note that this is      *
  * subject to change at the discretion of IBM.                  *
  ****************************************************************
  

Problem conclusion

• This problem was fixed.
  Affected platforms:  AIX, HP-UX, Solaris, Linux, and Windows.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  TSM SERVER

• Fixed component ID

  5698ISMSV

Applicable component levels

• R71A PSY

     UP

• R71H PSY

     UP

• R71L PSY

     UP

• R71S PSY

     UP

• R71W PSY

     UP