Recovering Cloud Assembly to the Same Region

Create a new VPC

Recovery creates a new VPC in the same region with same IP range (CIDR Block) as source VPC and recovers the selected resources and its dependencies to the new VPC.

The recovered EC2 instances will have the same private IPs as the source EC2 instances. The Subnets will be created with same IP ranges in the same Availability zones as the source.

You also have an option to change the availability zone under the "Advance options".

Example: If the source VPC is say "Prod-VPC" 10.0.1.0/24 , the new VPC created during recovery in the same region will also have the same CIDR block 10.0.1.0/24 and the EC2 instances will have the same private IPs as the source EC2 instances.

Recover the resources in the Same VPC as the source VPC in the same region.

Network Recovery Options

If the Network recovery options is enabled, you have the option to map the source and destination subnets.

The subnets will be automatically mapped if there is a tag attached to the destination subnet. Or it can be manually mapped.

Options

• As the Subnets already exist in the same VPC, the recovery will skip creating any subnet
• If there are any changes in the security group rules, the rules that was previously configured at the point of protection will be applied during the recovery

Conditions

• If the source EC2 instance already exists, Appranix will highlight saying that there is a conflicting resource and will provision the EC2 instance with a different IP address
• If you want the EC2 instance to be created with the same IP address as the source, the source EC2 instance should be removed completely (terminated) before triggering a recovery
• If the EC2 instance is associated with the load balancer, the recovered instances in the same Region, same VPC is not attached to the load balancer as a good practice. The addition of recovered instance to the load balancer is manual

Example: If the source VPC is say "Prod-VPC" with 10.0.1.0/24 , the EC2 instances having the same IP as source depends on if the source VM exist or not at the time of recovery.

Use existing VPC

Recover the resources in a Pre-Created/ Existing VPC with either the same configuration as the source VPC (Same IP Ranges and CIDR Blocks) or similar configuration as source (but with different IP Ranges and CIDR Blocks) in the same region.

Prerequisites

• The following resources are expected to be pre-created in a pre-existing VPC
• VPC Network
• Subnet
• Route Table
• Internet Gateway

• DHCP Option

• The source Security Group rules should be modified to have the pre-created subnet IP ranges allowed, so that the same are reflected in the recovery.

Source and destination VPC CIDR should have same capacity and same number of subnets (to support one to one mapping). Example: 172.31.0.0/16 (Source) and 10.31.0.0/16 (Destination) is acceptable whereas 172.31.0.0/16 (Source) and 10.31.0.0/20 (Destination) is not acceptable.

• It is expected to have the subnets pre-created with equivalent configuration as source in the DR/Pre-Existing VPC.
  Example, If the subnet in the source VPC are of ranges 10.0.1.0/24 and 10.0.2.0/24.

a) If the pre-existing VPC is of the same IP range as the source VPC.
-- Same subnets (IP Ranges) are expected to be Pre-created in the Pre-existing VPC
-- 10.0.1.0/24 and 10.0.2.0/24

b) If the pre-existing VPC is of different IP range than that of the source VPC.
-- Equivalent subnets (Number of available IPs) are expected to be pre-created in the pre-existing VPC
-- 172.16.1.0/24 and 172.16.2.0/24

• The source and destination subnets can be mapped for the recovery.
  -- You can use tags to auto map the destination subnet to the source subnets.
  -- If no tags are added, you have to manually map the subnets.
  Example tag format: Recovery resource tag name - ax-recovery-subnet-id & value - subnet-0297f00011dba2xx

• Routes have to be manually updated.
  For example, Nat Gateway which is created during the recovery on a pre-existing VPC has to be manually updated in the route table.