Backup and restore considerations for a two data center deployment

Points to consider when backing up and restoring a two data center disaster recovery (2DCDR) deployment on VMware.

The 2DCDR backup requirements are different for the Portal and Management subsystems.

Management subsystem 2DCDR backup requirements

  • Different remote backup locations must be specified for each data center.
  • Before you configure S3 backup settings you must first disable 2DCDR on both sites, and then re-enable 2DCDR after reconfiguring your backup settings.
    1. Disable 2DCDR for the management subsystems on both sites:
      apicup subsys set <management subsystem> multi-site-ha-enabled=false
      apicup subsys install <management subsystem>
    2. Configure your S3 backup settings.
    3. Enable 2DCDR for the management subsystems on both sites:
      apicup subsys set <management subsystem> multi-site-ha-enabled=true
      apicup subsys install <management subsystem>
    You do not need to do this for SFTP or local backups.
  • Both active and warm-standby Management subsystems run the scheduled backup job.
  • Restores must be run on the active data center.

Portal subsystem 2DCDR backup requirements

  • The backup settings for both the active and warm-standby portal must be identical.
  • Only the active data center portal takes backups. On failover, the backup job of the new warm-standby is disabled, and the backup job of the new active is enabled.
  • Portal restores are only done on the active data center.

Configuring backups for 2DCDR deployments

Keeping the different Portal and Management 2DCDR backup requirements in mind, the actual steps for configuring backups for both subsystems are the same as for a single API Connect deployment: