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 configuring IBM Connect:Direct® for UNIX running inside a container ensure that you have mapped it over Storage Volume. This ensures all configuration made to the container is intact and still available on the Storage Volume when a container is no longer available.
  • IBM Connect:Direct for UNIX node configurations of a destroyed container such as, cfg, security, work, secure+ can be reused to start a new container. To start a new container with backup configurations:
    • Configuration paths for the new container must be mapped to persistent configurations.

    • In cd_param_file, passwords need to be mentioned again, as they would have been deleted after the previous deployment.
      Note: cd_param_file file content should match file content at fresh deployment.
    • Host name of new container must be same as the destroyed container

    • Invoke the docker run command using the same host name and configuration paths as described in the example below:
      docker run --cap-drop=ALL \
      		--cap-add=FOWNER \
      		--cap-add=SETUID \
      		--cap-add=SETGID \
      		--cap-add=DAC_OVERRIDE \
      		--cap-add=CHOWN \
      		--cap-add=IPC_OWNER \
      		--cap-add=IPC_LOCK \
                    --cap-add=SYS_CHROOT \
      		--name=<container-name> \
      		--hostname=<host-name of previous container> \
      		-v <host_dir>:/opt/cdfiles \
      		-v <host mapped path>/cfg:/opt/cdunix/ndm/cfg \
      		-v <host mapped path>/secure+:/opt/cdunix/ndm/secure+ \
      		-v <host mapped path>/security:/opt/cdunix/ndm/security \
      		-v <host mapped path>/work:/opt/cdunix/work \
      		-v <upload directory path on host>:<mount point inside container> \
      		-v <download directory path on host>:<mount point inside container> \
      		-p <host mapped client port: CD client port> \
      		-p <host mapped server port: CD server port> \
      		-it -d <image-id OR image-name:tag>