Editing Futotemporarywikipage (section)

== 4. Idiotproof backups - the most important one ==

This is a beginner’s guide. Backing up Docker volumes, containers, networks, images, and configs is 100% doable. But let’s be honest, it requires some degree of competence. Backing up a virtual machine, on the other hand, is '''completely idiot-proof.'''

* A virtual machine backup is just a single <code>.qcow2</code> disk image and a single <code>.xml</code> configuration file. Drag and drop those two files to another system, import them into Virtual Machine Manager, and the virtual machine runs.
* There’s no need to rebuild Docker containers, recreate volumes, or edit <code>docker-compose.yml</code> files. It’s so simple that someone with absolutely no technical expertise could do it in one click.
* Infact it is so easy that even I can do it. If I can do it, it is truly idiotproof.

The backup script I provide is one I use myself. Once a week, it backs up all of my virtual machines as well as their configuration files to a ZFS pool which will continue running even if several hard drives fail. If I screw something up, it is two terminal commands or a few clicks in the GUI &amp; I’m back up &amp; running as if nothing stupid ever happened.

'''For beginners, when it comes to backups, simplicity is priceless.'''

Added complexity means you are less likely to ''use'' your backup system &amp; less likely to ''understand'' how restoring from a backup works.

<span id="why-this-guide-uses-virtual-machines"></span>