<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 4 November 2015 at 08:39, Thing <span dir="ltr"><<a href="mailto:thing.thing@gmail.com" target="_blank">thing.thing@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Thanks but, your solution doesnt protect for a single PC hardware failure like a PSU blowing ie giving me real time replication to the 2nd site so I can be back up in minutes. <div class="yj6qo ajU"><div id=":22d" class="ajR" tabindex="0"><img class="ajT" src="//ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif"></div></div></div></blockquote></div><br></div><div class="gmail_extra">ZFS can be configured to replicate every few minutes - whether that is sufficient is dependant on your uptime and data loss requirements.<br><br></div><div class="gmail_extra">If you *must* have realtime redundancy then yes something like gluster or ceph is your only option. Gluster is easier to setup and maintain then ceph. Both of them are a lot more reliable if you have three nodes, two nodes is asking for trouble - split brain etc.<br><br></div><div class="gmail_extra">If you want some throughput estimates then we need more spec's:<br><br></div><div class="gmail_extra">- RAM<br></div><div class="gmail_extra">- CPU<br></div><div class="gmail_extra">- Hard Disks<br></div><div class="gmail_extra">- Network<br></div><div class="gmail_extra">- Overall Config<br></div><div class="gmail_extra"> * Caching<br></div><div class="gmail_extra"> * Bonding<br></div><div class="gmail_extra"> * etc<br><br></div><div class="gmail_extra">- With a std 1GB ethernet, your writes will max out at around 110 MB/s<br></div><div class="gmail_extra">- Same for Reads, unless your VM Host is also your gluster node, in which case your reads will be a bit slower than your underlying file system access times<br></div><div class="gmail_extra"><br clear="all"><br>-- <br><div class="gmail_signature">Lindsay</div>
</div></div>