Three SQL Server recovery models: simple, full, bulk-logged recovery model

Tracy King updated on Apr 04, 2019 to Backup Utility | How-to Articles

There are THREE different recovery models of SQL Server, you should select SQL Server recovery model to manage log files and prepare for the SQL recovery in case of disaster. This document is to talk about three SQL Server recovery models: simple, full and bulk-logged. Among all, you should back up your SQL Server database.

This document recommends reliable SQL Server database backup and recovery software: EaseUS Todo Backup Advanced Server.

To learn more about the solution of SQL Server backup and restore.

Basic Information About Log Files

SQL Server database contains at least an MDF data file and a ldf log file. Mdf file contains all the database objects and data, such as the table, stored procedure, and user information. Ldf log file contains all logs in the database. While, you never only count on log files to recover your database, for example, to recover the database to some time-point through the ldf log file and the previous full backup.

What does the log file do?

  • Being physical store position of logs, we can back up the logs from the ldf log file, and recover database using log backup file.
  • SQL Server will read the log from ldf log file every time it launches. It will roll backup affairs not submitted before and roll forward those affairs which have been submitted but not have been written data file to ensure the integrity of affairs.
  • A full backup contains all data of the database, but not including all logs. Full backup only contains all data pages and logs in the tail of the current database.

Activity log means log records of current running affairs. Virtual log means a logic storage unit of the log. SQL Server logically divides ldf log file space into several pieces. Every piece is a virtual log. Log truncation means to delete former log.

Simple Recovery Model

When you choose the simple recovery model, SQL Server maintains only a minimal amount of information in the transaction log. SQL Server truncates the transaction log each time the database reaches a transaction checkpoint, leaving no log entries for disaster recovery purposes.

In databases using the simple recovery model, you may restore full or differential backups only. It is not possible to restore such a database to a given point in time, you may only restore it to the exact time when a full or differential backup occurred. Therefore, you will automatically lose any data modifications made between the time of the most recent full/differential backup and the time of the failure.

Simple Recovery requires the least administration. It is easier to manage than the Full or Bulk-Logged models, but at the expense of higher data loss exposure if a data file is damaged. Simple Recovery is not an appropriate choice for production systems where loss of recent changes is unacceptable. When using Simple Recovery, the backup interval should be long enough to keep the backup overhead from affecting production work, yet short enough to prevent the loss of significant amounts of data.

Advantage: permits high-performance bulk copy operations. Reclaims log space to keep space requirements small.

Disadvantage: changes since the most recent database or differential backup must be redone.

Full Recovery Model

With the full recovery model, SQL Server preserves the transaction log until you back it up. This allows you to design a disaster recovery plan that includes a combination of full and differential database backups in conjunction with transaction log backups.

You have the most flexibility restoring databases using the full recovery model when a database failure happens. In addition to preserving data modifications stored in the transaction log, the full recovery model allows you to restore a database to a specific point in time.

Advantage: no work is lost due to a lost or damaged data file. It can recover to an arbitrary point in time.

Disadvantage: if the log is damaged, changes since the most recent log backup must be redone.

Bulk-logged Recovery Model

The bulk-logged recovery model is a special-purpose model that works in a similar manner to the full recovery model. The only difference is in the way it handles bulk data modification operations. The bulk-logged model records these operations in the transaction log using a technique known as minimal logging. This saves significantly on processing time but prevents you from using the point-in-time restore option.

Advantage: permits high-performance bulk copy operations, minimal log space is used by bulk operations.

Disadvantage: if the log is damaged, or bulk operations occurred since the most recent log backup, changes since that last backup must be redone.

Full Recovery and Bulk-Logged Recovery models provide the greatest protection for data. These models rely on the transaction log to provide full recoverability and to prevent work loss in the broadest range of failure scenarios. The Bulk-Logged model provides higher performance and lower log space consumption for certain large-scale operations.

When you choose different MS SQL Server backup strategies, you will have specific limitations to recover SQL Server backups.

 
 

100% of people found this article helpful.

 

Frequently Asked Questions

What is the difference between Clone and Backup? In what cases should I use Clone?

Clone will copy one disk to another or one partition to another (unallocated space is also supported). Usually, this option is used to upgrade the current disk by creating an identical copy. Backup will generate a .PBD image file containing the selected files or system that can be restored from the .PBD image if needed.

What is the difference between System Backup and Disk Backup?

System Backup will auto-select the system boot related partition(s) as the backup source to make sure the system image can be restored properly. Disk/Partition Backup will allow you to manually select a whole disk or speficy a certain partition as the backup source. You will get the same backup result as System Backup if you manually select the system and boot partitions with the Disk/Partition Backup option.

As a computer newbie, what features should I use to protect my computer?

You can use System Backup to back up the system and boot partitions, use Disk/Partition backup to back up the data partition and add plans to run an automatic backup. If you use the computer frequently or have software that may cause boot failure of the computer, we would suggest you back up the computer every 1 to 2 days. For other situations, you can backup the computer once a week. In addition, you can schedule File Backup to back up the files which are changed frequently.

What kind of storage service should I use to save my backup images?

EaseUS Todo Backup can save backup images to internal disks, external disks, network drives, or free cloud(Google Drive, Dropbox, and OneDrive) and CD/DVD. It is suggested to save the images to the internal/external/network drives to save time as those kinds of disks have a better read-write speed. It is suggested NOT to save the image on the source disk, because once the disk is damaged, all the files on the disk will become unavailable and you will be unable to restore the image.

As a company network administrator, what features should I use to protect our internal computers?

It is recommended that you use the SQL Backup feature to back up your company's SQL server and Exchange Backup feature to back up the Exchange server. In addition, you can execute System Backup to back up the system and boot partitions on every computer and set a plan to execute the backup once a day or twice a week to ensure that the computer can be restored timely when it has boot issues. File Backup feature can be used to back up important user data. If there are a large quantity of computers, you can purchase EaseUS Backup Center to manage the backups on the client computers centrally.

About EaseUS Todo Backup

Be it a file, system, partition, or disk, EaseUS Todo Backup will help you back up or clone the item and provide you with multiple backup plans.