Restoring the management subsystem on OpenShift and Cloud Pak for Integration
You can restore your Management subsystem in your OpenShift and Cloud Pak for Integration environments.
Before you begin
About this task
To trigger a restore, you will create a ManagementRestore
custom resource. When
the ibm-apiconnect
operator detects the new CR, it starts the restore process.
- Ensure that the backup method that you used is complete before you attempt a restore. The backup data that is stored in the remote server is used for restoring the Management subsystem data back to a previous state. Ensure that these backups are on your remote server before you attempt a restore, and that the backup ID in the selected backup exists in remote storage.
- Restoring a backup restores the registration credentials (client_ID, client_secret) that were in use at the time that the selected backup was created. For information on the registration credentials, see Changing the registration client_id and client_secret for applications.
- If you have to perform a restore, you must complete the restoration of the Management Service first, and then immediately restore the Developer Portal. The backups of the Management and Portal must be taken at the same time to ensure that the Portal sites are consistent with Management database.
Note: There is a known issue where sometimes a restore from the Management subsystem's SFTP backup
succeeds but the data is not restored. If this happens, run the restore again.