Preparing Block Storage for Full Stack Disaster Recovery

If the disaster recovery topology contains any block storage volumes attached to compute instances, or any stand-alone block storage volumes, use the steps in this topic to prepare the block storage volumes for Full Stack DR.

  1. Create a block storage volume group in the same Availability Domain (AD) as the compute instance.
  2. Add the block storage elements (boot volumes or block volumes) to the volume group you created in Step 1.
  3. Identify the standby region (recovery region) in which you want to recover the block storage. This region can be the same as the primary region. However, Oracle recommends that you generally use cross-region DR configurations to protect against region-wide outages.
  4. Configure volume group replication to the standby region for the volume group you created in Step 1. Alternatively, configure backups for the volume group to the standby region.

    • Setting up block storage replication or backups is only required for DR topologies where compute instances move across regions. For an active or passive DR topology, you do not need to configure block storage replications or backups. However, you may require other mechanisms, such as rsync, to keep the primary and standby compute instance file systems in sync.
    • You do not need to configure both replication and backups for Full Stack DR, only one of them is required. Oracle recommends you to use replication over backups because replication provides a much better recovery point (the data in backups can be up to a day old). If both, replication and backups are configured, Full Stack DR chooses replicas over backups for restoring block storage.