Log shipping is one of methods for high availability/disaster recovery. It works by transferring the transaction logs from primary to the secondary.

Log shipping needs that the database should be either in full recovery mode or bulk logged recovery mode.

My questions is: Since the Bulk logged recovery mode doesn't log the bulk operations, then why is it allowed in log shipping? Doesn't this mean it violates the principle of high availability/disaster recovery because the secondary database will be missing all the data that was added into primary via bulk operations (as these are not written to the transaction log)?


"Bulk logged recovery mode doesn't log the bulk operations" - it's a wrong message. Instead of writing information about adding each row to the log file it writes full pages which were affected by a bulk logged operation to the log backup.

You could read more: Bulk Changed Map (BCM): The Minimally Logged Advantage

  • In particular the reason this works is stated in the linked article: "During a log backup, [affected by a minimally logged operation] are added to the backup in addition to the normal log information." So while it's true that the data isn't written to the log file, it is written to the log backups. – David Browne - Microsoft Oct 9 '18 at 13:25
  • Hello, then why is it that this recovery model doesnt support point in time recovery? – variable Oct 11 '18 at 12:56

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.