My system was running well until I tried to upgrade to 4.3.8 - Gluster and
Engine died.
From my perspective now it does seem that content backup to NFS shares over
10GBe is a must as Gluster is fine until it isn’t and when it isn’t you can
lose everything.
I will implement the solution
I understand your concerns and don't have very much personal experience
with geo-replication either, aside from knowing it's recommended in the
RHEV documentation for disaster recovery. I do believe your specific
concern about replicating issues to the geo replica have been considered
and
On February 6, 2020 6:06:18 PM GMT+02:00, Christian Reiss
wrote:
>Hey folks,
>
>Running a 3-way HCI (again (sigh)) on gluster. Now the _inside_ of the
>vms is backup'ed seperatly using bareos on an hourly basis, so files
>are
>present with worst case 59 minutes data loss.
>
>Now, on the
Hey Jamie,
thanks for replying. I was wondering about gluster g-rep, but what if
something that just happened to me (gluster f*ckup) will get replicated
too. At this point (lost 3 HCI clusters due to Gluster) I am not really
trusting this piece of software with my live data *and* my backups.
You should look at the gluster georeplication option, I think it would be
more appropriate for disaster recovery purposes. It is also possible to
export VMs as OVA which can then be reimported back into oVirt. I actually
just wrote an ansible playbook to do this very thing and intend to share my
5 matches
Mail list logo
