In general ever since 3.5 you don't need a export domain to do this.
It is advised you use import storage domain feature to do the same thing.
You create a new storage domain move VM to it and then remove it and attach
it to the new engine.
This should be much faster than the export domain.
Yaniv
On Mon, 14 Nov 2016 19:42:46 + Daniel wrote:
BD> An “export domain” is made for just this purpose. Create a NFS (version 3)
share and make it accessible to the hypervisors for each engine. (It should be
a dedicated NFS share, not used for anything else.) As I recall it should be
owned by vds
hristophe TREFOIS"
>
> To:
> "Beckman Daniel" , "users"
> Cc:
>
> Sent:
> Mon, 14 Nov 2016 20:10:16 +
> Subject:
> Re: [ovirt-users] Move a VM between 2 setups
>
>
> Hi Daniel,
>
>
>
>
> Fantastic in
; engines" is a bit
confusing...
- Original Message -
From:
"Christophe TREFOIS"
To:
"Beckman Daniel" , "users"
Cc:
Sent:
Mon, 14 Nov 2016 20:10:16 +0000
Subject:
Re: [ovirt-users] Move a VM between 2 setups
Hi Daniel,
...@ingramcontent.com]
Sent: lundi 14 novembre 2016 20:43
To: Christophe TREFOIS ; users
Subject: Re: [ovirt-users] Move a VM between 2 setups
Hi Christophe,
An “export domain” is made for just this purpose. Create a NFS (version 3)
share and make it accessible to the hypervisors for each engine. (It should
:14 AM
To: users
Subject: [ovirt-users] Move a VM between 2 setups
Hi,
We have a setup where we want to deploy 2 engines as the network between 2
buildings is unreliable.
With 2 engines, we then want to be able to move VMs (one time) from current
engine where they are running to new engine in
Hi,
We have a setup where we want to deploy 2 engines as the network between 2
buildings is unreliable.
With 2 engines, we then want to be able to move VMs (one time) from current
engine where they are running to new engine in the other building.
Is there a recommended workflow for doing this?
7 matches
Mail list logo
