IT46605: ARCHIVE JOB FAILS WITH "PARTNER ID DOES NOT MATCH CLOUD PARTNER ID" BECAUSE NEW ARCHIVE PARTNER IS CREATED

APAR status

• Closed as program error.

Error description

• IBM Spectrum Protect Plus archive job to Spectrum Protect server
  fails with below error:
  
  
  CTGGA0857,Partner update failed for <vsnap> Failed to create
  Vsnap cloud replication peer message: "Partner id does not match
  cloud partner id"  type: "Exception"
  CTGGA0851,Exception occurred during copy. Reason: Failed to
  create Vsnap cloud replication peer message: "Partner id does
  not match cloud partner id"  type: "Exception"
  
  
  New archive partner is created, so there are more than one
  archive partner associated with same bucket. The same may happen
  to copy job as well.
  

Local fix

• N/A
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect Plus level 10.1.16.2                    *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * IBM Spectrum Protect Plus archive job to Spectrum Protect    *
  * server fails with below error:                               *
  *                                                              *
  * CTGGA0857,Partner update failed for <vsnap> Failed to create *
  * Vsnap cloud replication peer message: "Partner id does not   *
  * match cloud partner id"  type: "Exception"                   *
  * CTGGA0851,Exception occurred during copy. Reason: Failed to  *
  * create Vsnap cloud replication peer message: "Partner id     *
  * does not match cloud partner id"  type: "Exception"          *
  *                                                              *
  * New archive partner is created, so there are more than one   *
  * archive partner associated with same bucket. The same may    *
  * happen to copy job as well.                                  *
  *                                                              *
  *                                                              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• The problem resulted from improper handling of certain S3 error
  codes coming from the SP server. This resulted in changing the
  partner id to a new one on the vSnap. The SPP backend was still
  using the old partner id, which no longer matched up with vSnap.
  This caused future backups to fail. A fix was made on the vSnap
  to properly handle the error codes and also allow for old ids to
  still function.
  

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