I have a server which is running fine in our primary location and we want to have a secondary location for failsafe reasons.
Are there other options than Active/Passive cluster solution?
What we want is that if the secondary location is activated due to a failure in the primary location and application is working against the secondary location and when primary location is fixed and started again, the application will be run against the primary location. The application will automatically decide which site to work against.
Now to the question, how to get the information stored in the secondary location back to primary location when primary location is started again?
Is the only answer an Active/Passive cluster solution?
What we are thinking about as an alternative is a merge replication.
I am also asking this question on SQLTeam.com