Backup Approach for On-Premises RDS Databases
Question
You are a development lead, and your team has maintained an emailing service for the company's major applications.
The emailing service is deployed on-premises with several RDS on VMware databases to store users' metadata.
There is no plan to migrate the on-premises RDS databases to AWS RDS.
However, you need an appropriate approach to backup the databases to AWS so that the database can be quickly restored.
Which steps should you take to fulfill this requirement? (Select THREE)
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D. E.Correct Answer - A, D, E.
When using Amazon RDS on VMware, it also makes it very easy to take advantage of the AWS scale for disaster recovery, cloud backups, and read replica scaling.
The same RDS console, APIs, or CLI can be used to manage RDS databases running on VMware or RDS databases running on AWS.
Refer to https://aws.amazon.com/rds/vmware/ on how to do the hybrid cloud backups and scaling.
Option A is CORRECT: Because the Amazon RDS on VMware backup/restore system enables point-in-time restore for all supported engines and allows you to specify an automated backup retention period of up to 35 days.
Option B is incorrect: Because for Amazon RDS on VMware, you can only create a read replica in the same region as the source DB instance.
Details please check https://aws.amazon.com/rds/vmware/faqs/.
Option C is incorrect: Because AWS Glacier is unsuitable for a quick restore.
Option D is CORRECT: Because the read replica can be created in the same region.
RDS on VMware is available in AWS US East (Northern Virginia) Region.
References can be found in https://aws.amazon.com/rds/vmware/faqs/
Please note that a Read Replica can be promoted if the database needs to be restored in AWS RDS.
Option E is CORRECT: Because this method can create a manual snapshot in AWS, if needed.
To fulfill the requirement of backing up the on-premises RDS databases to AWS, there are a few steps that should be taken, as follows:
Specify an automated backup every day to store the snapshot to the S3 bucket so that the backup has high availability and durability. This will ensure that the backups are taken regularly and stored in a highly available and durable location such as S3, which provides a cost-effective and secure way to store data.
Configure a read-replica in a different region from the one that the RDS on VMware instance connects to. This will provide an additional layer of redundancy and protection against disaster scenarios, such as if the primary database becomes unavailable due to a regional outage. By having a read replica in a different region, data can still be accessed and the application can continue to function without significant disruption.
Create a automated backup schedule in RDS and save the daily snapshots to AWS Glacier for long-term backup. This will ensure that long-term backups are taken and stored in a cost-effective and secure manner using AWS Glacier, which is designed for archiving data. It is important to note that Glacier is designed for long-term storage and may have slower retrieval times than other storage options.
It is important to also note that creating a read-replica in the same region for disaster recovery as long as the region supports RDS (Option D) can also be a valid approach to ensure that the data is still available if the primary database becomes unavailable. However, this may not provide the same level of protection as having a read-replica in a different region.
Additionally, creating a manual backup of the on-premise database if needed (Option E) is always a good practice to ensure that a backup can be taken at any point in time if required. However, relying solely on manual backups may not be sufficient for ensuring regular and consistent backups.
