IT32506: VSNAP REPLICATION REPORTS ERROR "FAILED TO GET SNAPSHOT INVALID CHARACTER" AFTER APPLYING 10.1.5 EFIX3 (10.1.5.2199)

APAR status

• Closed as program error.

Error description

• vSnap replication reports error "Failed to get Snapshot Invalid
  character" if SLA name contains special characters like
  space after applying 10.1.5 efix3 (10.1.5.2199). The job log
  displays following message:
  
  ERROR,<id>,<timestap>,2,,null
  e=...serviceprovider.common.storage.exception.StorageSnapshotGet
  Exception: Failed to get Snapshot Invalid character '+' for
  QUERY_PARAM in "<snapshot_name>_SPP+Catalog+Backup"
  ERROR,<id>,<timestamp>,2,,Skipping remaining snapshots for
  volume <ip_address>:<snapshot_name> due to unrecoverable error
  for Vsnap session <session_id>
  
  Even with the error, the snapshot may be replicated to target
  vSnap properly and replication job completed with status
  COMPLETED.
  

Local fix

• N/A
  

Problem summary

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

Problem conclusion

• As part of the changes made to address APAR IT32102, changes
  were made to encode special characters present in API query
  parameters sent from SPP to vSnap. The new encoding logic
  required additional special handling for space characters which
  was missed. As a result, a regression was introduced that caused
  API failures where there were spaces in the API query parameter.
  
  The problem has been resolved by updating the encoding logic to
  correctly handle space characters (in addition to other special
  characters) in SLA names.
  
  The fix takes effect for replication jobs that run after
  applying the update. For replication jobs that previously failed
  due to this problem, orphaned snapshots may exist on vSnap
  because they were successfully replicated but not cataloged by
  SPP. These orphaned snapshots may require manual deletion using
  the "vsnap snapshot delete" command.
  

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