>> I live migrate the VM's to the node that is staying up, then
>> back
> again when the reboot is complete.
>
> 2 questunes here ,
> - what happen if the reboot is at night(self reboot of the
> server) iv seen it happen
> and nobody there to do the migration ? the all thing breaks ?
You can use
> If i'm not wrong it will be synced once you try to access any
> of the unsynced files, except if the file does not exist on the
> first volume
That is not quite true, if all the modifications were performed from
the mountpoint, then it does not matter which server went down. If
files were remove
Jeff
> I live migrate the VM's to the node that is staying up, then back
again when the reboot is complete.
2 questunes here ,
- what happen if the reboot is at night(self reboot of the server) iv
seen it happen
and nobody there to do the migration ? the all thing breaks ?
- what do you mean migr
Hi,
> But what about if the file is a big image file of xen or kvm
I run replicate across two nodes, upon which I host xen images.
I often reboot one of the nodes while the xen machines are running.
I live migrate the VM's to the node that is staying up, then back
again when the reboot is compl
Hi ,
Thanks for the answare , probebly this is the case and i know the issue
with new files and ls
But what about if the file is a big image file of xen or kvm once
say node 1 reboots node 2 will start to serve xen / kvm images
and will hold a lock on the file indefenetly
so replication back to nod
Hi
If i'm not wrong it will be synced once you try to access any
of the unsynced files, except if the file does not exist on the
first volume
Hi ,
Its my seconds post regarding that , its stange
nobody noticed that if 1 node in replication pair reboots or something
the replication is no longer
Hi ,
Its my seconds post regarding that , its stange
nobody noticed that if 1 node in replication pair reboots or something
the replication is no longer good and not in sync ?
What i mean is :
- Files got updated on the other server does not replicate back to the
other node
while was offline say 1
