On Wed, Feb 20, 2013 at 09:01:16AM +0100, Markus Armbruster wrote:
> Dietmar Maurer writes:
>
> >> > * Backup to a single archive file
> >> > * Backup contain all data to restore VM (full backup)
> >> > * Do not depend on storage type or image format
> >> > * Avoid use of temporary storage
> >> >
Dietmar Maurer writes:
>> > * Backup to a single archive file
>> > * Backup contain all data to restore VM (full backup)
>> > * Do not depend on storage type or image format
>> > * Avoid use of temporary storage
>> > * store sparse images efficiently
>>
>> It is customary to send a 0/6 cover let
First, many thanks for the review!
> It is customary to send a 0/6 cover letter for details like this, rather than
> slamming it into the first patch (git send-email --cover-letter).
> Remember, once it is in git, it is no longer as easy to identify where a
> series
> starts and ends, so the cont
> > * Backup to a single archive file
> > * Backup contain all data to restore VM (full backup)
> > * Do not depend on storage type or image format
> > * Avoid use of temporary storage
> > * store sparse images efficiently
>
> It is customary to send a 0/6 cover letter for details like this, rathe
On 02/19/2013 04:31 AM, Dietmar Maurer wrote:
> This series provides a way to efficiently backup VMs.
>
> * Backup to a single archive file
> * Backup contain all data to restore VM (full backup)
> * Do not depend on storage type or image format
> * Avoid use of temporary storage
> * store sparse
This series provides a way to efficiently backup VMs.
* Backup to a single archive file
* Backup contain all data to restore VM (full backup)
* Do not depend on storage type or image format
* Avoid use of temporary storage
* store sparse images efficiently
The file docs/backup-rfc.txt contains mo
