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
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
It's just a setting on the target volume:
gluster volume set read-only OFF
Best Regards,Strahil Nikolov
On Mon, Jun 5, 2023 at 22:30, mabi wrote: Hello,
I was reading the geo replication documentation here:
https://docs.gluster.org/en/main/Administrator-Guide/Geo-Replication/
and I
Hello,
I was reading the geo replication documentation here:
https://docs.gluster.org/en/main/Administrator-Guide/Geo-Replication/
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?
