IC90812: REPLICATE NODE MAY SEND DATA TWICE

IBM Tivoli Storage Manager V6.3 Fix Pack 5 (6.3.5.000) Server Downloads

APAR status

• Closed as program error.

Error description

• The Tivoli Storage Manager source replication server sends data
  in several transactions to the target replication server.
  
  If in one transaction only the metadata are updated without
  sending the data (objects), then another (data) transaction will
  send the data twice. The target replication server has now two
  copies of the data.
  
  The following node replication process finds these two copies on
  the target replication server and deletes both of them from the
  target replication server.
  
  Next time a node replication process is running, it will find
  no copies on the target replication server and will therefore
  send the data again.
  
  Customer/L2 Diagnostics :
  Example output from actlog on the source replication server:
  
  1. In the first node replication, 111 objects are sent twice
     to the target replication server, so there are two copies
     on it. This will not be seen in the actlog.
  
  ANR0327I Replication of node NODEA completed.
    Files current: 18,592. Files replicated: 3,091 of 3,091.
    Files updated: 3,090 of 3,090. Files deleted: 0 of 0.
    Amount replicated: 1,037 MB of 1,037 MB.
    Amount transferred: 1,037 MB.
    Elapsed time: 0 Day(s), 0 Hour(s), 2 Minute(s).
  ANR0986I Process 80 for Replicate Node running in the
    FOREGROUND processed 24,773 items for a total of
    1,087,704,064 bytes with a completion state of SUCCESS at
    12:41:13.
  
  
  2. In the second node replication, the server found the copies
     and deleted these 111 objects from the target replication
     server.
     Note: here is the bug, expected will be the result from
           point 4 (i.e. no deletion of files)
  
  ANR0327I Replication of node NODEA completed.
    Files current: 24,773. Files replicated: 0 of 0.
    Files updated: 0 of 0. Files deleted: 111 of 111.
    Amount replicated: 0 KB of 0 KB.
    Amount transferred: 0 KB.
    Elapsed time: 0 Day(s), 0 Hour(s), 1 Minute(s).
  ANR0987I Process 81 for Replicate Node running in the
    FOREGROUND processed 24,773 items with a completion state of
    SUCCESS at 12:44:16.
  
  
  3. In the third node replication, the server found there are no
     copies on the target replication server, so the 111 objects
     are sent again. This time these 111 objects just sent once.
  
  ANR0327I Replication of node NODEA completed.
    Files current: 24,662. Files replicated: 111 of 111.
    Files updated: 0 of 0. Files deleted: 0 of 0.
    Amount replicated: 152 MB of 152 MB.
    Amount transferred: 152 MB.
    Elapsed time: 0 Day(s), 0 Hour(s), 1 Minute(s).
  ANR0986I Process 82 for Replicate Node running in the
    FOREGROUND processed 24,773 items for a total of
    159,836,160 bytes with a completion state of SUCCESS at
    12:46:37.
  
  4. In the fourth node replication, all is is as expected:
  
  ANR0327I Replication of node NODEA completed.
    Files current: 24,773. Files replicated: 0 of 0.
    Files updated: 0 of 0. Files deleted: 0 of 0.
    Amount replicated: 0 KB of 0 KB.
    Amount transferred: 0 KB.
    Elapsed time: 0 Day(s), 0 Hour(s), 1 Minute(s).
  ANR0987I Process 83 for Replicate Node running in the
    FOREGROUND processed 24,773 items with a completion state of
    SUCCESS at 12:48:48.
  
  
  Tivoli Storage Manager Versions Affected:
  Tivoli Storage Manager Server version  6.3 on all platforms
  
  Initial Impact:
  low
  
  Additional Keywords:
  TSM, zz63, repl node, double, twice
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All Tivoli Storage Manager server users of   *
  *                 the REPLICATE NODE command.                  *
  ****************************************************************
  * PROBLEM DESCRIPTION: See ERROR DESCRIPTION.                  *
  ****************************************************************
  * RECOMMENDATION: Apply fixing level when available. This      *
  *                 problem is currently projected to be fixed   *
  *                 in level 6.3.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.
  

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

• R62A PSY

     UP

• R62H PSY

     UP

• R62L PSY

     UP

• R62S PSY

     UP

• R62W PSY

     UP

• R62Z PSY

     UP

• R63A PSY

     UP

• R63H PSY

     UP

• R63L PSY

     UP

• R63S PSY

     UP

• R63W PSY

     UP

• R63Z PSY

     UP