IT31291: AFTER A VSNAP REPLICA SERVER IS REPAIRED SPP REPLICATES ONLY NEWRECOVERY POINTS INSTEAD OF ALL RECOVERY POINTS

APAR status

• Closed as program error.

Error description

• If a vSnap server acting as a replication target is lost and
  then rebuilt using the new vSnap Repair functionality in IBM
  Spectrum Protect Plus 10.1.5, the expected behavior is that when
  the next a replication job runs, it will again replicate all
  recovery points that exist on the primary vSnap to the new
  target vSnap.
  
  Instead, the defective behavior is observed: SPP replicates only
  new recovery points that were not previously replicated.
  Effectively, some recovery points which were previously present
  on the old target vSnap are no longer seen on the repaired
  target vSnap.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect Plus level 10.1.5                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * pply fixing level when available. This problem is currently  *
  * projected to be fixed in IBM Spectrum Protect Plus level     *
  * 10.1.5.2137 and 10.1.6. Note that this is subject to change  *
  * at the discretion of IBM.                                    *
  ****************************************************************
  

Problem conclusion

• When a replica vSnap server is repaired, no recovery points are
  initially present on the new vSnap. The repair process simply
  repairs the volume relationships and resets the replication
  status on the primary vSnap. After the repair is complete, SPP
  is supposed to repopulate the target vSnap by replicating all
  recovery points present on the primary vSnap.
  
  Due to an incorrect check in the replication logic, SPP does not
  realize that the target vSnap server was repaired. SPP assumes
  that older recovery points that were previously replicated are
  still present on the target vSnap. As a result, SPP skips over
  those recovery points and only replicates new recovery points
  created by new backup jobs.
  
  The problem has been resolved by fixing the incorrect check in
  the SPP replication job. Now, SPP will correctly realize that
  the target vSnap has been repaired, and it will correctly
  repopulate it by re-replicating all recovery points, not just
  newly created ones.
  

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

  SP PLUS

• Fixed component ID

  5737SPLUS

Applicable component levels