LI82783: RESTORE FAILS FOR S3 DISASTER RECOVERY

APAR status

• Closed as program error.

Error description

• Restore of Management subsystem fails during Disaster Recovery
  with S3. The Management subsystem goes into Warning state and
  restore cannot be completed
  

Local fix

• If management subsystem is already in a state where management
  CR shows Warning and upgrade CR does not go to completion,
  please delete the management CR or apiconnectCluste CR and it's
  resources
  
  Prepare for DR again and create necessary secrets
  As part of DR preparation, connect the DR cluster to a brand-new
  bucket instead of the old cluster's bucket
  Install the mgmt/apiconnect cluster subsystem
  At this point, this is treated as a brand new system with custom
  enc secret and app creds and backups going to a different bucket
  where upgrade CR is marked completed already.
  Change the S3 configurations to the old cluster bucket
  Wait for all the pods to go down and come up
  At this point mgmt CR will be still stuck in Warning State which
  is expected and there is no lock issue because upgrade is
  already marked complete
  Perform restore using one of the mgmtb backups
  

Problem summary

• v10.0.1.8 and v10.0.5.2 added a feature to track Postgres
  related problems and updating status which caused an issue when
  customers try to perform a disaster recovery restore using S3
  backups or moving from v2018 --> v10 using s3 mgmt backups where
  the Management subsystem goes into a Warning state and restore
  cannot be completed
  

Problem conclusion

• Fixed in versions v10.0.1.9 and v10.0.5.2
  

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

  API CONNECT ENT

• Fixed component ID

  5725Z2201

Applicable component levels