Hello Team,
I have design question on transactional replication with one publisher and 5 subscribers ( sql server standard 2014). replicating entire database for horizontal scaling.Publication size is more than 3 TB. We setup push replication with initialize with backup method.
During time of disaster recovery, whats the quick way to restore application when we publisher is crashed. Is there any quick way to promote one of the subscriber as master and re-configure replication.
Possible known options
1) Break replication, configure publication on one of the subscriber and re-configure replication with backup restore method
Drawback :- It takes 30 hrs to re-configure ( backup and restore)
2) save replication meta data, add subscriptions with @sync_type = N'replication support only'
Drawback :- If there is any latency between nodes before we breaking replication, then there could be data conflict issues
Thanks in advance,
Regards,
Chaitanya Konduri