RE: QEMU dirty-bitmap

2018-04-23 Thread Grégoire Lamodière
Hi Paul, This is a very good news. I am available for any work / help. Grégoire --- Grégoire Lamodière T/ + 33 6 76 27 03 31 F/ + 33 1 75 43 89 71 -Message d'origine- De : Paul Angus Envoyé : lundi 23 avril 2018 11:37 À : [email protected] Objet : RE: QEMU dirty-b

RE: QEMU dirty-bitmap

2018-04-23 Thread Paul Angus
From: Grégoire Lamodière Sent: 23 April 2018 09:52 To: [email protected] Subject: RE: QEMU dirty-bitmap Hi Simon, Thank you for your feedback. I'll continue working on this. In a more general perspective, this topic is related to backup process integrated into CS. I remember an o

RE: QEMU dirty-bitmap

2018-04-23 Thread Grégoire Lamodière
33 6 76 27 03 31 F/ + 33 1 75 43 89 71 -Message d'origine- De : Simon Weller Envoyé : dimanche 22 avril 2018 19:26 À : users Objet : Re: QEMU dirty-bitmap That looks pretty interesting. I'll read up on it. We've been more focused lately on working on Ceph replication, but

Re: QEMU dirty-bitmap

2018-04-22 Thread Simon Weller
7:15 AM To: users Subject: QEMU dirty-bitmap Dear List, Has anyone tried the dirty-bitmap solution to provide incremental backups on KVM/QEMU based CS clusters ? The solution sounds pretty nice, but instance migration scenarios need additional task to copy the bitmaps. Should we dig this subject and

QEMU dirty-bitmap

2018-04-22 Thread Grégoire Lamodière
Dear List, Has anyone tried the dirty-bitmap solution to provide incremental backups on KVM/QEMU based CS clusters ? The solution sounds pretty nice, but instance migration scenarios need additional task to copy the bitmaps. Should we dig this subject and share, or is there any existing work on