Hi guys
We are busy with a project to set up our websites in 2 geographically seperate datacenters. We are doing this for redundancy purposes so that we can have business continuity should the primary data centre be unavailable for any reason.We are going to be using a device called Radware to direct traffic to the seconday site should the primary not be available. Our web applications are based on .NET principles and we will be using a SQL database where some of the data is housed to build ASP pages and related. We may also use this for other application specific data (ie. not client data, yet). The client’s data is stored on several databases on site and we will have WAN links connecting our building (and thereby the backend databases) to the datacentres.
The question is, what are the best practises for maintaining some sort of synchronisation of the data sitting on the SQL databases at the 2 datacentres? I don;t want to limit you guys to SQL so if there is a better product to skin this cat please let me know.
I have been told that MS SQL synchronisation works fine as long as you are not accessing the secondary SQL database in any way. Is this correct? In our model it is quite possible that we could cutover to the secondary datacentre while the synchronisation is still happening.
There is a lot of information I have not included here because I don;t want to bore you with irrelevant stuff but if you need more I’m happy to deliver.
Thanks
dave