Get your network guys involved. You're going to need some server clustering and failover servers for the middle and data tiers. You'll also need a secondary telecom provider so that the links between the sites stay up.


>Hello all,
>
>Firstly, I'd like to say that this a VB/SQL Server app but I have great respect for the people of this community and would like your views on this. Also, I think this is more a design discussion than a tools discussion. So, here it goes.
>
>We have developped an app that runs 24/7. It is being use remotly from 3 different sites and also from HQ (although HQ uses it only for managerial purposes and is 9 to 5). The app is VB6/SQL Server.
>
>Everything (front, middle and data tier) is on the network. Lately, we were told that the app is now tagged critical and that we should find a way that operations of the 3 remotes sites run at all times without any down times (except those planned for maintenance, if necessary).
>
>We have looked into data replication and other solutions. But I'm not at all familiar with this kind of setup.
>
>Any insight, ideas and comments are welcome.
>
>TIA.