It can be tricky to have the same address range across a WAN, in 2 distinct locations.
Will you be recovering ALL your servers in one fell swoop, or possibly just some of them?
Would you then plan to migrate back to the original (or a new) data center, again phased for at once?
Do most things work properly through DNS or WINS, or are there static IP addresses all over system scripts?
Thanks for your reply. Neither of the two possible outcomes would have same IP addresses on a single WAN. We would either have 1) a WAN that had production AND secondary sites for failover when primary site is down, without duplicate IP Addresses, or 2) a WAN for production, and a physically segregated WAN for testing that could mimic production server names and IP addresses.
I keep hearing that we have been following DNS practices but then we run into an instance where there is a IP address imbedded in an application component.
I want the benefit of having a single WAN that all sites can persist on simultaneously, so we can test DR systems on the network we would use at time of disaster, but wish to avoid all the pre-test analysis and preparation that would be required to prevent potential enterprise transaction traffic/file transfers from bleeding from test into production systems.
Does anyone know of any white papers or industry best practices documentation that discusses this issue?