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.
   Note
   
   

   • For Cold VM DR or pilot light VM DR topologies, referred to as moving instances compute in Full Stack DR, add the boot volume and all block volumes attached to compute instances in the primary region to the replicated volume group.
   • For active-passive DR topology, referred to as non-moving instances in Full Stack DR, add all the block volumes attached to compute instances in the primary region to the replicated volume group. Generally, boot volumes do not need to be replicated. However, if you store application data on the boot volume (root partition), you may require other mechanisms, such as rsync or robocopy, to keep the primary and standby compute instance boot volume file systems in sync.