You have a server with a 5O0GB Amazon EBS data volume. The volume is 80% full. You need to back up the
volume at regular intervals and be able to re-create the volume in a new Availability Zone in the shortest time
possible. All applications using the volume can be paused for a period of a few minutes with no discernible
user impact.
Which of the following backup methods will best fulfill your requirements?
A.
Take periodic snapshots of the EBS volume
B.
Use a third party Incremental backup application to back up to Amazon Glacier
C.
Periodically back up all data to a single compressed archive and archive to Amazon S3 using a parallelized
multi-part upload
D.
Create another EBS volume in the second Availability Zone attach it to the Amazon EC2 instance, and use a
disk manager to mirror me two disks
Explanation:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-creating-snapshot.html
Correct answer is: A
Answer D is wrong, since an EBS volume should be in the same AZ as the EC2 instance. You can not connect a EBS volume in an other AZ.
Thanks,
Frank
1
0
I think the answer is A, because answer D implies your attaching an EBS volume to the original EC2 instance in the original AZ and that’s not possible.
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ebs-restoring-volume.html
EBS volumes can only be attached to EC2 instances within the same Availability Zone.
0
0
I agree with the others. A.
0
0
A
0
0
a
0
0
Its A
1
0
I”m going with A
D is wrong, there is no mention of using Veritas Volume Manager or some other lvm, plus this would be a mirror, not a backup.
C is wrong , we’d want incremental snapshots to choose from in S3
B is wrong, recovery from Glacier takes hours
Alpha
0
0
further evidence for A:
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSSnapshots.html
0
0
A
D: it is not possible Different AZ volumes cant be attach to EC2 instance.
0
0
A
0
0
A.
Take periodic snapshots of the EBS volume
0
0
A
0
0