Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
Hello, Personally I'm using option (a) on a 3 node proxmox cluster and drbd9. Replica count per VM is 2 and all 3 nodes act as both drbd control volumes and satellite nodes.I can live migrate VM over all 3 nodes without issues. Snapshots are also possible via drbdmanage + zfs snapshot + clones capability. Option (b) seems more suitable for a 2 node drbd8 cluster in a primary/secondary setup. Haven't tried it so I cannot tell if there are any clurpits. My only concern in such setup would be if drbd corrupts silently the data on the lower level and zfs is not aware of that.Also, if you are *not* going to use live migration, and you can affort loosing some seconds of data on the secondary node in favor of better performance in the primary node, then you could consider using protocol A instead of C for the replication link. Yannis On Fri, 18 Aug 2017 at 15:16, Gionatan Danti <g.danti at assyoma.it> wrote: > Il 18-08-2017 12:58 Julien Escario ha scritto: > > If you design with a signle big ressource, a simple split brain and > > you're screwed. > > > > Julien > > Hi, I plan to use a primary/secondary setup, with manual failover. > In other words, split brain should not be possible at all. > > Thanks. > > -- > Danti Gionatan > Supporto Tecnico > Assyoma S.r.l. - www.assyoma.it > email: g.danti at assyoma.it - info at assyoma.it > GPG public key ID: FF5F32A8 > _______________________________________________ > drbd-user mailing list > drbd-user at lists.linbit.com > http://lists.linbit.com/mailman/listinfo/drbd-user > -- Sent from Gmail Mobile -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20170819/8cdedc16/attachment.htm>