Hello Gail,

Thanks a lot for your reply.

The situation is not often on restart and occur rarely. Please clarify me, if the DB is in state of Restoring, can I recover the DB using command "restore database <Database name> with recovery"? As per my understanding the Slow recovery may be due to DB replication and related log files.

The mirroring requirement is not only for the above situation, rather its what the company want to implement for HA. The 2hr downtime and data loss of 1hr is acceptable in a disaster situation. In case of fail over the apps connection need to be changed manually, so we need it to manual fail over. Regarding the skill I need to make up my myself.. :).

Also Please suggest how it would be if the mirror/secondary DB set up in same server on a separate instance.

Besides this if I set up mirroring / log shipping, in above scenario, i.e. if the DB gone for restoring state, what will happen to mirrored / secondary DB. As the mirrored / secondary DB are always in recovery mode, if I recover the mirrored or Secondary DB and connect to production is it ok? If so what should be the next step, shall I have to create another mirroring / log shipping set up for the new production DB and this cycle goes on?

Sorry for asking too many questions.. Please make me correct If I am asking any silly questions.

Thank you..

Regards

Pradeep