cc_staff
1,486
edits
Backing up your VM: Difference between revisions
→An example backup strategy
No edit summary |
|||
| Line 34: | Line 34: | ||
==An example backup strategy== | ==An example backup strategy== | ||
Very large disk images (larger than 10-20 GB) can become difficult to manage with relatively long upload times and long VM creation times. A good basic strategy might be to separate large data sets from your operating system and software stack. The operating system and software stack can be | Very large disk images (larger than 10-20 GB) can become difficult to manage with relatively long upload times and long VM creation times. A good basic strategy might be to separate large data sets from your operating system and software stack. The operating system and software stack can be backed up either using a disk image or recreated using some provisioning software (see [[#Setup automation|setup automation]]). The data sets can then be backed up with using normal [[#File backup|file backup]] methods to a remote location. If you are using any database software such as MySQL or PostgreSQL you will want to create dumps of the databases to include in your backups. Finally, and most importantly, '''test restoring from your backup'''. If you can't restore from your backup it isn't that useful. | ||
==See also== | ==See also== | ||