On 02/24/2017 04:44 PM, Eric Blake wrote:
> On 02/24/2017 03:31 PM, John Snow wrote:
>>>
>>> But the Backup Server could instead connect to the NAS directly avoiding
>>> load on the frontent LAN
>>> and the Qemu Node.
>>>
>>
>> In a live backup I don't see how you will be removing QEMU from the d
On 02/26/2017 02:41 PM, Peter Lieven wrote:
> The live-snapshot/live-commit stuff could indeed help in my scenario. If I
> understand correctly this is
> something that already works today, correct? If I have taken a live-snapshot,
> is live-migration and
> stop/start of the VM still possible? Wh
> Am 24.02.2017 um 22:44 schrieb Eric Blake :
>
> On 02/24/2017 03:31 PM, John Snow wrote:
>>>
>>> But the Backup Server could instead connect to the NAS directly avoiding
>>> load on the frontent LAN
>>> and the Qemu Node.
>>>
>>
>> In a live backup I don't see how you will be removing QEMU f
On 02/24/2017 03:31 PM, John Snow wrote:
>>
>> But the Backup Server could instead connect to the NAS directly avoiding
>> load on the frontent LAN
>> and the Qemu Node.
>>
>
> In a live backup I don't see how you will be removing QEMU from the data
> transfer loop. QEMU is the only process that k
On 02/23/2017 09:27 AM, Peter Lieven wrote:
> Am 22.02.2017 um 13:32 schrieb Eric Blake:
>> On 02/22/2017 02:45 AM, Peter Lieven wrote:
A bit outdated now, but:
http://wiki.qemu-project.org/Features/IncrementalBackup
and also a summary I wrote not too far back (PDF):
http
Am 23.02.2017 um 20:34 schrieb John Snow:
>
> On 02/23/2017 09:29 AM, Peter Lieven wrote:
>> Am 22.02.2017 um 22:17 schrieb John Snow:
>>> On 02/22/2017 03:45 AM, Peter Lieven wrote:
Am 21.02.2017 um 22:13 schrieb John Snow:
> On 02/21/2017 07:43 AM, Peter Lieven wrote:
>> Hi,
>>
>
On 02/23/2017 09:29 AM, Peter Lieven wrote:
> Am 22.02.2017 um 22:17 schrieb John Snow:
>>
>> On 02/22/2017 03:45 AM, Peter Lieven wrote:
>>> Am 21.02.2017 um 22:13 schrieb John Snow:
On 02/21/2017 07:43 AM, Peter Lieven wrote:
> Hi,
>
>
> is there anyone ever thought about i
Am 22.02.2017 um 22:17 schrieb John Snow:
On 02/22/2017 03:45 AM, Peter Lieven wrote:
Am 21.02.2017 um 22:13 schrieb John Snow:
On 02/21/2017 07:43 AM, Peter Lieven wrote:
Hi,
is there anyone ever thought about implementing something like VMware
CBT in Qemu?
https://kb.vmware.com/selfserv
Am 22.02.2017 um 13:32 schrieb Eric Blake:
On 02/22/2017 02:45 AM, Peter Lieven wrote:
A bit outdated now, but:
http://wiki.qemu-project.org/Features/IncrementalBackup
and also a summary I wrote not too far back (PDF):
https://drive.google.com/file/d/0B3CFr1TuHydWalVJaEdPaE5PbFE
and I'm sure t
On 02/22/2017 03:45 AM, Peter Lieven wrote:
>
> Am 21.02.2017 um 22:13 schrieb John Snow:
>>
>> On 02/21/2017 07:43 AM, Peter Lieven wrote:
>>> Hi,
>>>
>>>
>>> is there anyone ever thought about implementing something like VMware
>>> CBT in Qemu?
>>>
>>>
>>> https://kb.vmware.com/selfservice/mic
On 02/22/2017 02:45 AM, Peter Lieven wrote:
>> A bit outdated now, but:
>> http://wiki.qemu-project.org/Features/IncrementalBackup
>>
>> and also a summary I wrote not too far back (PDF):
>> https://drive.google.com/file/d/0B3CFr1TuHydWalVJaEdPaE5PbFE
>>
>> and I'm sure the Virtuozzo developers cou
Am 21.02.2017 um 22:13 schrieb John Snow:
>
> On 02/21/2017 07:43 AM, Peter Lieven wrote:
>> Hi,
>>
>>
>> is there anyone ever thought about implementing something like VMware
>> CBT in Qemu?
>>
>>
>> https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=10
On 02/21/2017 07:43 AM, Peter Lieven wrote:
> Hi,
>
>
> is there anyone ever thought about implementing something like VMware
> CBT in Qemu?
>
>
> https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1020128
>
>
>
> Thanks,
> Peter
>
>
A bit out
On 02/21/2017 06:43 AM, Peter Lieven wrote:
> Hi,
>
>
> is there anyone ever thought about implementing something like VMware
> CBT in Qemu?
>
>
> https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1020128
Yes; in fact, the work on persistent dirty b
14 matches
Mail list logo