Hello,
I am using SQL 2012 SE and I have transaction replication setup with publisher, subscriber and distributor in one server in an Active Passive cluster environment.
If publisher goes down then I will have to rely on my full backup+all txlog backups and restart the entire replication.
If subscriber goes down then I will still have to restart the entire replication. The problem is replication is taking between 4 to 6 hours in our scenario and we want to avoid this down time. In the event of publisher/subscriber database goes down what is the best way to have applications/users connected to our database and still perform normal operations without me restoring backups and setting up replication?
Experts need your valuable design thoughts.
Thanks a ton.