Oracle Cloud Infrastructure Documentation

Restoring a Boot Volume

You can use a boot volume backup to create an instance or you can attach it to another instance as a data volume. However before you can use a boot volume backup, you need to restore it to a boot 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.

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 Core Infrastructure, go to Compute and click Boot Volume Backups.

  2. Choose your Compartment.

  3. In the list of boot volume backups, click the Actions icon (three dots) for the boot volume backup you want to restore and then click Create Boot Volume.

  4. Specify a name for the boot volume, select the availability domain to use, and optionally choose a backup policy for scheduled backups. See Policy-Based Backups for more information about scheduled backups and volume backup policies.

  5. You can restore a boot 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 Boot Volume for more information.

  6. Click Create Boot Volume.

    The boot volume will be ready to use once its icon no longer lists it as PROVISIONING in the details page for the boot volume.

Using the API

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.

To restore a boot volume backup, use the CreateBootVolume operation and specify BootVolumeSourceFromBootVolumeBackupDetails for CreateBootVolumeDetails.

Next Steps

After you have restored the boot volume backup, you can:

  • Use the boot volume to create an instance, for more information, see Creating an Instance.

  • Attach the boot volume to an instance as a data volume, for more information, see Attaching a Volume.

Making a boot volume backup while an instance is running creates a crash-consistent backup, meaning the data is in the identical state it was in at the time the backup was made. This is the same state it would be in the case of a loss of power or hard crash. In most cases you can use the restored boot volume to create an instance, however to ensure a bootable image, you should create a custom image from your instance. For information about creating custom images, see Managing Custom Images.