VMWorld
Up to Discussions in High Availability & Disaster Recovery

This Question is Possibly Answered

1 "correct" answer available (4 pts) 2 "helpful" answers available (2 pts)
1 Replies Last post: Mar 14, 2008 9:29 AM by Dace  
Click to view Roy's profile Candidate
Roy
1 posts since
Oct 19, 2007

Dec 20, 2007 3:51 AM

What about the Vm's IP addresses


The hole thing of disaster recovery is as soon as possible to power on the Vm's in your failover site.

Let's assume that our Ip addresses started with 172.16.x.x and in our failover site with 10.0.x.x. That's the status of network settings over there.

What to do then?

Click to view Dace's profile Candidate
Dace
2 posts since
Sep 19, 2007
1. Mar 14, 2008 9:31 AM in response to: Roy
Re: What about the Vm's IP addresses
High Availability (accomplished with VMotion or "Hot" Migration) does not exist between your production site and your dr site (no interuption of service). HA requires VMs at the source and destination ESX host to share the same networking. HA is designed for within a site.

Disaster Recovery strategies center around using a 3rd party SAN replication tool to replicate LUNs between a SAN at the production site and the DR site.

VMWare is working on a Virtual Center add-on called Site Recovery Manager to manage DR tasks such as presenting replicated LUNs to the ESX Hosts at the DR site in a specific order and to (if nescessary as it is in your case) redo the TCP/IP networking of the VMs automatically.

Basically a VM needs to be moved over while powered off and reconfigured to suite your new networking enviroment prior to turning on. In a non-DR situation this can be accomplished using a Cold Migration, but in a DR situation the VM needs to already be at the DR site on a replicated LUN.

Actions

More Like This