Attaching previously owned storage domain to 4.2 Cluster
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/importstoraged... 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
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 <jtqn42@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-leave@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/
On Wed, May 30, 2018 at 4:59 PM, John Nguyen <jtqn42@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?
Hello John, this is an expected message if your source cluster has been shut in a bad manner. You can import with no problems and then import all VMS. If you want to automate this task, i suggest you to take a look to https://github.com/oVirt/ovirt-ansible-disaster-recovery Luca -- "E' assurdo impiegare gli uomini di intelligenza eccellente per fare calcoli che potrebbero essere affidati a chiunque se si usassero delle macchine" Gottfried Wilhelm von Leibnitz, Filosofo e Matematico (1646-1716) "Internet è la più grande biblioteca del mondo. Ma il problema è che i libri sono tutti sparsi sul pavimento" John Allen Paulos, Matematico (1945-vivente) Luca 'remix_tj' Lorenzetto, http://www.remixtj.net , < lorenzetto.luca@gmail.com>
participants (3)
-
John Nguyen -
Luca 'remix_tj' Lorenzetto -
Maton, Brett