Local Backup Strategy on Primary with Transaction Log Shipping Enabled to Secondary DR site

  • I have a scenario where a customer is going to be using Log Shipping to the DR site; however, we need to maintain the normal backup strategy on the current system. (i.e. Nightly Full, Every 6 Hour Differential and Hourly Transaction Log backup)

    I know how to setup Transaction Log Shipping and Fail-over to DR and backup but now the local backup strategy is going to be an issue. I use the https://ola.hallengren.com/ maintenance solution currently.

    So the questions for everyone:

    Is it even possible to do regular backups locally keeping data integrity for your backup strategy with Transaction Log Shipping enabled?

    If not, does anyone have any recommendations?

    Have I overlooked something or is there a better solution?

    Thanks in advance

  • FULL, and DIFFERENTIAL backups do not break the LSN log chain, so you can have Log Shipping and it will be ok.

    Now, it is a horrible idea to keep your full backups locally without replicating or moving those to another server or disk's array. If your local storage goes down or got corrupted, you will loose all your data and backups.

    DR is not a replacement for your regular backups by the way.

  • Just to clarify the local backup files are sent to tape nightly.

    I also agree that DR is not a backup solution. If I had to pick I would always choose Always on Availability Groups.

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply