IT32102: VSNAP REPLICATION FAILS WITH ERROR "TARGET SNAPSHOT NOT FOUND"

APAR status

• Closed as program error.

Error description

• vSnap replication fails with error "Target snapshot not found".
  The replication job log shows:
  
  ERROR,1579164716293,<date,time,timezone>,2,,Unable to
  find target snapshot <snapshot-name> on volume: <volume-name>
  ERROR,1579164716419,<date,time,timezone>,2,,null
  e=...xsb.commons.XSBException: Target snapshot not found
  
  vSnap log shows the error "Cannot find DB entry for snapshot
  named <snapshot-name>". But snapshot and relationship do exist
  on vSnap side. vSnap fails to query out the the snapshot because
  it truncates the complete snapshot name due to special
  character, like #, included in the SLA name.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect Plus levels 10.1.0, 10.1.1, 10.1.2,     *
  * 10.1.3, 10.1.4, 10.1.5.                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in IBM Spectrum Protect Plus levels    *
  * 10.1.5.2199 and 10.1.6. Note that this is subject to change  *
  * at the discretion of IBM.                                    *
  ****************************************************************
  

Problem conclusion

• SPP uses portions of the SLA name in the names of volumes and
  snapshots created on vSnap. When the SLA name contains a pound
  symbol ('#'), certain API calls from SPP to vSnap failed because
  SPP did not correctly encode the pound symbol which occurred as
  part of a URL parameter. This caused failures during
  replication.
  
  The problem has been resolved by correctly encoding parameters
  in API calls made from SPP to vSnap.
  

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