Preparing your environment for disaster recovery

Prepare your environment for disaster recovery. When the primary environment cannot provide service, the secondary environment provides service. For more information about how to back up your environment, see Backing up your environments.

Procedure

  1. Set up your environment to support disaster recovery:
    1. Ensure that your primary environment is deployed successfully, by ensuring that the necessary operators and components are installed correctly. For more information about installed components, see Capabilities for production deployments.
    2. If you are using LDAP, configure the LDAP connection and configure the LDAP user to Zen.
    3. If you are using Db2, set up the IBM Db2® HADR primary node and secondary node across the primary environment and the secondary environment.
    4. Back up the custom resource (CR) definition that is used to deploy the primary environment.
    5. Back up the secure definition that is used to protect the configuration data in the primary environment.
    6. Back up the PV and persistent volume claim (PVC) definitions.
    7. Back up the content in your database. Remember to back up your database regularly.
  2. Prepare the secondary environment by following the installation procedure so that the secondary environment can be used to install the operator and other components.
  3. Apply the backup secure definition from the primary environment in the secondary environment.
  4. Use the backup PV and PVC definitions to create the PVs and PVCs that access the shared storage.
  5. Prepare the CR definition for the secondary environment. The following hostnames might be different between the primary environment and secondary environment. If they are, change the hostname in CR definition to the hostname that is available in the secondary environment.
      • Router hostname.
      • NFS server hostname in PV definition.
      • Redis server hostname.
    2. The folders and files were created with a specified user identifier (UID) in the primary environment. Update the shared_configuration.sc_run_as_user value in the CR definition to use the same UID as the primary environment. You must complete this step so that the secondary environment can reuse the folders and files.
  6. Start the secondary environment:
    1. Use the Db2 secondary nodes to takeover the Db2 workload from the primary nodes.
    2. Deploy the secondary environment with the modified custom resource definition.
    Note: Do not start the primary environment and secondary environment at the same time.
  7. Complete disaster recovery preparation for the following components that you configured in your environment.