cstrabley Conceptually, this process is a perfect fit. In practice, everything appears to be working except for the last step. The 'DataMirror' is stuck in restoring mode. Is this what should happen? The dbDataMirror database indicates the bak was verified and applied, then the subsequent trn files. The job fires off every set interval. Why would the destination db still be restoring?
Chris,
Did you ever figure out what was happening with that last step?
I am about to implement this solution for a warm backup of our production database. Also - what interval is appropriate to run the big job on the backup server? Ideally - I wouldn't want to be more than 15 minutes behind the actual production box if we had to cut over to the warm backup...so is this realistic:
1. Full backup at the top of each hour
2. Trans log backup every 15 minutes
3. Run complete restore job (Step 3 script) at like :50 minute mark each hour
Or am I misunderstanding this script? Can I set it to run every 16 minutes so it just restores each new transaction log to the already "ready" database.
A bit confused...any help would be appreciated.
Cheers!
Bruce