--- title: Create a Disaster Recovery Plan --- # Create a Disaster Recovery Plan ## 1. Requirements and Compatibility ### Supported VM Series DRaaS is available for the following VM series: | Series | Type | | ------ | ----------------------- | | C3 | General-purpose compute | | M3 | Memory-optimized | | E1 | Economy | Other VM series are not currently supported. ### Supported Regions DRaaS supports cross-region replication between E2E Networks data centers as follows: | Source Region | Available Target Regions | | ------------- | ------------------------ | | Delhi | Chennai | | Chennai | Delhi | Source and target must always be different regions. Same-region DR is not supported. ### Pre-conditions for Creating a DR Plan Your source VM must meet all of the following before you can create a DR plan: | Requirement | Details | | ------------------------------ | --------------------------------------------------------------------------- | | VM is Running | Source VM must be in active running state. You cannot protect a stopped VM. | | No encryption on disks | VMs with encrypted disks are not supported. | | No auto-terminate enabled | If Reserved Instance auto-terminate is enabled, disable it first. | | No scheduled power-off actions | Remove scheduled on/off automation before plan creation. | | Block storage plans available | Attached block storage plans must be available in target region. | | Sufficient infra credits | Account balance must be enough to cover DR plan cost. | ## 2. Getting Started Checklist Before creating a plan, gather: - Source VM you want to protect - Target region (different from source) - Desired RPO (1 to 240 hours) - Desired retention period (1 to 365 days, default 7 days) - Optional list of block storage volumes to include ## 3. Steps to Create a DR Plan 1. From the sidebar menu, navigate to Disaster Recovery. 2. Click Create Disaster Recovery. 3. On the DR creation page, select the node to protect. 4. Select volumes to include in DR (optional, recommended). 5. Choose the target region. 6. Configure RPO (1 to 240 hours). 7. Configure Recovery Point Retention (1 to 365 days). 8. Click Create Disaster Recovery and confirm in the popup. ## 4. Create a DR Plan from a Node You can also create a DR plan from the Nodes page: 1. Go to Nodes. 2. Select the node to protect. 3. Click Enable DR from the actions menu. 4. You are redirected to DR creation page. 5. Complete plan creation. ## 5. Target and Source Resource Nodes ### Target Resource - All actions on target node are restricted, except security group attach/detach. - Security groups from source are automatically attached to target. - SSH keys from source are automatically attached to target. - Source start script is automatically applied to target. ### Source Resource - Source cannot be powered off unless DR plan is in Stopped state. - Reinstallation is not allowed while DR plan is active. - Moving resource to another project is not permitted while DR is active. - Source resource upgrade and deletion are restricted during DR. - You can start Recovery Mode only after stopping DR plan. - Volumes can be attached to source once DR plan is stopped. ## 6. What Happens After Creation After creation, plan enters Creating state. DRaaS then: 1. Provisions standby VM at target region (same OS and SKU) 2. Creates replica volumes at target and attaches them 3. Clones security groups to target region 4. Powers off target VM (standby mode) 5. Triggers first data replication immediately 6. Sets plan to Active state This usually completes within a few minutes. A confirmation email is sent once plan is fully active and first recovery point is available. ## 7. Understanding Plan Status | Status | Meaning | What You Can Do | | ----------------- | --------------------------------------------------------------------- | ----------------------------------------------------------------------------- | | Creating | DRaaS is setting up standby VM and first replication. | Wait and recheck. | | Active | Replication runs on schedule and recovery points are generated. | Stop, delete, drill, recover, create manual recovery points, update settings. | | Stopping | Replication is being paused. | Wait. | | Stopped | Replication paused; no new recovery points. Existing points remain. | Start (resume) or delete. | | Starting | Replication is being resumed. | Wait. | | Starting DR Drill | DRaaS is restoring recovery points for drill prep. | Wait. | | In Drill | Target VM is powered on for testing. | Stop drill when done. | | Stopping DR Drill | Drill ending; target powering off; replication resumes shortly. | Wait. | | Recovering | Recovery is in progress and target VM is being restored/powered on. | Wait. | | Recovered | Recovery complete; target VM running in target region; DR plan ended. | Operate from target region. | | Deleting | Plan is being removed; target VM and snapshots are being cleaned up. | Wait. | | Deleted | Plan fully removed. | Create new plan if needed. | | Failed | Creation or operation encountered unrecoverable error. | Contact support or create new plan. | ### Action Blocking During Data Shipment While replication shipment is running, these actions are blocked: - Stop plan - Delete plan - Start DR drill - Perform recovery - Create manual recovery point System message: > "Not allowed when data shipment is going on. Please wait." Wait for shipment completion, then retry. ## 8. Important Notes :::info - Only running and available nodes can be included in a new DR plan. - Nodes already part of an active DR plan cannot be reused in another plan. - DR currently supports only C3, M3, and E1 non-encrypted nodes and non-encrypted volumes. - DR creation is currently supported only between Delhi and Chennai regions. ::: ---