Show/Hide Toolbars

SQL Backup Master Help

Navigation: Backups

Backup types

Scroll Prev Top Next More

SQL Backup Master supports three distinct database backup types:

 

Full

 

Creates a full backup of the target database(s).

 

Recovering a full database backup will restore all data captured during the full backup process.

 

Full database backups have the benefit of being simple to understand and restore. However, the database backup files tend to be larger because they represent the entirety of the database at the point of backup.

 

Differential

 

Creates a backup file containing only the database information that changed since the last full backup.

 

Recovering a differential database backup involves first restoring the latest full backup, followed by the latest differential backup.

 

Differential database backups have the benefit of using less storage space while keeping the data backed up current. Differential database backups also execute and upload more quickly than full backups.

 

Important: By default, SQL Backup Master will remove old differential backup files whenever a full or differential backup job executes. You can change this default behavior in the general job settings.

 

Transaction Log

 

Creates a backup file containing transaction logs.

 

Recovering a transaction log backup involves first restoring the latest full backup, followed by the latest incremental backup, and then restoring each transaction log backup since.

 

Transaction log backups are considerably more granular than other backup types, and have the benefit of allowing for point-in-time recovery (although this concept isn't supported directly by SQL Backup Master, it can be done via SQL Server administrative tools).

 

Important: By default, SQL Backup Master will remove old transaction log backup files whenever a full or differential backup job executes. You can change this default behavior in the general job settings.

 

Important: Any databases making use of transaction log backups must have their recovery model set to FULL or BULK-LOGGED. When a database's recovery model is set to FULL or BULK-LOGGED, you must back up transaction logs regularly in order to prevent them from becoming too large.