Recovering the management subsystem from S3 backups
You can recover the management subsystem from S3 backups after a disaster event.
Before you begin
Important: Successful disaster recovery depends on recovery of both the Management subsystem
and the Developer Portal
subsystem. You must complete preparation steps for both subsystems in order to achieve disaster
recovery. If you have to perform a restore, you must complete the restoration of the Management
Service first, and then immediately restore the Developer Portal. Therefore, 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.
About this task
To recover from a disaster event, you must create a new IBM API Connect® installation with a running IBM API Connect Operator.
Note: Limitation for backups created on Version 10.0.2
- If restoring a Version 10.0.2 backup onto a new Version 10.0.2 deployment, performing a restore may not work if the subsystem CR name exceeds 15 characters. This limitation applies only to restoring onto Version 10.0.2.
- Restoration is supported for Version 10.0.2 backups onto a Version 10.0.3.0 or later deployment
when subsystem name exceeds 15 characters, as long as the correct
spec.originalUID
is specified upon restore. See Step 3.f.