Container Recovery
Containers are like any other data source that needs to be protected. As your organization comes to rely on Docker containerization technology for critical IT functions, you need to ensure appropriate safeguards are in place to minimize disruptions to your business operations.
This section describes container backup and disaster recovery methods.
- When you configure IBM Sterling External Authentication Server to run inside a docker container ensure that you have mapped it to host directory or persistent volume. This ensures all configuration made to the container is intact and still available on the host machine when a container is destroyed/no longer available.
- IBM Sterling External Authentication Server configurations of a destroyed container such as, certificate validation profiles and Authentication definitions etc. can be used to recover your container. You can launch a new container using backup configuration.
- Configuration path for a new container must be mapped to persistent configurations.