Here is my current design:
AD Site 1 (production)
Subnet 10.254.26.0/24
3 GCs
All other servers are Exchange 2013 servers
We are looking to add a second AD site at our disaster recovery location with 3 more GCs and Exchange 2013 DR servers mirroring our production setup.
Our network is a L2 link that spans both datacenters so this vLan is available at the DR location as well. The gateway is an F5 (there are F5s at both datacenters with a shared configuration).
My question is around the creation of the second AD site in AD Sites and Services. My network team is unwilling to provide a separate subnet for us to use in DR (or even to segment this subnet into two) so we were considering breaking the subnet up logically in AD sites and services with half the subnet for the production servers and the other half for the DR servers. Note that the latency is sub 10ms between datacenters.
Are there any reasons to NOT take this approach?
AD Site 1 (production)
Subnet 10.254.26.0/24
3 GCs
All other servers are Exchange 2013 servers
We are looking to add a second AD site at our disaster recovery location with 3 more GCs and Exchange 2013 DR servers mirroring our production setup.
Our network is a L2 link that spans both datacenters so this vLan is available at the DR location as well. The gateway is an F5 (there are F5s at both datacenters with a shared configuration).
My question is around the creation of the second AD site in AD Sites and Services. My network team is unwilling to provide a separate subnet for us to use in DR (or even to segment this subnet into two) so we were considering breaking the subnet up logically in AD sites and services with half the subnet for the production servers and the other half for the DR servers. Note that the latency is sub 10ms between datacenters.
Are there any reasons to NOT take this approach?