We installed standalone sql servers with system dbs at DR.

We created jobs on Prod servers to script logins, permissions, jobs etc and robocopy scripts to the relevent sql servers at DR.

Data and log drives are repliacted to DR real time.

We have created a schedule fo DR now and every 1 months we sync up all releases and changes.

During that time, we ask out storage team to present images at DR servers. Once the replicated drives are available, we attach the dbs and run the latest permissions, jobs scripts.

Middleware team deploy all the releases, QA does spot testing and we declare 'all is well' at teh end of the day feeling good that we have some plan. 🙂

We had some bumpy start with Recovery Point. See my previous message on this thread. Basically, when we get that message questioning integrity, we go contunue going back to previous images until we find the one that works. We communicated to Complianec team at work that even though target is to have no data loss in case of disaster, this situation could cause some data loss - not major since image is taken almost every few seconds.