Backup Methodologies for Fastest Database Restore Time in Limited Storage Space

Which Backup Methodology Should You Implement for Fastest Database Restore Time in Limited Storage Space?

Prev Question Next Question

Question

A company has limited storage space available and an online presence that cannot be down for more than four hours.

Which of the following backup methodologies should the company implement to allow for the FASTEST database restore time in the event of a failure, while being mindful of the limited available storage space?

A.

Implement full tape backups every Sunday at 8:00 p.m.

and perform nightly tape rotations. B.

Implement differential backups every Sunday at 8:00 p.m.

and nightly incremental backups at 8:00 p.m. C.

Implement nightly full backups every Sunday at 8:00 p.m. D.

Implement full backups every Sunday at 8:00 p.m.

and nightly differential backups at 8:00 p.m.

B.

Explanations

A company has limited storage space available and an online presence that cannot be down for more than four hours.

Which of the following backup methodologies should the company implement to allow for the FASTEST database restore time in the event of a failure, while being mindful of the limited available storage space?

A.

Implement full tape backups every Sunday at 8:00 p.m.

and perform nightly tape rotations.

B.

Implement differential backups every Sunday at 8:00 p.m.

and nightly incremental backups at 8:00 p.m.

C.

Implement nightly full backups every Sunday at 8:00 p.m.

D.

Implement full backups every Sunday at 8:00 p.m.

and nightly differential backups at 8:00 p.m.

B.

Option B is the correct answer for this scenario. The reason is that differential backups capture all changes made since the last full backup, whereas incremental backups capture changes made since the last backup, whether it was a full or incremental backup. In this scenario, full backups every night would consume a lot of storage space, and the company has limited storage available. Therefore, the company needs to strike a balance between backup frequency and storage space.

Implementing full tape backups every Sunday at 8:00 p.m. and performing nightly tape rotations (Option A) would be a good solution if storage space were not an issue, but in this scenario, it is. Performing full backups every night would consume a lot of storage space and would not be the most efficient solution.

Implementing nightly full backups every Sunday at 8:00 p.m. (Option C) would also consume a lot of storage space, especially if the database is large. This option would also take longer to restore in case of a failure.

Implementing full backups every Sunday at 8:00 p.m. and nightly differential backups at 8:00 p.m. (Option D) would also consume a lot of storage space, especially if the database is large. Differential backups capture all changes made since the last full backup, so if a failure occurs, it would take longer to restore the database.

Therefore, implementing differential backups every Sunday at 8:00 p.m. and nightly incremental backups at 8:00 p.m. (Option B) would be the best solution in this scenario. This option strikes a balance between backup frequency and storage space and would allow for the fastest database restore time in case of a failure, while being mindful of the limited available storage space.