Red Hat Summit Red Hat SummitSupportConsoleDevelopersStart a trialContact

Chapter 4. Customizing the Block Storage backup service

When you have deployed the backup service for the Block Storage service (cinder), you can change the default parameters.

Prerequisites

  • You have the oc command line tool installed on your workstation.
  • You are logged on to a workstation that has access to the RHOSO control plane as a user with cluster-admin privileges.

Administrators can back up any volume belonging to the project. To ensure that the volume owner can also access the volume backup, administrators must provide arguments to authenticate the volume owner when backing up the volume.

Procedure

  • Provide the following arguments to authenticate a volume owner for access to volume backups: 

    $ openstack --os-project-name <projectname> \
--os-username <username> \
--os-password <password> \
volume backup create [--name <backup_name>] <volume>
    Copy to Clipboard Toggle word wrap
    • Replace <projectname> with the name of the project (tenant) of the owner of the volume.
    • Replace <username> and <password> with the username and password credentials of the user that is the owner of the volume within this project.
Note

[--name <backup_name>] <volume> are the typical arguments when creating a volume backup.

4.2. Viewing and modifying project backup quotas
Copy link

You can change or view the limits of the following resource quotas that apply to Block Storage volume backups that users can create for each project (tenant):

  • backups, specify the maximum number of Block Storage volume backups that users of this project can create. By default, this limit is set to 10.
  • backup-gigabytes, specify the total size, in gigabytes, of all the Block Storage volume backups that users of this project can create. By default, this limit is set to 1000.

You can also view the usage of these Block Storage backup resource quotas for each project.

Procedure

  1. Access the remote shell for the OpenStackClient pod from your workstation: 

    $ oc rsh -n openstack openstackclient
$ source ./cloudrc
    Copy to Clipboard Toggle word wrap
    Note

    If the cloudrc file does not exist, then type in the exit command and create this file. For more information, see Creating the cloudrc file.

  2. Optional: List the projects to obtain the ID or name of the required project: 

    $ openstack project list
    Copy to Clipboard Toggle word wrap

  3. View the current limits of the backup quotas for a specific project: 

    $ openstack quota show <project>
    Copy to Clipboard Toggle word wrap

    • Replace <project> with the ID or name of the required project.

      This provides the limits of all the resource quotas for the specified project. Take note of the Limit column for the backup-gigabytes and backups fields in the table. For example: 

      $ openstack quota show c2c1da89ed1648fc8b4f35a045f8d34c
+-----------------------+-------+
| Resource              | Limit |
+-----------------------+-------+
...
| backups               |    10 |
...
| backup-gigabytes      |  1000 |
...
+-----------------------+-------+
      Copy to Clipboard Toggle word wrap

  4. Optional: Modify the total size of all the Block Storage volume backups that users can create for a project: 

    $ openstack quota set --backup-gigabytes <totalgb> <project>
    Copy to Clipboard Toggle word wrap
    • Replace <totalgb> with the total size, in gigabytes, of the backups that users can create for this project.

  5. Optional: Modify the maximum number of the Block Storage volume backups that users can create for a project: 

    $ openstack quota set --backups <maxnum> <project>
    Copy to Clipboard Toggle word wrap
    • Replace <maxnum> with the maximum number of backups that users can create for this project.

  6. Optional: View the usage of these Block Storage volume backup quotas and, if necessary, review any changes to their limits for a specific project: 

    $ cinder quota-usage <project_id>
    Copy to Clipboard Toggle word wrap

    • Replace <project_id> with the ID of the project.

      The first two rows in this table specify the backup quotas for the specified project. Look at the following columns in this table:

    • The In_use column indicates how much of each resource has been used.

    • The Limit column indicates whether the quota limits have been adjusted from their default settings, in this example both have been adjusted. 

      $ cinder quota-usage c2c1da89ed1648fc8b4f35a045f8d34c
+-----------------------+--------+----------+-------+-----------+
| Type                  | In_use | Reserved | Limit | Allocated |
+-----------------------+--------+----------+-------+-----------+
| backup_gigabytes      | 235    | 0        | 500   |           |
| backups               | 7      | 0        | 12    |           |
...
      Copy to Clipboard Toggle word wrap

  7. Exit the openstackclient pod: 

    $ exit
    Copy to Clipboard Toggle word wrap
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat