IT12737: BACKUP STGPOOL MIGHT NOT PROCESS ALL FRAGMENTS OF A FILE

7.1.4.100-TIV-TSMSRV-AIX
7.1.4.100-TIV-TSMSRV-HP-UX
7.1.4.100-TIV-TSMSRV-Linuxppc64
7.1.4.100-TIV-TSMSRV-Linuxs390
7.1.4.100-TIV-TSMSRV-Linuxx86_64
7.1.4.100-TIV-TSMSRV-SolarisSPARC
7.1.4.100-TIV-TSMSRV-WIN
7.1.5.000-TIV-TSMSRV-AIX
7.1.5.000-TIV-TSMSRV-HP-UX
7.1.5.000-TIV-TSMSRV-Linuxppc64
7.1.5.000-TIV-TSMSRV-Linuxs390x
7.1.5.000-TIV-TSMSRV-Linuxx86_64
7.1.5.000-TIV-TSMSRV-SolarisSPARC
7.1.5.000-TIV-TSMSRV-WIN
IBM Spectrum Protect Server V7.1.4.X interim fix downloads
IBM Spectrum Protect Server V7.1 Fix Pack 5 (7.1.5.000) Downloads

APAR status

• Closed as program error.

Error description

• Problem Description:
  
  A file larger than the MAXFRAGMENTSIZE setting (defaults to
  10000M) is stored in a storage pool as multiple fragments, the
  backup stg <primary_pool> <copy_pool> might not backup all of
  fragments to copy pool. In activity log, there is no message
  showing there is problem for backup storage pool command.
  
  Customer/L2 Diagnostics:
  
  Run the below command;
  
  db2 connect to TSMDB1
  db2 set schema TSDB1
  db2 "select bfsa.poolid, bfsa.objid, afsg.volid,  bfsa.sequence,
  afsg.start from BF_SUPER_AGGREGATES bfsa, AF_SEGMENTS afsg where
  bfsa.bfid = afsg.bfid and bfsa.poolid=afsg.poolid  and
  bfsa.poolid=<primary poolid> and afsg.srvid is not NULL order by
  bfsa.poolid, bfsa.objid, afsg.volid, bfsa.sequence"
  
  If the output for afsg.start of the output records with the same
  volid is not in ascending order, there might be this problem in
  the system.
  
  Tivoli Storage Manager Versions Affected:
  Tivoli Storage Manager V7
  
  Initial Impact:
  High
  
  Additional Keywords:
  TSM; BACKUP STG
  

Local fix

• N/A
  

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.5. 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.
  After applying the fix, resetting the backup optimizations for
  the storage pool.
  

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