• Last year when we tried to do DR testing first time, it was bad ( see my previous posts ). We learnt our lessons, perfected our methods, RP is working out excellent for DR.

    We now have DR releases followed by regular release. At that time, we present the drive images at DR site. Once the drives are available, we attach the databases, apply permission scripts, add new jobs ( we are not syncing system dbs ). We initialize replication as part of attach script. After taht we follow regular release steps and then testing. We have to watch to make sure that this is done in adequate time before journals get full. Most of the times, we are done well within time. Sometimes with some unknown issue, we detach dbs as journals are almost full, let the sync catch up with prod drives and present drives again at DR and attach dbs again.

    Feels good to have nailed down DR process..

    For the issues we had with integrity, we learnt that we can go back few seconds earlier image if there is an issue. However, it has been going smoothly and dont recall going back to older images ( even within second ) during last several runs.