<div dir="ltr"><div class="gmail_quote"><div dir="ltr">On Fri, Dec 8, 2017 at 5:25 PM Max Reitz <<a href="mailto:mreitz@redhat.com">mreitz@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 2017-12-07 23:19, Nir Soffer wrote:<br>
> On Wed, Dec 6, 2017 at 6:02 PM Jason Lelievre <<a href="mailto:jlelievre@folksvfx.com" target="_blank">jlelievre@folksvfx.com</a><br>
> <mailto:<a href="mailto:jlelievre@folksvfx.com" target="_blank">jlelievre@folksvfx.com</a>>> wrote:<br>
><br>
> Hello,<br>
><br>
> What is the best way to set up a daily live snapshot for all VM, and<br>
> have the possibility to recover, for example, a specific VM to a<br>
> specific day?<br>
><br>
><br>
> Each snapshot you create make reads and writes slower, as qemu has to<br>
> lookup data through the entire chain.<br>
><br>
> When we take a snapshot, we create a new file (or block device) and make<br>
> the new file the active layer of the chain.<br>
<br>
I'm not sure how much this is going to slow you down exactly, but I can<br>
tell you that there are also incremental backups to look into.<br>
<br>
(e.g. <a href="https://wiki.qemu.org/Features/IncrementalBackup" rel="noreferrer" target="_blank">https://wiki.qemu.org/Features/IncrementalBackup</a>)<br></blockquote><div><br></div><div>checking, thanks!</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Max<br>
<br>
</blockquote></div></div>