The backup strategy must meet the following retention requirements:• Daily backups: must be kept for 6 days• Weekly backups: must be kept for 4 weeks:• Monthly backups: must be kept for 11 months• Yearly backups: must be kept for 7 yearsWhich backup strategy will meet these requirements with the LEAST administrative effort?
Use Amazon Data Lifecycle Manager to create an Amazon Elastic Block Store (Amazon EBS) snapshot policy. Create tags on each resource that needs to be backed up. Create multiple schedules according to the requirements within the policy. Set the appropriate frequency and retention period.
Use AWS Backup to create a new backup plan for each retention requirement with a backup frequency of daily, weekly, monthly, or yearly. Set the retention period to match the requirement. Create tags on each resource that needs to be backed up. Set up resource assignment by using the tags.
Create an AWS Lambda function. Program the Lambda function to use native tooling to take backups of file systems in Amazon EC2 and to make copies of databases in Amazon RDS. Create an Amazon EventBridge rule to invoke the Lambda function.
Use Amazon Data Lifecycle Manager to create an Amazon Elastic Block Store (Amazon EBS) snapshot policy. Create tags on each resource that needs to be backed up. Set up resource assignment by using the tags. Create multiple schedules according to the requirements within the policy. Set the appropriate frequency and retention period. In Amazon RDS, activate automated backups on the required DB instances.
Explanations:
Amazon Data Lifecycle Manager (DLM) is primarily designed for EBS snapshot management, not RDS. While it can meet the retention requirements for EBS snapshots, it doesn’t handle RDS backups, so it doesn’t fulfill the entire backup strategy.
AWS Backup can handle both EC2 (EBS volumes) and RDS backups with configurable retention periods for daily, weekly, monthly, and yearly backups. It also allows the use of tags for resource assignment, making it a fully automated solution for the backup strategy.
While an AWS Lambda function could technically automate backups, this would require extensive custom development and maintenance. It would not be as efficient as AWS Backup for managing both EC2 and RDS backups with the desired retention policies.
Amazon Data Lifecycle Manager only supports EBS snapshots and does not natively handle RDS backups. While automated backups can be activated for RDS, this option does not provide a fully integrated solution for both EC2 and RDS resources.
I reckon the answer is:
Use AWS Backup to create a new backup plan for each retention requirement with a backup frequency of daily, weekly, monthly, or yearly. Set the retention period to match the requirement. Create tags on each resource that needs to be backed up. Set up resource assignment by using the tags.