Which backup architecture will meet these requirements?
Backup RDS using automated daily DB backups. Backup the EC2 instances using AMIs and supplement with file-level backup to S3 using traditional enterprise backup software to provide file level restore.
Backup RDS using a Multi-AZ Deployment. Backup the EC2 instances using Amis, and supplement by copying file system data to S3 to provide file level restore.
Backup RDS using automated daily DB backups. Backup the EC2 instances using EBS snapshots and supplement with file-level backups to Amazon Glacier using traditional enterprise backup software to provide file level restore.
Backup RDS database to S3 using Oracle RMAN. Backup the EC2 instances using Amis, and supplement with EBS snapshots for individual volume restore.
Explanations:
This option meets all requirements by leveraging RDS automated backups for the database, AMIs for whole EC2 instance restoration, and file-level backup to S3 for granular recovery. Automated backups of RDS ensure point-in-time recovery, and file-level backups allow individual file restores within the required 2-hour recovery time.
While a Multi-AZ RDS deployment provides high availability, it is not a backup solution and does not allow for point-in-time recovery. Copying file system data to S3 can help with file-level restores, but it lacks a formal backup approach for individual files and database restoration in a timely manner.
Glacier is not suitable for rapid recovery because it has longer retrieval times, which conflicts with the 2-hour recovery time requirement. Additionally, while EBS snapshots are suitable for volume-level backups, they do not support individual file restores directly.
Oracle RMAN backups to S3 would require additional configuration and management, and RMAN does not integrate seamlessly with RDS since it is a managed service. This approach does not provide a reliable solution for instance-level, volume-level, or file-level restoration within the required time frame.