Oracle Cloud Infrastructure Documentation

Restoring a Backup to a New Volume

You can restore a backup of a volume as a new volume using Block Volume.


Avoid entering confidential information when assigning descriptions, tags, or friendly names to your cloud resources through the Oracle Cloud Infrastructure Console, API, or CLI.

Required IAM Policy

To use Oracle Cloud Infrastructure, you must be given the required type of access in a An IAM document that specifies who has what type of access to your resources. It is used in different ways: to mean an individual statement written in the policy language; to mean a collection of statements in a single, named "policy" document (which has an Oracle Cloud ID (OCID) assigned to it); and to mean the overall body of policies your organization uses to control access to resources. written by an administrator, whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you try to perform an action and get a message that you don’t have permission or are unauthorized, confirm with your administrator the type of access you've been granted and which A collection of related resources that can be accessed only by certain groups that have been given permission by an administrator in your organization. you should work in.

For administrators: The policy in Let volume admins manage block volumes, backups, and volume groups lets the specified group do everything with block volumes and backups.


When users create a backup from a volume or restore a volume from a backup, the volume and backup don't have to be in the same A collection of related resources that can be accessed only by certain groups that have been given permission by an administrator in your organization.. However, users must have access to both compartments.

If you're new to policies, see Getting Started with Policies and Common Policies. If you want to dig deeper into writing policies for instances, cloud networks, or other Core Services API resources, see Details for the Core Services.

Using the Console

  1. Open the navigation menu. Under Block Storage, click Block Volume Backups.

    A list of the block volume backups in the compartment you're viewing is displayed. If you don’t see the one you're looking for, make sure you’re viewing the correct compartment (select from the list on the left side of the page).

  2. Click the Actions icon (three dots) for the block volume backup you want to restore.
  3. Click Create Block Volume.
  4. Enter a name for the block volume and choose the availability domain in which you want to restore it.
  5. You can restore a block volume backup to a larger volume size. To do this, check Custom Block Volume Size (GB), and then specify the new size. You can only increase the size of the volume, you cannot decrease the size. If you restore the block volume backup to a larger size volume, you need to extend the volume's partition, see Extending the Partition for a Block Volume for more information.

  6. Optionally, you can select the appropriate backup policy for your requirements. See Policy-Based Backups for more information about backup policies.
  7. Optionally, you can encrypt the data in this volume using your own Key Management encryption key. To use Key Management for your encryption needs, select the Encrypt using Key Management check box. Then, select the Vault Compartment and Vault that contain the master encryption key you want to use. Also select the Master Encryption Key Compartment and Master Encryption Key. For more information about encryption, see Overview of Key Management.

  8. Optionally, you can apply tags. If you have permissions to create a resource, you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you are not sure if you should apply tags, skip this option (you can apply tags later) or ask your administrator.
  9. Click Create.

    The volume will be ready to attach once its icon no longer lists it as PROVISIONING in the volume list. For more information, see Attaching a Volume.


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.

Using the API

The API used to restore a backup is CreateVolume. The API has an optional volumeBackupId parameter that you can use to define the backup from which the data should be restored on the newly created volume. For details, see CreateVolumeDetails Reference.

For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.

For more information about backups, see Overview of Block Volume Backups and Backing Up a Volume.