Currently they have a single SQL 2000 Std install on a server that needs to be retired. They run an app in terminal services to manipulate the data.
So I'm looking at two new servers with SQL 2008 (Workgroup I hope..) one on site, one off connecting via an IPsec tunnell. The connection is not in place yet. Each server will run terminal services and the locally installed app will be setup to use it's local SQL instance.
So someone can log on to Server1 via TS and access the primary SQL server. Or log on to Server2 via TS and access the backup SQL server. They simply launch the app same as they always do.
So I need to keep server2 up to date so server1 can blow up and I just need to tell the users to connect to Server2. Then they can go on with their day.
When server1 was repaired I would bring it online probably manually verify the changes from server2 came across. And move everyone back over to 1 again.
Well in a perfect world that would happen lol How close can I get?
While I do need 2-way synch it's not an everyday thing and changes should generally be limited to one side a time plus the user base is small.
I'm not a SQL expert, so I really want to avoid an massively complex process everytime we have to cut back and forth.