|
|
| (17 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| == Livebackup - A full backup solution for making full and incremental disk backups of a running VM == | | {| class="wikitable" style="margin: 2em; border:1px solid black;" |
| Livebackup provides the ability for an administrator or a management server to use a livebackup_client program to connect to the qemu process and copy the disk blocks that were modified since the last backup was taken.
| | | |
| | '''Note: This feature proposal is available via archive only, the code was not merged into QEMU. |
|
| |
|
| == Contact ==
| | The [[Features/IncrementalBackup|Incremental Backup]] feature was merged into QEMU instead for the 2.4 development window. |
| Jagane Sundar (jagane at sundar dot org)
| |
|
| |
|
| == Overview ==
| | For the old feature proposal, please see [http://wiki.qemu.org/index.php?title=Features/Livebackup&oldid=1188 Livebackup (2011-05-09)]''' |
| The goal of this project is to add the ability to do full and incremental disk backups of a running VM. These backups will be transferred over a TCP connection to a backup server, and the virtual disk images will be reconstituted there. This project does not transfer the memory contents of the running VM, or the device states of emulated devices, i.e. livebackup is not VM suspend.
| | |} |
|
| |
|
| == Source Code Repositories ==
| | [[Category:Obsolete feature pages]] |
| Currently, Livebackup is available as an enhancement to both the qemu and qemu-kvm projects. The goal is to get Livebackup accepted by the qemu project, and then flow through to the qemu-kvm project.<br>
| |
| Clone git://github.com/jagane/qemu-livebackup.git to get access to a clone of the qemu source tree with Livebackup enhancements.<br>
| |
| Clone git://github.com/jagane/qemu-kvm-livebackup.git to get access to a clone of the qemu-kvm source tree with Livebackup enhancements.<br>
| |
| | |
| == Use Cases ==
| |
| Today IaaS cloud platforms such as EC2 provide you with the ability to have two types of virtual disks in VM instances
| |
| * ephemeral virtual disks that are lost if there is a hardware failure
| |
| * EBS storage volumes which are costly (EBS stands for Elastic Block Storage - Amazon EC2's block storage with availability guarantees)
| |
| I think that an efficient disk backup mechanism will enable a third type of virtual disk - one that is backed up, perhaps every hour or so. So a cloud operator using KVM virtual machines can offer three types of VMS:
| |
| * an ephemeral VM that is lost if a hardware failure happens
| |
| * a backed up VM that can be restored from the last hourly backup
| |
| * a fully highly available VM running off of shared storage.
| |
| | |
| == High Level Design ==
| |
| * During normal operation, livebackup code in qemu keeps an in-memory bitmap of blocks modified.
| |
| * When a backup client connects to the livebackup thread in qemu, it creates a snapshot
| |
| * A snapshot, in livebackup terms, is merely the dirty blocks bitmap of all virtual drives configured for the VM
| |
| * After the snapshot is created, livebackup_client starts to transfer the modified blocks over to the backup server
| |
| * The snapshot is maintained during the time that this transfer happens, after which it is destroyed.
| |
| * Note that when this snapshot is active, any write by the VM to the underlying virtual disk has to be intercepted, and if the write overlaps a block that is marked as dirty in the snapshot's livebackup dirty blocks bitmap, then the blocks from the underlying virtual disk have to be copied over to a COW file in the snapshot, before being overwritten.
| |
| | |
| == Illustrations ==
| |
| === Normal Operation ===
| |
| [[File:Livebackup-1.png|border]] | |
| === livebackup_client calls snapshot before transferring dirty blocks ===
| |
| [[File:Livebackup-2.png|border]]
| |
| === While a backup operation is in progress ===
| |
| [[File:Livebackup-3.png|border]]
| |
| == Details ==
| |
| * When qemu block driver is called to open a virtual disk file, it checks for the presence of a file with suffix .livebackupconf, for example when opening the file vdisk0.img, it would look for a file called vdisk0.img.livebackupconf.
| |
| * If the livebackupconf file exists, then this disk is part of the backup set, and the block driver for that virtual disk starts tracking blocks that are modified using an in-memory dirty blocks bitmap. This in-memory dirty blocks bitmap is saved to a file called vdisk0.img.dirty_blocks when the VM shuts down. Thus this dirty blocks bitmap is persisted across VM reboots. It is operated on in memory when the VM is running, but saved to disk when the VM shuts down, and read in again when the VM boots.
| |
| * qemu starts a livebackup thread, that listens on a TCP port for connections from livebackup_client
| |
| * When the operator wants to take an incremental backup of the running VM, he uses the program livebackup_client. This program opens a TCP connection to the qemu process' livebackup thread.
| |
| * First, the livebackup_client issues a snapshot command.
| |
| * qemu saves the dirty blocks bitmap of each virtual disk in a snapshot struct, and allocates new in-memory dirty blocks map for each virtual disk
| |
| * From now on, till the livebackup_client destroys the snapshot, each write from the VM is checked by the livebackup interposer. If the blocks written are already marked as dirty in the snapshot struct's dirty blocks bitmap, the original blocks are saved off in a COW file before the VM write is allowed to proceed.
| |
| * The livebackup_client now iterates through all the dirty blocks in the snapshot, and transfers them over to the backup server. It can either reconstitute the virtual disk image at the time of the backup by writing the blocks to the virtual disk image file, or can save the blocks in a COW redo file of qcow, qcow2 or vmdk format.
| |
| * The important thing to note is that the time for which qemu needs to copy the original blocks and save them in a COW file is equal to the time that the livebackup_client program is connected to qemu and transferring blocks. This is hopefully something like 15 minutes out of 24 hours or so.
| |
| | |
| | |
| == Comparison to other proposed qemu features that solve the same problem ==
| |
| === Snapshots and Snapshots2 ===
| |
| [http://wiki.qemu.org/Features/Snapshots snapshots]<br>
| |
| [http://wiki.qemu.org/Features/Snapshots2 snapshots2]<br>
| |
| In both of these proposals, the original virtual disk is made read-only and the VM writes to a different COW file. After backup of the original virtual disk file is complete, the COW file is merged with the original vdisk file.
| |
| | |
| Instead, I create an Original-Blocks-COW-file to store the original blocks that are overwritten by the VM everytime the VM performs a write while the backup is in progress. Livebackup copies these underlying blocks from the original virtual disk file before the VM's write to the original virtual disk file is scheduled. The advantage of this is that there is no merge necessary at the end of the backup, we can simply delete the Original-Blocks-COW-file.
| |
| | |
| Here's Stefan Hajnoczi's feedback (Thanks, Stefan)<br>
| |
| Here's what I understand:
| |
| 1. User takes a snapshot of the disk, QEMU creates old-disk.img backed by the current-disk.img.
| |
| 2. Guest issues a write A.
| |
| 3. QEMU reads B from current-disk.img.
| |
| 4. QEMU writes B to old-disk.img.
| |
| 5. QEMU writes A to current-disk.img.
| |
| 6. Guest receives write completion A.
| |
| The tricky thing is what happens if there is a failure after Step 5. If writes A and B were unstable writes (no fsync()) then no ordering is guaranteed and perhaps write A reached current-disk.img but write B did not reach old-disk.img. In this case we no longer have a consistent old-disk.img snapshot - we're left with an updated current-disk.img and old-disk.img does not have a copy of the old data.<br>
| |
| The solution is to fsync() after Step 4 and before Step 5 but this will hurt performance. We now have an extra read, write, and fsync() on every write.<br>
| |
| | |
| == Failure Scenarios ==
| |
| === qemu crashes during normal operation of the VM ===
| |
| When this happens, the livebackup_client is forced to do a full backup the next time around. Here's how: livebackup writes out the in-memory dirty bitmap to a dirty bitmap file only at the time of orderly shutdown of qemu. Hence, the mtime of the virtual disk file is later than the mtime of the livebackup dirty bitmap file. This causes livebackup to consider the dirty bitmap invalid, and forces the livebackup_client to do a full backup next time around.
| |
| | |
| | |
| == Other technologies that may be used to solve this problem ==
| |
| === LVM snapshots ===
| |
| It is possible to create a new LVM partition for each virtual disk in the VM. When a VM needs to be backed up, each of these LVM partitions is snapshotted. At this point things get messy - I don't really know of a good way to identify the blocks that were modified since the last backup. Also, once these blocks are identified, we need a mechanism to transfer them over a TCP connection to the backup server. Perhaps a way to export the 'dirty blocks' map to userland and use a deamon to transfer the block. Or maybe a kernel thread capable of listening on TCP sockets and transferring the blocks over to the backup client (I don't know if this is possible).
| |
