A volume backup can only be restored on the same Block Storage service, because restoring a volume from a backup requires metadata available on the database used by the Block Storage service. For information about how to back up and restore a volume Backing up and Restoring Volumes and Snapshots .
To export the metadata of a volume backup, run the following command as a Metacloud admininstrator. It is recommended that you create a volume backup before proceeding with this export.
$ cinder backup-export BACKUP_ID
BACKUP_ID is the ID of the volume backup. This command returns the corresponding database information as encoded string metadata.
Exporting and storing this encoded string metadata enables you to completely restore the backup, even in the event of a catastrophic database failure. This precludes the need to back up the entire Block Storage database, particularly if you only need to keep complete backups of a small subset of volumes.
If you have enabled encryption on your volumes, you must specify a UUID encryption key when you create the volume to ensure the key remains in place when you restore the volume. Using backup metadata support, UUID keys specified for a volume remain valid when you restore a backed-up volume. The restored volume will remain encrypted and will be accessible with your credentials.
Having a volume backup and the corresponding backup metadata also provides volume portability. Backing up a volume and exporting the metadata enables you to restore the volume on a different Block Storage database or a different cloud service.
To import backup metadata, run the following command as a Metacloud administrator:
$ cinder backup-import METADATA
METADATA is the exported backup metadata.
Once you have imported the backup metadata into a Block Storage database, restore the volume see Backing up and Restoring Volumes and Snapshots .