I've not needed to do it with production data. But when I trash my testlab hosted engine I regularly re-import the existing vm (not hosted engine) storage domain. Not had many issues with the process.
That said, I've only done it with all vm's being down and physical hosts rebooted to ensure that no VM is active on the 'old' storage area. On 30 May 2018 at 15:59, John Nguyen <jtq...@gmail.com> wrote: > Hi Guys, > > I'm working through a disaster recovery of a failed cluster. And I found > the documentation for attaching the old storage domain as an import domain > to a new Cluster. Both clusters are 4.2. > > https://ovirt.org/develop/release-management/features/ > storage/importstoragedomain/ > > The documentation is referencing 3.5 and I would like to know if its still > applies to the 4.2 release. > > When I try to do the import I see warnings below: > > > > I know that its really hard to say this operation may not be destructive. > But is the general work flow outlined in the 3.5 documentation still valid? > > Thanks, > John > > _______________________________________________ > Users mailing list -- users@ovirt.org > To unsubscribe send an email to users-le...@ovirt.org > Privacy Statement: https://www.ovirt.org/site/privacy-policy/ > oVirt Code of Conduct: https://www.ovirt.org/community/about/community- > guidelines/ > List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/ > message/GRFF63P6ORZKGGH734EJT5Y53W3PB36P/ > >
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/PTETMNEPFLBMTBKN6NWG72QL3UNYLYEQ/