| Info |
|---|
Pre-requisite: EWC - OpenStack Command-Line client |
...
| Table of Contents |
|---|
Foreword
Before restoring
...
When backing up resources in OpenStack, it's important to understand the difference between two three primary methods:
- VM Images Intance Snapshots (Glance): These capture the entire virtual machine, including the operating system, applications, and configuration. VM images Instance snapshots are useful for cloning VMs, creating templates, or disaster recovery scenarios. They're managed through the Glance service.
- Volume Snapshots (Cinder): These are delta copies of the block storage volumes. Volume snapshots are not full copies and rely on the original volume for restoration, so they are mostly useful for accident recovery. They're managed through the Cinder service.
- Volume Backups (Cinder): These are point-in-time copies of block storage volumes. Volume backups preserve the data within a volume and can be used to restore the volume to the exact state it was in when backed up. They're ideal for data recovery and are managed through the Cinder service.
Choose the appropriate method based on your recovery needs: volume backups for data recovery, VM images for full system recovery or replicationinstance snapshots for full system recovery or replication, volume snapshots for accident prevention and recovery or volume backups for full data security and recovery.
| Info |
|---|
| 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 |
| Warning |
|---|
| When creating backups or snapshots of VMs and volumes, it is highly recommended that the following command are run outside from said VMs and volumes. Doing so from within may cause corrupted backups or snapshots |
Restoring VMs and Volumes
Restoring VMs from ImagesAnchor RestoringVMImages RestoringVMImages
| RestoringVMImages | |
| RestoringVMImages |
OpenStack 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:
|
where
VM-NAME: The name of the existing VMIMAGE_ID: Name of the backup image of the VM you created before
Restoring Volume BackupsAnchor RestoringVolumeBackups RestoringVolumeBackups
| RestoringVolumeBackups | |
| RestoringVolumeBackups |
...
3. Now, you need to attach the volume again to the VM as explained in `Configuring the extra volume in the instance`.
Common use cases
WIP
Backup automation
WIP