Re: Geo replication procedure for DR

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



To be honest, I have never reached that point but I think that if the original volume is too outdated it makes sense to setup a new volume on primary site and run a replication from the DR to primary site and then schedule a cut-over (Read-only DR volume, remove replication, point all clients to main site).

You will need to test the whole scenario on a separate cluster , till the procedure is well established.


Best Regards,
Strahil Nikolov 



On Wednesday, June 7, 2023, 9:13 PM, mabi <mabi@xxxxxxxxxxxxx> wrote:

Dear Strahil,

Thank you for the detailed command. So once you want to switch all traffic to the DR site in case of disaster one should first disable the read-only setting on the secondary volume on the slave site.

What happens after when the master site is back online? What's the procedure there? I had the following question in my previous mail in this regard:

"And once the primary site is back online how do you copy back or sync all data changes done on the secondary volume on the secondary site back to the primary volume on the primary site?"

Best regards,
Mabi

------- Original Message -------
On Wednesday, June 7th, 2023 at 6:52 AM, Strahil Nikolov <hunter86_bg@xxxxxxxxx> wrote:

It's just a setting on the target volume:

gluster volume set <VOL> read-only OFF

Best Regards,
Strahil Nikolov 

On Mon, Jun 5, 2023 at 22:30, mabi
<mabi@xxxxxxxxxxxxx> wrote:
Hello,

I was reading the geo replication documentation here:


and I was wondering how it works when in case of disaster recovery when the primary cluster is down and the the secondary site with the volume needs to be used?

What is the procedure here to make the secondary volume on the secondary site available for read/write?

And once the primary site is back online how do you copy back or sync all data changes done on the secondary volume on the secondary site back to the primary volume on the primary site?

Best regards,
Mabi
________



Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Gluster-users mailing list

________



Community Meeting Calendar:

Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://meet.google.com/cpu-eiue-hvk
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users

[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux