I have a few entire infrastructures on esx, exchange, dc's, sql etc . Even had one of the esx boxes die (no vmotion at the time) and was able to copy it over and restart it all without error.
You don't need to push the vm's you could do realtime replication or snapshot replication depending on your requirements. In house can be done with some free apps, or inexpensively with datacore for those not faint of heart :) -----Original Message----- From: Kurt Buff [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 30, 2008 2:11 PM To: NT System Admin Issues Subject: Re: VMWARE ESX QUESTION On Jan 30, 2008 6:12 AM, Ziots, Edward <[EMAIL PROTECTED]> wrote: > > Yep, > > We are pushing that at our organization, its easier to set 3+ ESX servers at > a Hotsite, setup a B2B VPN and push the VM's down to the offsite, or have > the hotsite as a Lag site for AD ( say 2-3 DC"s about 12 hr replication > apart, in case main site gets hit, we have DCs/DNS/WINS/ that can take over > at offsite cease the roles and only be 12 hrs behind in changes from main > site) ( Use ESX Ranger, etc etc) Why the lag? > I have done WINS/DNS/WEB/SQL/Apps on VM's without issues, but not DC's. I > wouldn't P2V a DC but I would say its probable that you can spin up a DC > from VM via DCPromo without issues. It's not merely probable - I've done it. However, I was cautioned that the holder of the FSMO roles shouldn't be virtualized. Can't remember why at the moment - something to do with Exchange, IIRC - but that's why one of our DCs is not on ESX. Kurt ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
