We're designing a remote site disaster recovery center and are at the stage of developing a series of tests. An IBM mainframe is at both the main data center and at the remote one. Our mainframe folks want/need to be able to test the same applications on both mainframes and they don't want to change the IP address of the interface that supports those application.
For instance say all the TN3270 clients resolve the hostname IBMA to 192.168.100.12. Well the IBM test folks want 192.168.100.12 to not only be at the main data center, but also at the remote data center - so the clients don't have to change how they point to the applications.
What do other people do who have this requirement?
1. Do they have load balancers that redirect traffic to different backends depending on certain criteria?
2. Is the remote data center isolated from the main production network and accessed remotely by the testers - thereby insuring total separation from the same subnets and IP addresses?
I'm sure this problem has been addressed before and a rock-solid solution is available.