Which backup architecture will meet these requirements?

Your customer wishes to deploy an enterprise application to AWS which will consist of several web servers,
several application servers and a small (50GB) Oracle database information is stored, both in the database and
the file systems of the various servers. The backup system must support database recovery whole server and
whole disk restores, and individual file restores with a recovery time of no more than two hours. They have
chosen to use RDS Oracle as the database
Which backup architecture will meet these requirements?

Your customer wishes to deploy an enterprise application to AWS which will consist of several web servers,
several application servers and a small (50GB) Oracle database information is stored, both in the database and
the file systems of the various servers. The backup system must support database recovery whole server and
whole disk restores, and individual file restores with a recovery time of no more than two hours. They have
chosen to use RDS Oracle as the database
Which backup architecture will meet these requirements?

A.
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

B.
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.

C.
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

D.
Backup RDS database to S3 using Oracle RMAN Backup the EC2 instances using Amis, and supplement with
EBS snapshots for individual volume restore.

Explanation:

http://www.boyter.org/wp-content/uploads/2014/12/Backup-And-Recovery-Approaches-Using-Aws.pdf



Leave a Reply 44

Your email address will not be published. Required fields are marked *


Sandy

Sandy

Answer is B for sure.

C is incorrect as Glacier is used for backup which will take atleast 4 hours for restoration.
D doesn’t make sense
Eliminate A as it is trying to use enterprise backup software

a

a

copy 50G file to S3?

Frank

Frank

Hi,

I would choose: A

I think answer C is NOT correct, since it will not match the restore of individual files within two (2) hours. Glacier typically complete a restore in 3-5 hours.

LaVa

LaVa

Wrong answer, pulling data off glacier requires more than 2h.

Mandu

Mandu

Answer is A. The customer wants recovery withing 2 hours. Glacier takes 3-5 hours to retrieve data.

LSK

LSK

Why not D ? Oracle RMAN is a backup tool for Oracle.
Let us discuss this .

Venku

Venku

yes you were right LSK. The answer is D. EBS volumes can be used as file system by using this command

mkfs -t ext4 /dev/xvdf

Senator

Senator

Why i think A is the right answer and not D is because, D does not have “automated” backup which option ‘A” has

lol

lol

and why use an oracle product..? oracle is only mentioned because they currently use an oracle product.. irrelevant for RDS

lol

lol

Sry… misread RDS for Aurora.. ignore

Tony Kuo

Tony Kuo

A
You don’t need RMAN backup when using RDS.

Harsh Wardhan

Harsh Wardhan

Oracle does not support Multi AZ deployment.So it has to be A.

Felipe

Felipe

yes it does support Multi AZ! read the documentation

“Amazon RDS for Oracle makes it easy to use replication to enhance availability and reliability for production workloads. Using the Multi-AZ deployment ”
https://aws.amazon.com/rds/oracle/

The only ones I see that would be able to cover the 2 hours
are :

B or D
but I not sure …

Umesh

Umesh

I would choose A.

Venku

Venku

What traditional enterprise backup they are referring to while supplementing the data present in the File system. We know the best way to back up the file system storage volumes is by the EBS Snapshot. There is no traditional way backup mechanism in AWS apart from EBS Snapshot. I hope it makes sense right now.

A- They don’t discuss about the EBS Snapshots to back up the data on file system.

D- It does mention about the Snapshots. Amazon also suggest you to use RMAN

Reference: https://forums.aws.amazon.com/thread.jspa?threadID=156423

Srinivas

Srinivas

Ans . A

Amazon snapshot will not provide file level restoration.So you have to Enterprise backup tool for such scenarios.

James Mortenson

James Mortenson

Since they have mentioned max 2 hours recovery for everything then Glacier is out of questions.
C is the Wrong answer.

B Sounds more reasonable.

tom

tom

‘B’ – we don’t have to opt for RMAN/3rd party backup tools when RDS provides the service along with Multi-AZ’s

JK

JK

C does not meet the RTO of 2 hours because of Glacier.
D does not meet individual file restore requirements.

A is more suitable than B.

If you read the following whitepaper:
https://d0.awsstatic.com/whitepapers/Backup_and_Recovery_Approaches_Using_AWS.pdf

Where ever it mentions your existing backup software not natively supporting S3, then they recommend Storage Gateway as the bridge. They do not make any mention of file copies to S3.

Excerpt:
“If your existing backup software does not natively support cloud storage for
backup or archive, you can use a storage gateway device, such as a bridge,
between the backup software and Amazon S3 or Amazon Glacier.”

fun4two

fun4two

jk you are right answer is A

Explanation:
Point-In-Time Recovery
In addition to the daily automated backup, Amazon RDS archives database change logs. This enables you to recover your database to any point in time during the backup retention period, up to the last five minutes of database usage.
Amazon RDS stores multiple copies of your data, but for Single-AZ DB instances these copies are stored in a single availability zone. If for any reason a Single-AZ DB instance becomes unusable, you can use point-in-time recovery to launch a new DB instance with the latest restorable data. For more information on working with point-in-time recovery, go to Restoring a DB Instance to a Specified Time.
Note
Multi-AZ deployments store copies of your data in different Availability Zones for greater levels of data durability. For more information on Multi-AZ deployments, see High Availability (Multi-AZ).

muthu

muthu

Answer is B . No need to include any traditional backup software . All the requirements can accomplish with aws service..

Manuil.com

Manuil.com

As per this thread https://forums.aws.amazon.com/thread.jspa?threadID=156423, AWS doesn’t use RMAN backup, so D is grayed out
C is grayed out because of Glacier, can’t restore in two hours time
with option A requirement can be achievable however depended on third party backup software

so I would go with B, which is recommend by AWS, that RDS instance must be backedup using availability zone

DakkuDaddy

DakkuDaddy

Agree with JK and fun4two

The correct answer is
A.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 & Recovery
Automated Backups – Turned on by default, the automated backup feature of Amazon RDS enables point-in-time recovery for your DB Instance. Amazon RDS will backup your database and transaction logs and store both for a user-specified retention period. This allows you to restore your DB Instance to any second during your retention period, up to the last five minutes. Your automatic backup retention period can be configured to up to thirty five days.

DB Snapshots – DB Snapshots are user-initiated backups of your DB Instance. These full database backups will be stored by Amazon RDS until you explicitly delete them. You can create a new DB Instance from a DB Snapshot whenever you desire.

https://aws.amazon.com/rds/oracle/

Kishore M V S

Kishore M V S

multiAz deployment is supported by oracle,So D is correct

Aryan Bansel

Aryan Bansel

a..its saying backup.. Multi-AZ used in Disaster recovery ..

laughsmile

laughsmile

B

Don’t use RMAN for RDS backups, but db snapshots.
For complete recoverability in RDS, you would need to use Multi-AZ, which maintains a synchronous replica of your main instance.
You can also use Oracle in EC2, In that case you can run RMAN backing up to S3.(Only in the case, you can choose A)
Source:
https://forums.aws.amazon.com/thread.jspa?threadID=156423

vladam

vladam

B is not specific enough regarding how would you copy files to S3.

A is the right answer.

You need to use enterprise backup software to provide file level restore. See
https://d0.awsstatic.com/whitepapers/Backup_and_Recovery_Approaches_Using_AWS.pdf

Page 18:
If your existing backup software does not natively support the AWS cloud, you can use AWS storage gateway products. AWS Storage Gateway is a virtual appliance that provides seamless and secure integration between your data center and the AWS storage infrastructure.

Dat

Dat

If “B is not specific enough regarding how would you copy files to S3” , then A does not mention which software should we use. Your argument could be applied for the both cases.

By the way, A mentioned about enterprise backup (sounds like on-premise system). But the whole question is about “…customer wishes to deploy an enterprise application to AWS…” which mean we ought to use pre-existence solution provided by Amazon.

B should be the correct answer based on the strategy solely. Because , if we following strategies provided by then we could implement by using various different technique. Moreover, B satisfies all the requirement the question provided.

Paul

Paul

Its A because you would use traditional file level backup solution to back up data to S3 — B sounds right as well when you first read but it says ‘file system data’ so thats why i discounted it …

cncluo

cncluo

It cannot be B, b/c Multi-AZ isn’t a backup solution.

For example, if data is accidentally deleted, the deletion is propagated to standby nodes fast, and you cannot roll back to certain point in time in past. So only periodic backup can address this scenario.

Ryan

Ryan

A is the correct answer. B is just there to confuse you.

Gabriel Wu

Gabriel Wu

Answer is A
B multi-AZ deployment it’s for DR failover, disaster recovery, i don’t think this is recommended as way as backup
C: Glacier, this is too slow
D: S3 is object based.

Gabriel Wu

Gabriel Wu

I prefer B
It’s mentioned recovery time, restore files ,database, this is definitely for disaster recovery.

John Araujo

John Araujo

Come on Grabriel you need to decide if you want A or B. Otherwise it confuses honest people researching and trying to find a good answer. I would go with B as well.

Amit

Amit

A is most plausible answer here is why

B: MultiAZ deployement is not a backup mechanism its a HA mechanism
C: GLacier kills this option as question ask for restoration time of less than 2 hours
D: File level recovery is not possible with AMI and Snapshots

A: Does not need AMI backups however it may be added to juust add spcie to the question

Amit

Amit

Answer is A.

Linh

Linh

C

Linh

Linh

Sorry, Answer is A.

You need to use enterprise backup software to provide file level restore. See:
https://d0.awsstatic.com/whitepapers/Backup_and_Recovery_Approaches_Using_AWS.pdf
Page 18:
If your existing backup software does not natively support the AWS cloud, you can use AWS storage gateway products.
AWS Storage Gateway is a virtual appliance that provides seamless and secure integration between your data center
and the AWS storage infrastructure.

lyannabear

lyannabear

Answer is A

Most of the answers at the top are wrong. I’ve gone through the trouble of correcting all 400 of them for my own study purposes. If you would like a digital copy of this dump please send $40 to paypal.me/lyannabear