Oracle Cloud Infrastructure Documentation

Overview of Block Volume Backups

The backups feature of the Oracle Cloud Infrastructure Block Volume service lets you make a point-in-time backup of data on a block volume. These backups can then be restored to new volumes either immediately after a backup or at a later time that you choose. Backups are encrypted and stored in Oracle Cloud Infrastructure Object Storage, and can be restored as new volumes to any availability domain within the same region they are stored. This capability provides you with a spare copy of a volume and gives you the ability to successfully complete disaster recovery within the same region.

There are two ways you can initiate a backup, either by manually starting the backup, or by assigning a policy which defines a set backup schedule.

Manual Backups

These are on-demand one-off backups that you can launch immediately by following the steps described in Backing Up a Volume. When launching a manual backup, you can specify whether an incremental or full backup should be performed. See Volume Backup Types for more information about backup types.

Policy-Based Backups

These are automated scheduled backups. Each backup policy has a set backup frequency and retention period. There are three predefined policies, Bronze, Silver, and Gold.

See Policy-Based Backups for more information.

Volume Backup Types

There are two backup types available in the Block Volume service:

  • Incremental: This backup type includes only the changes since the last backup.

  • Full: This backup type includes all changes since the volume was created.

Note

Backup Details

Backups are not an identical copy of the volume being backed up. For incremental backups, they are a record of all the changes since the last backup. For full backups, they are a record of all the changes since the volume was created. For example, in a scenario where you create a 16 TB block volume, modify 40 GB on the volume, and then launch a full backup, upon completion the volume backup size is 40 GB.

Planning Your Backup

The primary use of backups is to support business continuity, disaster recovery, and long-term archiving. When determining a backup schedule, your backup plan and goals should consider the following:

  • Frequency: How often you want to back up your data.
  • Recovery time: How long you can wait for a backup to be restored and accessible to your applications that use it. The time for a backup to complete varies on several factors, but it will generally take a few minutes or longer, depending on the size of your data being backed up and the amount of data that has changed since your last backup.
  • Number of stored backups: How many backups you need to keep available and the deletion schedule for those you no longer need. You can only create one backup at a time, so if a backup is underway, it will need to complete before you can create another one. For details about the number of backups you can store, see Block Volume Capabilities and Limits.

The common use cases for using backups are:

  • Creating multiple copies of the same volume. Backups are highly useful in cases where you need to create many instances with many volumes that need to have the same data formation.
  • Taking a snapshot of your work that you can restore to a new volume at a later time.
  • Ensuring you have a spare copy of your volume in case something goes wrong with your primary copy.

Copying Block Volume Backups Across Regions

You can copy block volume backups between regions using the Console, command line interface (CLI), SDKs, or REST APIs, see Copying a Volume Backup Between Regions. This capability enhances the following scenarios:

  • Disaster recovery and business continuity:

    By copying block volume backups to another region at regular intervals, it makes it easier for you to rebuild applications and data in the destination region if a region-wide disaster occurs in the source region.
  • Migration and expansion: You can easily migrate and expand your applications to another region.

To copy volume backups between regions, you must have permission to read and copy volume backups in the source region, and permission to create volume backups in the destination region. For more information see Required IAM Policy.

Once you have copied the volume backup to the new region you can then restore from that backup by creating a new volume from the backup using the steps described in Restoring a Backup to a New Volume.

Best Practices When Creating Block Volume Backups

When creating and restoring from backups, keep in mind the following:

  • Before creating a backup, you should ensure that the data is consistent: Sync the file system, unmount the file system if possible, and save your application data. Only the data on the disk will be backed up. When creating a backup, once the backup state changes from REQUEST_RECEIVED to CREATING, you can return to writing data to the volume. While a backup is in progress, the volume that is being backed up cannot be deleted.
  • If you want to attach a restored volume that has the original volume attached, be aware that some operating systems do not allow you to restore identical volumes. To resolve this, you should change the partition IDs before restoring the volume. How to change an operating system's partition ID varies by operating system; for instructions, see your operating system's documentation.
  • You should not delete the original volume until you have verified that the backup you created of it completed successfully.

See Backing Up a Volume and Restoring a Backup to a New Volume for more information.