We did a storage migration from a HDS to Huawei Dorado FC Storage.
We did import the new LUNs into the oVirt cluster and setup a new storage 
domain with the new LUNs, then we did a live storage migration of all VMs and 
finally removed the "old" SD and LUNs without disruption.
You could do the oVirt update before or after the storage migration.

rgds,
Arsene

On Wed, 2018-11-14 at 09:09 -0600, Jacob Green wrote:

     I just have a few simple questions, have you migrated a fiber

channel storage domain from one ovirt environment to another? And how

did it go, did it just work aside from having to import all the vms and

configure their settings was it any more difficult than that?


We want to migrate our fiber channel storage with VM's intact from an

oVirt 4.1 environment to a brand new oVirt 4.2 environment.


We are using fiber channel via An HP MSA. I do not for see any issues,

but since we have never done it before, and we do not have spare Fiber

Channel storage to test with, we are just unsure of what the behavior

should be. So just wanted to get some opinions or basic guidance, is

there anything we should watch out for and does it "just work".



--

Jacob Green


Systems Admin


713-300-5690

_______________________________________________

Users mailing list -- [email protected]<mailto:[email protected]>

To unsubscribe send an email to 
[email protected]<mailto:[email protected]>

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/[email protected]/message/R3MO5G4BC3XD4B2QMHPTPK7QEIKY4TZF/

_______________________________________________
Users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]/message/HCNUUEEC33RL4ZP55DBZYDJ4YJNN6Z6W/

Reply via email to