Oracle Cloud Infrastructure Documentation

Volume Groups

The Oracle Cloud Infrastructure Block Volume service provides you with the capability to group together multiple volumes in a volume group. A volume group can include both types of volumes, boot volumes, which are the system disks for your Compute instances, and block volumes for your data storage. You can use volume groups to create volume group backups and clones that are point-in-time and crash-consistent.

This simplifies the process to create time-consistent backups of running enterprise applications that span multiple storage volumes across multiple instances. You can then restore an entire group of volumes from a volume group backup.

Similarly, you can also clone an entire volume group in a time-consistent and crash-consistent manner. A deep disk-to-disk and fully isolated clone of a volume group, with all the volumes associated in it, becomes available for use within a matter of seconds. This speeds up the process of creating new environments for development, quality assurance, user acceptance testing, and troubleshooting.

For more information about Block Volume-backed system disks, see Boot Volumes. For more information about Block Volume backups see Overview of Block Volume Backups. See Cloning a Volume for more information about Block Volume clones.

This capability is only available using the command line interface (CLI) or REST APIs.

Volume groups and volume group backups are high-level constructs that allow you to group together multiple volumes. When working with volume groups and volume group backups, keep the following in mind:

  • You can only add a volume to a volume group when the volume status is available.

  • You can add up to 10 volumes in a volume group. This is the default limit and can be increased up to 64 volumes with a limit increase request for your tenancy.

  • Each volume may only be in one volume group.

  • When you clone a volume group, a new group with new volumes are created. For example, if you clone a volume group containing three volumes, once this operation is complete, you will now have two separate volume groups and six different volumes with nothing shared between the volume groups.

  • You need to specify all the volumes to include in the volume group each time you use the update operation. If you do not include a volume ID in the update call, that volume will be removed from the volume group.

  • When you delete a volume group the individual volumes in the group are not deleted, only the volume group is deleted.

  • When you delete a volume that is part of a volume group you must first remove it from the volume group before you can delete it.

  • When you delete a volume group backup, all the volume backups in the group are deleted.

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 and backups lets the specified group do everything with block volumes and backups. The policy in Let volume backup admins manage only backups further restricts access to just creating and managing backups.

Tip

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 CLI

For information about using the CLI, see Command Line Interface (CLI).

To retrieve information about the supported operations

Volume Group Operations

To list the volume groups in a specified compartment
To create a volume group from existing volumes
To clone a volume group from another volume group
To restore a volume group from a volume group backup
To retrieve a volume group
To update display name or add/remove volumes from a volume group
To delete a volume group

Volume Group Backup Operations

To list volume backup groups
To create a volume group backup
To retrieve a volume group backup
To update display name for a volume group backup
To delete a volume group backup

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.

Use the following operations for working with volume groups:

Use the following operations for working with volume group backups: