SQL Backup Master uses this folder to store all transient database backups before they are uploaded to their final backup destination(s). By default, SQL Backup Master will use the local Windows temp folder for this setting.
One reason you may wish to change this setting is to support remote backups, in which case you will likely need to configure it with a shared UNC path. For more information, see the remote backups help topic.
Also please note that SQL Backup master compresses database files contained within this folder. If you find that the compression of large database files is creating too much local file system I/O, you may wish to consider mapping the temporary backup folder to another drive (e.g. a different local drive on a separate I/O channel, an external drive, a network drive, etc.).
Important: We recommend against the use of mapped network drives when choosing a temporary backup folder. Instead, consider using UNC paths in the form of "\\server\share" (without the quotes).
You can also click the Advanced button to configured advanced temp folder settings.
If you're having trouble with some aspect of your temporary backup folder, please see the troubleshooting section of this guide.
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.
•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.
•Skip auto-discovered user databases that are in the OFFLINE state - When enabled, discovered user databases that are offline are skipped (and a warning message logged). This feature is applied only to databases discovered by use of the Back up all non-system databases backup job option.
•Skip auto-discovered user databases that are read-only - When enabled, discovered user databases that are in the read-only state will be skipped. Requires SQL Server 2008 or later.
•Skip transaction log backups for auto-discovered user databases using the SIMPLE recovery model - When enabled, discovered user databases using the SIMPLE recovery model will be skipped (and a warning message logged). This feature is applied only to databases discovered by use of the Back up all non-system databases backup job option.
•If no qualified databases are found by auto-discovery, consider the backup failed - By default, backup job execution will fail if auto-discovery is enabled and no databases are found.