Backup Strategies for Legacy Applications on Oracle Cloud Infrastructure (OCI)

Secure and Cost-Effective Block Volume Backup

Question

You are running a legacy application in a compute instance on Oracle Cloud Infrastructure (OCI)

To provide enough space for it to store internal data, a block volume is attached to the instance in paravirtualized mode.

Your application is not resilient to crash-consistent backup.

What should you do to backup the block volume in a secure and cost effective way? (Choose the best answer.)

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D.

B.

The correct answer is D. Save your application data, detach the block volume and create a backup.

Explanation: The scenario described in the question is that the legacy application in the compute instance requires additional space to store internal data, and a block volume has been attached in paravirtualized mode to provide this extra storage capacity. The application is not resilient to crash-consistent backup.

In order to backup the block volume in a secure and cost-effective way, the recommended approach is to follow these steps:

  1. Save your application data: Before initiating any backup, it's always a good practice to save your application data to ensure that you don't lose any important data during the backup process.

  2. Detach the block volume: Detaching the block volume ensures that the volume is not being actively used by the application, and that any data written to the volume during the backup process is consistent.

  3. Create a backup: Once the block volume is detached, create a backup of the volume. The backup can be created using the OCI Console or the OCI CLI. The backup can be stored in the same region or in a different region for better disaster recovery.

By following these steps, you can ensure that the backup is secure and cost-effective. Option A (Save your application data, detach the block volume and create a clone) is not a recommended approach as creating a clone of the block volume can result in higher costs and also won't provide versioning of the backup. Option B (Create a volume group, add the boot volume and then run the volume group backup) is not a valid approach as a volume group backup won't backup the attached block volume. Option C (Create a backup, detach the block volume and save your application data) is not a recommended approach as detaching the block volume before creating a backup can result in data loss if any data is written to the volume during the detachment process.