Editing Backup of a running container with vzdump
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 84: | Line 84: | ||
While the LVM solution is the cleanest, since it allows to create an online backup without having to stop or suspend the virtual machine, it is also the hardest to set up. There are a few dependencies you should be aware of before setting up your LVM: | While the LVM solution is the cleanest, since it allows to create an online backup without having to stop or suspend the virtual machine, it is also the hardest to set up. There are a few dependencies you should be aware of before setting up your LVM: | ||
− | * You need to have at least 512MB free in | + | * You need to have at least 512MB free in the volume group that is hosting your virtuals (usually <code>/vz/private</code>) |
− | * The directory where you are writing your backup dumps to (usually <code>/vz/dump</code>) should be on a different volume group than the one you are taking a backup from | + | * The directory where you are writing your backup dumps to (usually <code>/vz/dump</code>) should be on a different volume group than the one you are taking a backup from |
* There is a bug in <code>VZDump.pm</code> that can make the snapshot creation fail | * There is a bug in <code>VZDump.pm</code> that can make the snapshot creation fail | ||