Menu
I'm planning to set up log shipping to a remote site for disaster recovery but I still want to take a nightly full backup so I can copy it to our backup tape and also use it to restore onto our reporting server. Can I do that without breaking the cycle of log backups?
959
No, doing a full backup will not affect the LSN chain so LogShipping will continue to function as needed.
The full backup does not truncate or remove data from the transaction log. Your transaction log file operates kind of independent from the full backup file. When you take full backup and transaction backup both at the same time, the transaction log backups are cleaned only after the full backup completes.
Understand truncating the logA full database backup does not truncate the log. If you don't take regular transaction log backups, the log file continues to grow until it runs out of space. While truncating the log makes the space available for use again, it does not decrease the transaction log file size.
The full backup has to include all the transaction log from the begin LSN of the oldest active transaction at the time the data read portion of the backup ends, until the LSN at which the data read portion ends.
Yes you can. You start the log shipping process from a restore of a full backup, and from then on you only need to restore transaction log backups. You can take as many diffs or full backups as you like and it doesn't affect the LSN and therefore does not interfere with the log shipping process as long as the logs are restored in order.
90
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
