We were contracted to build a "Hot-Standby" for a company which keep their data in the cloud. The through-put is relatively low. Database availability/accuracy is a matter of life or death. The Principle and secondary are running running SQL Server 2012 Standard Edition and reside in different regions.The secondary needs to be ready to stand in for the principle, seconds after failure and match the principle verbatim. Then after the primary is repaired and back online, the secondary needs to update the primary and switch roles back.
Peer-To-Peer is not applicable because the company will not invest the money in Enterprise edition.
Mirroring is an unlikely option because the two servers have minimal disk space and are not keeping logs.
I've researched all the methods of replication: Transactional, Snapshot, Merging. But have only been able to settle on Transactional with Queue updating. Then I hear that using this method is not advised in a disaster recovery scenario and that logs are required.
I have a theory that I have not tested yet as it would take a large amount of resources 'just to see if it works'. I have not seen the strategy recommended or even mentioned anywhere so I would appreciate if you could offer your opinion on it as well as provide any additional direction apart from it.
Put Distribution, Publisher and a subscriber on both servers and cross chain them, so if the right side failed (principle), the left server would still be able to publish without logs and it would update the right side once it came back online. Then the roles could be switched again after everything was replicated from the left side.
Just to reiterate my problem is the right side going down, the roles switch and the left becomes primary and receives new data. Then the right comes back and changes to the left must be pushed to the right. I can't lose the distributor during this process because of the lack of logging.
Keep in mind I only have two servers. All constructive direction is appreciated.
Additional details The focus would be labeled as HA as opposed to DR. I agree completely that if this is life and death then the client should be made aware that this approach is suboptimal and have made my concerns known. My motivation to bring this to the forums was to seek out a unseen solution, if it existed. (RTO < 1 hour, RPO < 5 mins)