Backing up your VM/fr: Difference between revisions

Created page with "===Instances persistantes=== Persistent VMs are designed to boot from volumes (see Les instances persistantes sont conçues pour être OpenStack/fr#Démarrer_depuis_un_volum..."
No edit summary
(Created page with "===Instances persistantes=== Persistent VMs are designed to boot from volumes (see Les instances persistantes sont conçues pour être OpenStack/fr#Démarrer_depuis_un_volum...")
Line 17: Line 17:
OpenStack offre aussi des outils pour créer des images de disques et des instantanés d’instances. Les gabarits d’instance principaux p (‘’persistent’’) et c (‘’compute’’) ont des comportements différents; nous recommandons donc des procédures différentes de sauvegarde pour chaque gabarit.
OpenStack offre aussi des outils pour créer des images de disques et des instantanés d’instances. Les gabarits d’instance principaux p (‘’persistent’’) et c (‘’compute’’) ont des comportements différents; nous recommandons donc des procédures différentes de sauvegarde pour chaque gabarit.


===Persistent VMs===
<div class="mw-translate-fuzzy">
Persistent VMs are designed to boot from volumes (see [[OpenStack#Booting_from_a_Volume| booting from a volume]]) thus creating a copy of the volume(s) the VM has attached to it will produce a backup. However this would not preserve things like VM flavor, public IP, and security rules. The best way to create a copy of a volume for backup purposes is to create an image from that volume. An image can be [[OpenStack#Downloading_an_Image|downloaded]] and reused to create multiple new VMs, can be [[OpenStack#Creating_a_VirtualBox_VM_from_a_Cloud_Image|accessed by VirtualBox]] on your desktop or laptop, and [[OpenStack#Uploading_an_Image|uploaded]] to other clouds.
===Instances persistantes===
Persistent VMs are designed to boot from volumes (see Les instances persistantes sont conçues pour être [[OpenStack/fr#Démarrer_depuis_un_volume|démarrées depuis un volume]]. Une copie de sauvegarde est créée lorsqu’une copie du ou des volumes associés à l’instance est créée. Cependant, ceci ne comprend pas le gabarit de l’instance, son IP publique et ses règles de sécurité. La meilleure manière de créer une copie de sauvegarde d’un volume est donc de créer une image de ce volume. Cette image peut alors être [[OpenStack#Creating_an_Image_from_a_VM/fr#Télécharger_une_image|téléchargée]] et réutilisée pour créer plusieurs nouvelles instances; vous pouvez y [[OpenStack#Creating_an_Image_from_a_VM/fr#Créer_une_instance_VirtualBox_depuis_une_image_d’un_nuage| accéder par VirtualBox]] à partir de votre ordinateur personnel; ou la [[OpenStack#Creating_an_Image_from_a_VM/fr#Téléverser_une_image|téléverser]] vers un autre nuage.
</div>


To be able to create an image from a volume, that volume must be detached from the VM. In addition, if the volume is the root volume of the VM it cannot be detached unless the VM is deleted. If you are sure that when you created the VM you did not check the box "Delete Volume on Instance Delete", then you can delete your VM knowing you will not lose any data. However, if you are unsure whether or not you checked this box, OpenStack unfortunately doesn't tell you if this box was checked when you created a VM. One trick which may be useful for getting around this deficiency is to create a snapshot of the volume provided you have a storage quota which allows it, since snapshots count towards your storage quota. As volumes cannot be deleted if there is a volume snapshot created from them, when you delete the VM the volume will not be deleted even if you checked the box.
To be able to create an image from a volume, that volume must be detached from the VM. In addition, if the volume is the root volume of the VM it cannot be detached unless the VM is deleted. If you are sure that when you created the VM you did not check the box "Delete Volume on Instance Delete", then you can delete your VM knowing you will not lose any data. However, if you are unsure whether or not you checked this box, OpenStack unfortunately doesn't tell you if this box was checked when you created a VM. One trick which may be useful for getting around this deficiency is to create a snapshot of the volume provided you have a storage quota which allows it, since snapshots count towards your storage quota. As volumes cannot be deleted if there is a volume snapshot created from them, when you delete the VM the volume will not be deleted even if you checked the box.
rsnt_translations
56,437

edits