Forum Discussion
Hello,
For running active-active setup you have two or more active traffic-groups correct?
Do you have session persistance and such setup for the backend application or how do you plan on handling possible failovers and such for synchronising the backend?
I'd probably solve it by creating a second VS which is attached to traffic-group-2 and which uses the the second application server (presuming you have at least two different application servers) Also you'd probably need a second leg with routes to the internal backendserver which is also part of traffic-group-2. Then i'd probably setup a DNS-record for application.example.com, which points to app1.example.com and app2.example.com where app1 and app2 corresponds to the VS assigned IPs. Then it will resolve in a round robin style towards the servers, but the best option would obviously be by using GSLB for name resolution which will solve DNS-persistance for the clients so that they go towards the same VS.
/Ted