Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-1783

[RFE] cinder backup needs to restore thin volumes (new volumes only)

XMLWordPrintable

    • [RFE] cinder backup needs to restore thin volumes (new volumes only)
    • 8
    • False
    • False
    • OSPRH-5024Ceph RBD clone optimisations
    • Committed
    • No Docs Impact
    • OSPRH-5024 - Ceph RBD clone optimisations
    • Committed
    • Committed
    • 0% To Do, 33% In Progress, 67% Done
    • Hide
      .Enhanced Block Storage volume restoration on thinly provisioned back ends

      This enhancement optimizes the process of restoring Block Storage volume backups on any thinly provisioned back end. Previously, when restoring a backup on a thinly provisioned back end, the full volume size was restored instead of only restoring the portion of the volume that was used. This caused unnecessary network traffic and greatly increased the time taken by the restoration process. This enhancement ensures that when restoring a volume on a thinly provisioned back end, only the portion of the volume that was used is restored.
      Show
      .Enhanced Block Storage volume restoration on thinly provisioned back ends This enhancement optimizes the process of restoring Block Storage volume backups on any thinly provisioned back end. Previously, when restoring a backup on a thinly provisioned back end, the full volume size was restored instead of only restoring the portion of the volume that was used. This caused unnecessary network traffic and greatly increased the time taken by the restoration process. This enhancement ensures that when restoring a volume on a thinly provisioned back end, only the portion of the volume that was used is restored.
    • Enhancement
    • Done
    • Proposed
    • Rejected

      Description of problem:
      The current default behavior during a cinder-backup/cinder-restore procedure is that thin volumes are restored as thick. Taking much more space than necessary and creating problems during migration.

      It would be good if the original volume size is kept during backup/restore procedure.

      Version-Release number of selected component (if applicable):
      rhosp13/openstack-cinder-api:124

      How reproducible:
      100%

      Steps to Reproduce:
      1.Create empty volume (10GB size but 0B used)
      2.Cinder-backup to export the volume
      3.Cinder-restore to import the volume
      4.Volume now uses 10GB of disk space

      Actual results:
      Thin volume become thick

      Expected results:
      Thin volume stay thin

      Additional info:

              udesale@redhat.com Unmesh Desale
              jira-bugzilla-migration RH Bugzilla Integration
              Yosi Ben Shimon Yosi Ben Shimon
              rhos-dfg-storage-squad-cinder
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: