Backing up your VM: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
{{draft}} | {{draft}} | ||
It is often a good idea to backup your VM. The two main VM flavors the persistent (p) flavors and the compute (c) flavors have different behaviors and backups should be considered differently for each. | It is often a good idea to backup your VM. The two main VM flavors the persistent (p) flavors and the compute (c) flavors have different behaviors and backups should be considered differently for each. | ||
==Persistent VMs== | ==Persistent VMs== | ||
Revision as of 17:43, 17 November 2017
This article is a draft
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 the persistent (p) flavors and the compute (c) flavors have different behaviors and backups should be considered differently for each.
Persistent VMs
Persistent VMs are designed to boot from volumes (see []).
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