Restoring DynamoDB Tables to a Different Cloud Account

You can restore the DynamoDB tables to a region on a different cloud account. You can restore the table with the same name or a different name to the destination region or to any supported region on the destination account.

Note

While restoring the DynamoDB tables, Commvault also restores the auto scaling policies and global tables.

Before You Begin

If the DynamoDB table is KMS encrypted, make sure that the user has necessary permissions to access the KMS key.

Procedure

  1. From the navigation pane, go to Protect > Databases.

    The database overview page appears.

  2. On the Instances tab, for the database instance that you want to back up, click the action button action_button, and then click Restore.

    The Backup content page appears.

  3. Select the backups to restore:

    • To use the latest backup, in the upper-right corner of the page, click Show latest backups > Show latest backup.

    • To use a backup from a specific date, in the upper-right corner of the page, click Show latest backup > Show backups as of a specific date, then select the date, and then click Ok.

    • To use a backup from a specific date range, in the upper-right corner of the page, click Show latest backup > Show backup for a date range, then select the date range, and then click Ok.

  4. Select the data that you want to restore:

    • To restore all of the data, select the check box next to Region.

    • To restore individual tables, click the Region, and then select the check box next to each table that you want to restore.

  5. Click Restore.

    The Restore options page appears.

  6. From the Destination cloud account list, select a cloud account to which you want to restore. By default, the same cloud account is selected.

  7. In the Number of streams box, type the number of streams to be used by the restore operation.

  8. If you want to restore tables that already exist on the destination, move the Overwrite destination tables toggle key to the right.

    If you do not enable this option and a table already exists on the destination, the restore jobs may fail.

  9. If you want to restore data with Local Secondary Index (LSI), move the Restore LSI toggle key to the right.

    Note

    LSI restore uses batch write to restore the data. The entire data is written using write units instead of import.

  10. To disable the restore with Global Secondary Index (GSI), move the Restore GSI toggle key to the left. By default, it is enabled.

  11. If you wan to restore the replicated tables, move the Restore Replica Tables toggle key to the right.

  12. If you want to restore to a different region on the selected cloud account, move the Overwrite region toggle key to the right.

  13. From the Region list, select the region you want to restore to.

  14. If you want to restore to a different table, under Destination table, enter the new table name.

  15. In the Staging bucket path box, enter the new path to stage the data temporarily. Alternatively, click Browse to locate the path.

  16. In the KMS Key ARN box, enter the KMS encryption key.

  17. Click Submit.

    The Confirm restore dialog box appears.

  18. Click Yes.

What to Do Next

If any of the following attributes were configured on the DynamoDB table that you restored, then after the restore operation, re-configure the attributes on the restored table.

  • Cloudwatch metrics and alarms

  • Tags associated with tables

  • TTL (time to live)

  • Resource-based policy

×

Loading...