Migrating VM with RDM into another ESX host in different SAN array
Hi All,
I'm about to do my Exchange Server 2007 DR migration from one SAN array into another new SAN array but without ISL link.
so what should I expect and I do in order to make it working in the new ESXi blades connected to the new array ?
I'm about to do my Exchange Server 2007 DR migration from one SAN array into another new SAN array but without ISL link.
so what should I expect and I do in order to make it working in the new ESXi blades connected to the new array ?
Andrew Hancock (VMware vExpert PRO / EE Fellow/British Beekeeper)
Do you want to keep using an RDM in the new SAN, or change to VMDK?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I Think Cold Migration and Option 3 You Suggested Last The Same
But I Agree That Your Option is Safer !
But I Agree That Your Option is Safer !
No physical move with Option 3! It's a copy/clone.
You cannot rollback, if it all goes wrong with any other option.
You cannot rollback, if it all goes wrong with any other option.
ASKER
Hi,
Do you want to keep using an RDM in the new SAN, or change to VMDK?
I'd like to use 1.5 TB VMDK over VMFS, as I no longer implement Physical RDm for my Exchange Server due CCR working fine, I do not need to use EMC Replication manager to do the SnapView directory checking.
Do you want to keep using an RDM in the new SAN, or change to VMDK?
I'd like to use 1.5 TB VMDK over VMFS, as I no longer implement Physical RDm for my Exchange Server due CCR working fine, I do not need to use EMC Replication manager to do the SnapView directory checking.
ASKER
HancockA,
Using V2V with VMware converter sounds great :-)
the only issues at the moment is that between two SAN array, there is no ISL (Inter Switch Link) in place yet, so sVmotion is not an option.
Hm.. I am thinking to just "re-create" the VM C:\ drive only while the rest of the Database and Transaction log can be recreated again manually using Update-StorageGroupCopy (Exchange DB re-seed).
Using V2V with VMware converter sounds great :-)
the only issues at the moment is that between two SAN array, there is no ISL (Inter Switch Link) in place yet, so sVmotion is not an option.
Hm.. I am thinking to just "re-create" the VM C:\ drive only while the rest of the Database and Transaction log can be recreated again manually using Update-StorageGroupCopy (Exchange DB re-seed).
there is no requirement for a ISL.
Do you have a workstation or server, which can connect to both Hosts (which are connected to the SAN).
V2V copies from one ESX host (connect to old SAN), to the other ESX host (connected to new SAN). Across the network.
Do you have a workstation or server, which can connect to both Hosts (which are connected to the SAN).
V2V copies from one ESX host (connect to old SAN), to the other ESX host (connected to new SAN). Across the network.
ASKER
Do you have a workstation or server, which can connect to both Hosts (which are connected to the SAN).
Yes it is my VCenter VM itself :-)
Yes it is my VCenter VM itself :-)
Okay, so you will be able to complete the V2V from this computer with VMware vCenter Converter Standalone 5.0 installed.
ASKER
Many thanks for the information and solutions provided.
ASKER
So is this the software that you mention "VMware vCenter Converter Standalone 5.0" --> Freeware ?
Yes, follow my Article and Links!