Configuration-Only Recovery

Cloud Rewind enhances recovery capabilities by enabling configuration-only recovery for AWS resources in cross-region and cross-account scenarios. Unlike traditional full-resource recovery, which includes both configuration and data resources, this feature will focus solely on restoring AWS infrastructure configurations, such as networking, load balancing, and infrastructure metadata, without recovering large-scale data resources like EC2 instance volumes and RDS databases.

Rebuilding any cloud configuration alone is time-consuming and error-prone, as configurations tend to drift from their initial state over time. This approach will allow customers to rapidly re-create their AWS environment’s network and infrastructure topology in another region or account while retaining the flexibility to restore application data separately via Commvault Cloud, Clumio, cloud native applications, or all, depending on the incident type. It is beneficial for disaster recovery, migration planning, and cost-optimized standby environments.

Features

These are the following features that Cloud Rewind provides to recover only AWS configuration data:

  • Cross-Region Recovery – Ability to restore/rebuild AWS configurations in a different AWS region from the source.

  • Cross-Account Recovery – Ability to restore/rebuild configurations in a separate AWS account, enabling Disaster Recovery (DR) setups or migration scenarios.

  • Configuration Dependency Mapping – Ensures dependencies between AWS resources, such as VPC, subnet, and route table, are recreated in the correct order.

  • Data Separation – Only the metadata and configuration of resources are restored, while excluding the application or user data.

  • Seamless Integration with Commvault Cloud – Customers can recover infrastructure from Cloud Rewind and then restore data resources from Commvault Cloud.

  • Post Recovery Configuration Update – Using this option, the customer can easily update the recovered VM resource reference to the load balancer target group and route table after successful recovery of VM resources from Commvault Cloud or any Cloud native restore.

Supported Configuration Resources for Recovery

Resource Description
VPC (Virtual Private Cloud) Network definitions, CIDR blocks, DNS settings
Subnets Availability Zone mappings, subnet configurations
Route Tables Routes, associations with subnets, and gateway links
Dedicated Hosts Host settings for compute resources
Load Balancers Classic and application/network load balancers, listener rules, target groups
Security Groups & Network ACLs Firewall and access configurations
Elastic IP Static and public IPv4 address used for inbound and outbound communication
Internet Gateways & NAT Gateways Connectivity setup without attached data services
Simple Notification Service (SNS)* Messaging between decoupled microservices or directly to users via SMS
Simple Queue Service (SQS) Sending and receiving messages between decoupled microservices

* Cross-account recovery is not supported for SNS.

Configuration Resources not Supported for Recovery

The following resources are not recovered as part of the configuration-only recovery, and can be restored separately from Commvault Cloud, if required.

  • EC2 Instances and their EBS Volumes.

  • RDS Instances along with data.

  • Lambda function configuration with function code

  • EFS file systems

  • DynamoDB

Configure the AWS Configuration Assembly

  1. Connect to AWS.

    Note

    To enable cross-account configuration recovery, create a Shared AWS Connection

  2. To create an AWS cloud assembly with configuration-only protection, while creating an AWS cloud assembly, select the protection strategy as Configuration only.

Recover the AWS Configuration Assembly

The recovery process for an AWS Config Assembly focuses on restoring the configurations of protected resources. Unlike a full disaster recovery, this process is similar to rebuilding the infrastructure; however, it does not recover data resources such as EC2 instances, EBS volumes, or RDS databases. Instead, it is limited to restoring the configuration state of the resources.

  1. From the navigation pane, go to Cloud Resilience.

  2. Click the AWS cloud assembly with the configuration-only protection policy.

  3. On the Timeline tab, click the backup associated to the point in time that you want to recover.

  4. On the top right corner of the screen, click Recover.

    On the Recover Resources page:

    • Enter the recovery name.

    • Select a recovery type:

      • Select Same Region for recovering to a VPC in the same region.

      • Select Cross Region for recovering to a VPC in a different region.

        Note

        To enable cross-account recovery, configure two active cloud connections according to the procedure in Shared AWS Connection.

    • Depending on the Same Region, Cross Region, or Cross Account selection, you must enter the VPC type, recovery region and other requirements.

  5. Click Recover.

  6. In the Recover Protection Timeline dialog box, type RECOVER, and then click RECOVER.

    Tip

    If you are testing recovery, then to delete the recovered configuration after a specific time, enable the Enable scheduled reset toggle and specify the time after which the recovered configuration must be deleted.

Update a Recovered Resource Configuration

You must update the recovered resource configuration after successfully recovering the VM resources via Commvault Cloud or any cloud-native application restore. This update reduces the following mandatory manual configuration update over the recovered configuration resources.

Before You Begin

  1. To update the recovered resource configuration, add the tags to the recovered VM resources.

    • Tag Key Name: commvault:sourceId

    • Tag Key Value: <source-vm-resource-id>

  2. Update the Recovered load balancers target groups target either with a VM ID or VM IP address.

    • This mechanism finds the recovered VMs using the listed tags and, based on the protected load balancers' configuration, updates the VM reference to the corresponding recovered load balancers' target groups.

    • This update ensures a successful configuration recovery with data recovery.

  3. Update the Route table VM routes (VM NIC ID) based on the protected route table configuration.

    • The recovery mechanism identifies the recovered VMs using the listed tags and collects their network interfaces.

    • It then compares the IP addresses of the recovered network interfaces with the private IP addresses of the protected network interfaces.

    • Based on this comparison, the recovered network interfaces are updated in the corresponding route table configuration.

    • This ensures accurate restores of the instance routing configurations.

Procedure

  1. From the navigation pane, go to Cloud Resilience.

  2. Click the AWS cloud assembly with the configuration-only protection policy.

  3. On the Repository tab, click the Recoveries tab.

  4. In the row of the configuration restore that you want to update, click Action > Update Recovery Config.

  5. On the Update Recovery Configuration dialog box, click Update.

×

Loading...