Hello! Nice talk. What about backup system via ploop write tracker?
On Sun, Jun 22, 2014 at 12:21 AM, Kevin Holly <ope...@lists.dedilink.eu> wrote: > Am 16/06/14 12:28, schrieb Aleksandar Ivanisevic: >> Kir Kolyshkin <k...@openvz.org> writes: >> >> [...] >> >>>> >>>> http://openvz.livejournal.com/48634.html >> >> Speaking of ploop send/copy, have you ever thought about a continuous >> ploop send as a way of providing redundancy? In essence, ploop send >> would, instead of exiting and running a suspend command, just keep >> sending the changes to remote, so, in case the primary dies, remote >> instance can be started with the latest image. Something like DRBD does, >> but optimized for an OpenVZ use case. > That would be really cool. Something like the kernel permanently > tracking writes and something doing the live sync when a block changes. > > From what I've read, ploop migration makes the kernel track writes to > the device and then migrate these blocks in the ploop device as > long/often as needed until no blocks change anymore or always the same > blocks change, so that can be also kind of useful in a live sync of the > ploop image. >> >> If you can provide the feature I would be happy to provide the scripting >> around it. >> >> [...] >> >> > > _______________________________________________ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users -- Sincerely yours, Pavel Odintsov _______________________________________________ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
