rsnt_translations
56,430
edits
Backing up your VM: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
Provisioning tools such as [https://www.ansible.com/ ansible], [https://puppet.com/ puppet], [https://www.chef.io/ chef], and [https://saltstack.com/ saltstack] can be used to automate setup and configuration of software and operating systems. Recreating your virtual machine then becomes a trivial matter given the right specification files for a given provisioning tool. These specification files can be managed with version control tools like [https://git-scm.com/ git]. Provisioning tools can be combined with orchestration tools such as heat and terraform (see [[Automating VM creation]]) to automate the entire process of virtual machine creation and software configuration. Any data which is generated or created outside this automation would then need to be backed up using one of the [[#File backup| file backup]] methods. | Provisioning tools such as [https://www.ansible.com/ ansible], [https://puppet.com/ puppet], [https://www.chef.io/ chef], and [https://saltstack.com/ saltstack] can be used to automate setup and configuration of software and operating systems. Recreating your virtual machine then becomes a trivial matter given the right specification files for a given provisioning tool. These specification files can be managed with version control tools like [https://git-scm.com/ git]. Provisioning tools can be combined with orchestration tools such as heat and terraform (see [[Automating VM creation]]) to automate the entire process of virtual machine creation and software configuration. Any data which is generated or created outside this automation would then need to be backed up using one of the [[#File backup| file backup]] methods. | ||
==OpenStack | ==OpenStack backup methods== <!--T:5--> | ||
OpenStack has two different storage options: Volumes, which are protected by 3 times replication, and ephemeral storage local to the VM. The 3 times replication of Volumes is to protect against hardware failure and does not protect against accidental deletion or data loss from malicious intent. Data stored on node local ephemeral storage can suffer data | OpenStack has two different storage options: Volumes, which are protected by 3 times replication, and ephemeral storage local to the VM. The 3 times replication of Volumes is to protect against hardware failure and does not protect against accidental deletion or data loss from malicious intent. Data stored on node local ephemeral storage can suffer data loss due to hardware failure and should not be relied upon for any critical data and is best suited to temporary or working data. | ||
<!--T:6--> | <!--T:6--> | ||
OpenStack provides tools to create disk images and snapshots of your virtual machines. The two main VM flavors - persistent (p) and compute (c) - have different behaviors | OpenStack provides tools to create disk images and snapshots of your virtual machines. The two main VM flavors - persistent (p) and compute (c) - have different behaviors, so we recommend different procedures for backing up each flavor. | ||
===Persistent VMs=== <!--T:7--> | ===Persistent VMs=== <!--T:7--> | ||