IT02571: With "SPLITLARGEObjects" enabled, BACKUP STGPOOL can REPORT SUCCESS When some bitfiles have not been sent to copy pool.

IBM Tivoli Storage Manager (TSM) server V7.1.0.x interim fix downloads

APAR status

• Closed as program error.

Error description

• With version 7.1 server with node attribute "SPLITLARGEObjects"
  enabled,
  it can happen that backup stgpool can report success but not
  actually
  backup certain files to the copy storage pool.
  This can happen when the first
  fragment(s) has been sent to the copypool already and backup
  stgpool retries as the whole object has not been sent.
  
  For example, running consecutive backup stgpool commands, it can
  be
  seen that same 6 items are reported as backed up each time.
  
  06/01/2014 11:08:52  ANR0986I Process 4756 for BACKUP STORAGE
  POOL
                        running in
                        the BACKGROUND processed 6 items for a
  total of
                        45,374,028,876 bytes with a completion
  state of
                        SUCCESS
                        at 11:08:52 AM. (SESSION: 87293, PROCESS:
  4756)
  06/01/2014 13:09:22  ANR0986I Process 4757 for BACKUP STORAGE
  POOL
                        running in
                        the BACKGROUND processed 6 items for a
  total of
                        45,374,028,876 bytes with a completion
  state of
                        SUCCESS
                        at 01:09:22 PM. (SESSION: 87317, PROCESS:
  4757)
  06/01/2014 15:09:27  ANR0986I Process 4758 for BACKUP STORAGE
  POOL
                        running in
                        the BACKGROUND processed 6 items for a
  total of
                        45,374,028,876 bytes with a completion
  state of
                        SUCCESS
                        at 03:09:27 PM. (SESSION: 87341, PROCESS:
  4758)
  
  No errors are reported in activity log.
  
  Looking at server trace, ( AF BF AS SS BACK BACKD flags in this
  example) the same bitfiles are seen each time for each backup
  stgpool process:
  
  14:02:02.564 [199][afcputil.c][4840][CopyCluster]:Copying
  bitfiles for
  cluster SrvId=0, PoolId=6, Ck1=9, Ck2=2, for volume
  T05011(1020457)
  14:02:27.154 [199][afcputil.c][5595][CopyBatch]:Copying bitfile
  batch
  SrvId=0, PoolId=6, Ck1=9, Ck2=2, Count=1, for volume
  T05011(1020457)
  14:02:27.154 [199][bfcopy.c][227][BfCopy]:Copying bitfile
  24835426 from
  pool 6 to pool -1
  14:04:21.476 [199][afcputil.c][4840][CopyCluster]:Copying
  bitfiles for
  cluster SrvId=0, PoolId=6, Ck1=9, Ck2=2, for volume
  T05111(1020467)
  14:04:21.486 [199][afcputil.c][5595][CopyBatch]:Copying bitfile
  batch
  SrvId=0, PoolId=6, Ck1=9, Ck2=2, Count=4, for volume
  T05111(1020467)
  14:04:21.486 [199][bfcopy.c][227][BfCopy]:Copying bitfile
  24809803 from
  pool 6 to pool -1
  14:06:01.047 [199][bfcopy.c][227][BfCopy]:Copying bitfile
  24809804 from
  pool 6 to pool -1
  14:06:46.591 [199][bfcopy.c][227][BfCopy]:Copying bitfile
  24809805 from
  pool 6 to pool -1
  14:07:31.763 [199][bfcopy.c][227][BfCopy]:Copying bitfile
  24809806 from
  pool 6 to pool -1
  14:08:43.797 [199][afcputil.c][5595][CopyBatch]:Copying bitfile
  batch
  SrvId=0, PoolId=6, Ck1=9, Ck2=2, Count=1, for volume
  T05111(1020467)
  14:08:43.797 [199][bfcopy.c][227][BfCopy]:Copying bitfile
  24809807 from
  pool 6 to pool -1
  
  these bitfiles are fragments in a Super Aggregate and are not
  being backed up
  to copy storage pool. Each backup stgpool will show same
  fragments being copied again.
  
  
  Tivoli Storage Manager versions affected:
  server 7.1 on all platforms
  
  Initial Impact: Medium
  
  Additional Keywords:
  zz71 tsm backup stgpool fragments
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All Tivoli Storage Manager server users.                     *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION.                                       *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing levels when available.                          *
  * This problem is currently projected                          *
  * to be fixed in levels 7.1.0.100 and 7.1.1.                   *
  * 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