You must create at least one vault before creating a backup plan or starting a backup job.
You can see Backup vault is created successfully
Now, we need to create backup plan.
Select backup frequency. The backup frequency determines how often a backup is created. Using the console, you can choose a frequency of every 12 hours, daily, weekly, or monthly. Choose a backup window. Backup window consists of the time that the backup window begins and the duration of the window in hours. Backup jobs are started within this window. I am configuring backup at 8 PM UTC start within 1 hour and completes within 4 hours.
Further, select lifecycle. The lifecycle defines when a backup is transitioned to cold storage and when it expires. I am configuring backup to move cold storage after 31 days and expire after 366 days.
Note: Currently cold storage isn’t supported for DynamoDB. Only Amazon EFS file system backups can be transitioned to cold storage. However, you should configure it anyway.
Note: Backups that are transitioned to cold storage must be stored in cold storage for a minimum of 90 days
Now assign the resource to backup plan. When you assign a resource to a backup plan, that resource is backed up automatically according to the backup plan.
After a resource has been backed up at least once, it is considered protected and is available to be restored using AWS Backup.
The Restore jobs pane appears. A message at the top of the page provides information about the restore job. You can see job status is running.After some time you can see status changes to completed
You can also monitor the all backup and restore jobs in central dashboard.
To see the restored table, go to the DynamoDB Console and click on Tables from the side menu.Choose ProductCatalogRestotred table. You can see the table is restored along with data.