I am trying to create an exact replica of the production network at the DR location. Using replication from host to host, host to vmdk, and back up data, I am replicating the servers and data over. Now I need the same subnet mirrorred along with the server names and domain. Currently the production network and DR site use different subnet addresses separated by a point to point T3 connection.
Applications were not designed with DR in mind. Resources are referenced by name or IP.
Easier to clone DC and specific application systems.
Other systems can be online on the DR subnet and replicating data until the time of disaster, then give DR server the same name and IP address of production system.
Need to be able to bring a server on the mirrored domain online for test without affecting the production network and domain.
Considered L2TPv3, but this doesn't solve my problem of mirroring the systems. I can't bring up 2 mirrored domain controllers or any replicated servers up at the same time.
Thinking of using a router to NAT from DR subnet to the mirrorred production subnet. Adds a lot of complexity and IP mapping conplexity.
Also considering setting up a DMZ on the DR PIX with the production subnet. Allows me to route traffic to the DR subnet and to the Internet. Allows me to filter traffic to avoid name and IP conflicts.
Of course any testing that will be done will require disabling the T3 connection and accessing the DR network from another path such as VPN.
Looking for thoughts, recommendations, previous configurations.
I know the basics for Cisco routers and switches but what I want to know is, if I set up VTP on a switch, is there a way to send it through routers to other switches? This will probably end up more hassle than gain, but it's interesting and cool to p...