Customer requirement is he want his intranet server in HQ (http:a kind of internal Web application) should be failover to DR site whenever the power from the HQ is totally shutdown.this means whenever there is a power outage in HQ , branch office's should continue working with their worflow, they shld access the internal web application through DR site,
Also customer need the replication (mirroring) of the main server to DR site whenever the changes are applicable in the server, He needs the database replication from HQ end to DR side,incase of any failure, the database shld be accessible from DR site,
if they are more then 200 km far away synchronous mirroring is not possible (propagation delay becomes too big) and only asynch mirroring can be used.
You can consider async mirroring like backups: at scheduled time intervals DB is sent to DR (may be incrementally)
You need also to clearly specify with customer how handover to DR web application is done:
that is if it is acceptable for use to reconnect to the web application this could be done with routing only (for example by using the same IP address like an anycast) and having the preferred path to HQ from all sites.
if the customer would expect to go on with the web application on DR web server with no interruption this requires additional activity:
the servers have to be configured as a cluster with a management interface (different from front end where user connects) in order to communicate state information to peer (web sessions and other info)
I would say this makes sense only if sync mirroring is possible otherwise there is no use on switching seamlessy to DR web server with a DB that is not in sync with HQ one.
So I would suggest to better define requirements with customer
1) The HQ site is not more than 200 KM the branch offices are far away, so i shld suggest customer synchronous mirroring
2) that is if it is acceptable for use to reconnect to the web application this could be done with routing only (for example by using the same IP address like an anycast) and having the preferred path to HQ from all sites
I hope what i understand from ur above words is a Anycast routing through MPLS cloud hitting to prefered HQ server. If not then to DR ?? correct me ???????????????? How to configure any document??????
3)the servers have to be configured as a cluster with a management interface (different from front end where user connects) in order to communicate state information to peer (web sessions and other info)
I didnt get ur above 3 statement becz i m unaware how server clustering works?? what i only know is clustering is more than 1 server for backup within a LAN, How this will work when 1server is in HQ and the other is DR any keepalive are there between servers, and suppose if there are then how the ISP edge router PE (which is connecting to HQ) will come to know that i have to route the traffic to DR server.
Still the router configs are not clear for me from my end as well as ISP end,i m wondering how the traffic will be routed to DR.
Ip SLA route tracking by the ISP end and i hope the IP of a server shld be virtual.
Thanks for ur reply,
i was expecting u and u replied thanks once again.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...