On Tue, Jun 8, 2021 at 3:38 AM Simon Scott <si...@justconnect.ie> wrote:
> Anyone have any comments please? > > Hi Simon, With the latest version of gluster, when geo-replication is in setup, the slave volume will be set to read-only. Before you could import that storage domain, make sure to disable read-only on the slave volume. # gluster volume set <slave-vol> features.read-only off I do not think the documentation details available upstream. @Ritesh Chikatwar <rchik...@redhat.com> Could you check, whether the documentation is available upstream. Thanks, Satheesaran Sundaramoorthi > On 28 May 2021, at 08:01, Simon Scott <si...@justconnect.ie> wrote: > > > Hi All, > > Does anyone have any further input on this please? > > Kind regards > > Simon... > > On 25 May 2021, at 09:26, Ritesh Chikatwar <rchik...@redhat.com> wrote: > > > Sas, maybe you have have some thoughts on this > > On Tue, May 25, 2021 at 1:19 PM Vojtech Juranek <vjura...@redhat.com> > wrote: > >> (CC Pavel, who recently worked on DR, maybe he will have some thoughts) >> >> On Monday, 24 May 2021 17:56:56 CEST si...@justconnect.ie wrote: >> > Hi All, >> > >> > I have 2 independent Hyperconverged Sites/Data Centers. >> > >> > Site A has a GlusterFS Replica 3 + Arbiter Volume that is Storage Domain >> > data2 >> This Volume is Geo-Replicated to a Replica 3 + Arbiter Volume at >> > Site B called data2_bdt >> > I have simulated a DR event and now want to import the Ge0-Replicated >> volume >> > data2_bdt as a Storage Domain on Site B. Once imported I need to import >> the >> > VMs on this volume to run in Site B. >> >> > The Geo-Replication now works perfectly (thanks Strahil) but I haven't >> been >> > able to import the Storage Domain. >> >> > Please can someone point me in the right direction or documentation on >> how >> > this can be achieved. >> >> > Kind Regards >> > >> > Shimme... >> > _______________________________________________ >> > Users mailing list -- users@ovirt.org >> > To unsubscribe send an email to users-le...@ovirt.org >> > Privacy Statement: https://www.ovirt.org/privacy-policy.html >> > oVirt Code of Conduct: >> > https://www.ovirt.org/community/about/community-guidelines/ List >> Archives: >> > >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/LQCTZS6YTKMME >> > 2EHBXJEGUM2WDNSYXEC/ >> >> _______________________________________________ >> Users mailing list -- users@ovirt.org >> To unsubscribe send an email to users-le...@ovirt.org >> Privacy Statement: https://www.ovirt.org/privacy-policy.html >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/A6J63RH74YKX7OCK5RCR5IQOUDSF7GG7/ >> > _______________________________________________ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/privacy-policy.html > oVirt Code of Conduct: > https://www.ovirt.org/community/about/community-guidelines/ > List Archives: > https://lists.ovirt.org/archives/list/users@ovirt.org/message/JMOT5WWGBCAR7RW7L5H3KY6FDK7STDTH/ > >
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/46G24KFGGYFLQIISZTP5GD2E5UYSNMQP/
