SQL Server - Configure Logshipping on database where Mirroring is already configured

While working on a project to configure Log-shipping on couple of Production databases as a Disaster Recovery solution where databases were already part of Mirroring as a High Availability solution, Initially I configure the Log-shipping from Principal database and all was working until database failover happen from Principal to Mirror.

Now, as there was no configuration from Mirrored copy of database so DR site was out of sync from so many days and it was the reason which forces me to configure Logshipping from Mirror copy of databases as well.

I completed this configuration on our production environment and same is working fine as expected so I thought to share this with all who might be interested in doing same.

Steps:

1. Backup share (where all T-Log backup will be placed for Log Shipping) should be a shared location as in my case , I used Witness server and created folder named LogShip as a shared folder and granted appropriate rights to SQL Agent service account

2. Configure Logshipping from Principal copy of database with standard process via T-SQL/ GUI as per your preference

3. Here is the trick: Script out logshipping which you configured from Principal database and run only backup script on Mirror server.

4. Job will be enabled on both but Logshipping will not raise alert if backup is not happening from mirror copy.

Hope this will help ..!!

Brgds,

Chhavinath Mishra  

Database Administrator

Microsoft Certified IT Professional (MCITP
)