Cross-Account Cross-Region Recovery in N2WS

Overview

This article explains why the "Restore to Region" is greyed out when you are attempting a recovery from a backup in your DR account as shown below:

Understanding the “Restore to Region” Drop-Down Menu

Why is the “Restore to Region” drop-down menu greyed out?

The “Restore to Region” drop-down menu is greyed out when you are attempting to restore from your DR account backup because when cross-account DR has been configured for that policy you have chose to keep the snapshot in the original region as shown below:

Steps to Enable Cross-Region Recovery

If you want to restore to a different region, such as Paris, follow these steps:

1. Access the N2WS UI:
1. Navigate to the N2WS user interface.
2. Edit the Backup Policy:
1. Go to Policies.
2. Select the policy you want to modify (e.g., N2WS-Policy-Weekly).
3. Click on Edit.
3. Configure DR Settings:
1. In the policy settings, navigate to the DR tab.
2. On the DR screen, you will see the option to store the backup additionally to a different region. This needs to be done both in the original account and in the DR account.
3. Choose the desired region (e.g., Ireland).
   

1. Execute the Backup:
1. Save the changes and execute the backup of the policy.
2. Wait for the backup to complete.
2. Perform the Recovery:
1. Once the backup is complete, you can perform the recovery.
2. The “Restore to Region” drop-down menu should now show the newly selected region (e.g., Paris) as an option.
   

Additional Notes

1. Backup Completion: Ensure that the backup process is fully completed before attempting the recovery to see the new region in the drop-down menu.
2. Region Availability: Verify that the selected region is available and properly configured in both the original and DR accounts.

By following these steps, you can enable cross-region recovery and ensure that the “Restore to Region” drop-down menu includes your desired regions.

• Related Articles

• Cross-Account and Cross-Region DR of an encrypted RDS database may fail

  If cross-region and cross-account backup of an encrypted RDS database is successful, but fails in the cross-region cross-account DR copy, you may see the following error in the cpm logs: ERROR: start_copy_region(dr_rds.py:381) RDS DR copy_snapshot ...

• Cross region copy of RDS snapshots may fail with error: RDS DR copy snapshot failed (in Backup account). No matching KMS alias in target region

  Issue: The Following error may appear in the CPM Server logs: ERROR: start_copy_region(dr_rds.py:301) RDS DR copy snapshot failed (in Backup account). No matching KMS alias on target region (source EU (Frankfurt), target Asia Pacific (Singapore), RDS ...

• Error "Could not share private image ami-12345678 between accounts" may occur during cross-account instance recovery

  Error "Could not share private image ami-12345678 between accounts" may occur during cross-account instance recovery: Error - Could not share private image ami-12345678 between accounts Error - First step (launching instance) failed. Reason: Could ...

• Recovery of an encrypted volume may fail: "Not authorized to use key"

  Issue: Performing a cross account recovery of an encrypted volume, or of an instance containing an encrypted volume may not work if the target account cannot access the encryption key from the source account. Error may appear in the CPM Server log as ...

• RDS Cross Region DR fails with Exception: Cannot copy more than 5 snapshots across regions

  You may see the following errors in the CPM logs when cross region RDS DR copies fail to successfully copy to the DR region. ERROR:  cpm_copy_dbsnapshot(aws_rds_utils.py:217)  Exception: Cannot copy more than 5 snapshots across regions ...