SQL Backup Master Help

These options are used to configure how database backup files are uploaded and stored.

 

General

 

•Upload each database backup immediately after creation - By default, all backup files are created in one step and subsequently uploaded. Enabling this option will cause backup files to be uploaded immediately after they are created (and optionally encrypted/compressed), thereby reducing temporary backup file storage requirements.

•Store backups for each database in its own subfolder - Use this option to store backups of your databases in their own, separate folders.

•Store backups for each backup type (full, diff, log) in its own subfolder - Similar to the above option, but creates separate subfolders for each backup type.

 

Automatic Cleanup

 

By default, SQL Backup Master will automatically delete old differential and transaction log backup files after each full or differential backup job executes. This is done to conserve storage space.

 

Since each differential backup contains all the data changed since the last full backup, there's generally no need to keep previous differential backup files around.

 

Similarly, transaction log backups are generally only used to restore to some point after the latest full or differential backup.

 

You're also given the option to retain the most recent full, diff, and log backups (for each database being backed up) during file cleanup operations, regardless of the age of said backup. For example, if you configure a backup destination to remove old backup files after 7 days, this option will retain the most recent full, diff, and log backup files even if it's older than that.

 

Important: Be sure that your backup destination has sufficient storage space to accommodate whatever data retention options you choose.

 

Retry Failed Storage Attempts

 

In addition to the backup job retry mechanism available in the Scheduling configuration window, SQL Backup Master can retry failed backup file uploads.

 

This feature affects only the file upload phase of backup job processing, and can help mitigate transient failures (server disconnects, etc.) without re-running the entire backup job.