How to sync config to a different data center with a different network topology

Does your cold (or warm) site have the backend resources (pool members, nodes) with the same IP addressing as your production site? Is all of the supporting network infrastructure configured with different IP addressing?

I guess I'm trying to get a scope of exactly what the differences are between your active and standby locations, and what happens during a DR scenario to determine if this config move is feasible.

We live in a very large county and resources can be in several different buildings. While a hurricane can hurt one area pretty bad, other parts will be fine. Plus we have a DR site that's not in our area at all.

In every pool, there are members in the different locations. When everything is fine all LTMs have access to all the members. In the case of a hurricane, we would move the VS IP range to the cold site, which has critical servers at that location as well.

I hope I answered it clearly, but the simple answer is that if I picked up the config from production and placed it at the DR site (minus routing, IPs Subnet, Gateway) The LTM would have access to all pool members in South, North, Central, West county and the DR site. As we started losing buildings due to power and network issues the LTM could keep serving from the members that are available.

Normally what I have done in the past was create a pool for the route that includes an IP from both locally attached subnets on both sides and it works :) one pool member fails on one side and the others fails on the other side/site