I recently inherited a system on SQL 2005 that was using Log Shipping to sync data to a secondary data center. I am not sure why they decided to use Logs rather than Mirroring, but after a bit of digging I found no reason not to update the system to use mirroring, which is a much easier system to manage and in my experience much more efficient.
It occurred to me though, that I wasn’t sure if I would have to completely re-initialize the database on the secondary once I turned Log Shipping off, after all, it would be up to date from a log backup point of time, but the database would be in Stand By / Read only mode once I switched the log shipping off. Happily I found that I did not have to ship a full backup down and start from scratch, following the steps below I could switch from Log shipping to Mirroring in a couple of minutes:
- Disable Backup Job in Log Shipping configuration.
- Make sure the latest logs had been copied and applied to our secondary to bring it up to date.
- Turn off Log Shipping at the principal under Database Properties.
- Restore the database on the secondary using the command: RESTORE DATABASE [DBName] WITH NORECOVERY;
- Enable Mirroring at the Principal using the wizard or scripts.
- Configure New Log Backup schedule.
The last part is important, previous to the configuration change the logs were backed up by your Log Shipping Configuration. Once this was deleted you are without log backups.