Backing up your VM: Difference between revisions
No edit summary |
No edit summary |
||
Line 4: | Line 4: | ||
==Persistent VMs== | ==Persistent VMs== | ||
Persistent VMs are designed to boot from volumes (see []). | Persistent VMs are designed to boot from volumes (see [[OpenStack#Booting_from_a_Volume]]) and as such to back a persistent VM a copy can be created of the volume(s) the VM has attached to it. | ||
Go to the 'Volumes' tab, and from the drop down menue for the volume you wish to create an image of select 'Upload Volume to Images'. Select the 'QCOW2' Disk format and give your volume image a name. | |||
==Compute VMs== | ==Compute VMs== | ||
Revision as of 20:36, 17 November 2017
This is not a complete article: This is a draft, a work in progress that is intended to be published into an article, which may or may not be ready for inclusion in the main wiki. It should not necessarily be considered factual or authoritative.
It is often a good idea to backup your VM. The two main VM flavors persistent (p) and compute (c) have different behaviors and backups should be considered differently for each.
Persistent VMs
Persistent VMs are designed to boot from volumes (see OpenStack#Booting_from_a_Volume) and as such to back a persistent VM a copy can be created of the volume(s) the VM has attached to it.
Go to the 'Volumes' tab, and from the drop down menue for the volume you wish to create an image of select 'Upload Volume to Images'. Select the 'QCOW2' Disk format and give your volume image a name.
Compute VMs
- Volumes versus ephemeral drives?
- OpenStack Command Line Clients
- OpenStack#Creating_an_Image_from_a_VM
- OpenStack#Downloading_an_Image
- OpenStack#Uploading_an_Image