EMC MirrorView replication, Windows 2003 and HAL / ACPI
Hi,
I'm planning to use EMC's MirrorView to replicate an EMC Clariion CX3-40 LUNs to a remote CX3-20 machine (in the DR site).
The application host is a Windows 2003 server doing boot from SAN from the CX3-40, over Fiber Channel. When needed to start the application host in the DR Site, I plan to connect the remote DR application host to the replicated LUNs (in the CX3-20), using boot from SAN over FC.
The server hardware in the production site and the server in the DR site are not the same (the prod. site is HP DL585 and the DR site is an HP Blade BL460).
The problem I suspect that might happen is that the hardware of the two servers are not equal, so that might cause the Windows 2003 in the DR site not to boot OK, because the ACPI/HAL are differenet.
On the other hand, though the hardware is dissimilar, I'm doing boot from SAN on both the local and the remote site and therefor the boot from SAN process should be similar and Windows on the remote site might overcome other hardware changes (which can be fixed manually after Windows on the DR site starts correctly).
Another option is that the remote application host would be a VM inside an ESX that would be installed on the BL460 machine.
I'd like to know if I should expect a problem in booting up the DR server because of these hardware changes.
I'm planning to use EMC's MirrorView to replicate an EMC Clariion CX3-40 LUNs to a remote CX3-20 machine (in the DR site).
The application host is a Windows 2003 server doing boot from SAN from the CX3-40, over Fiber Channel. When needed to start the application host in the DR Site, I plan to connect the remote DR application host to the replicated LUNs (in the CX3-20), using boot from SAN over FC.
The server hardware in the production site and the server in the DR site are not the same (the prod. site is HP DL585 and the DR site is an HP Blade BL460).
The problem I suspect that might happen is that the hardware of the two servers are not equal, so that might cause the Windows 2003 in the DR site not to boot OK, because the ACPI/HAL are differenet.
On the other hand, though the hardware is dissimilar, I'm doing boot from SAN on both the local and the remote site and therefor the boot from SAN process should be similar and Windows on the remote site might overcome other hardware changes (which can be fixed manually after Windows on the DR site starts correctly).
Another option is that the remote application host would be a VM inside an ESX that would be installed on the BL460 machine.
I'd like to know if I should expect a problem in booting up the DR server because of these hardware changes.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER