Open Stack

On Mon, May 2, 2011 at 9:12 PM, Michael Barton
<mike-launchpad at weirdlooking.com> wrote:
> What I've been playing with is having a manifest that contains hashes
> of (4mb) chunks for the volume's backups.  When a user initiates a new
> backup, dm-snapshot does its thing and gives me a block device.  I
> read and hash chunks from that block device and compare them to the
> manifest, uploading any that differ to Swift, then update the manifest
> with the new backup.

Oh, and I don't know if keeping track of dirty chunks so backups are
less work is worth putting an indirection layer on top of volumes.
It's probably something we can discuss more fully and do some testing
around later.

-- Mike