We are planning to create an IT DR site where a copy of the running systems in production would be kept in an online state. The IT DR site is connected over an MPLS link and is accessible from the primary site as though on the same LAN albeit a different subnet and has a windows 2003 domain controller extending the same domain/ forest to the DR site as it is on the primary.
The complexity arises in the following:
We have about 50 member servers with varied applications but base OS are all Windows 2K3 and 2008. Single domain, single forest environment.
We intend to use Vmware's physical to virtual feature in order to take a copy of running servers, create a virtual disk and host it at the DR site in a virtualised environment.
There is a need to keep the virtualised servers running at all times so that Antivirus and patch / updates can be maintained.
How should the FQDN , IPs and DNS names be maintained at the DR site? If we do not attach the DR servers to domain (single DNS environment), how would we perform the bi-annual testing to have a sufficient confidence of invoking DR and maintain our required recovery time objectives?
Has anyone been there and done that?