Pre-requisite: EWC - OpenStack Command-Line client |
When backing up resources in OpenStack, it's important to understand the difference between two primary methods:
Choose the appropriate method based on your recovery needs: volume backups for data recovery, VM images for full system recovery or replication.
Before starting make sure you are in the machine where you configured openstack client and you can run openstack commands as described in EWC - OpenStack Command-Line client |
To list all available backups in your cloud, you can use the following command:
openstack volume backup list |
Additionally, you can filter the results with additional options to list backups for a specific volume:
openstack volume backup list --volume VOLUME_ID |
To create a backup of a volume:
openstack volume backup create [--incremental] [--force] [--name NAME] VOLUME |
Where:
--incremental: Create an incremental backup (requires a previous full backup)--force: Create a backup even if the volume is attached--name NAME: Specify a name for the backupVOLUME: The ID or name of the volume to back upsudo umount --verbose <path-to-volume> |
openstack volume backup restore BACKUP_ID VOLUME_ID |
Where:
BACKUP_ID: The ID of the backup to restoreVOLUME_ID: The ID of the volume to restore to (must be at least as large as the original volume)3. Now, you need to attach the volume again to the VM as explained in `Configuring the extra volume in the instance`.
To list all available images:
openstack image list |
To create a new VM from an image:
openstack server image create --name IMAGE_NAME SERVER |
Where:
--name IMAGE_NAME: The name for the new imageSERVER: The ID or name of the server to create an image fromOpenStack provide a mechanism to replace the underlying disk of an existing VM with an image without creating a new VM instance running the following command:
openstack server rebuild VM-NAME --image IMAGE_ID |
where
VM-NAME: The name of the existing image
IMAGE_ID: Name of the backup image of the VM you created before