SQL Backup Master Help

Temporary Backup Folder

 

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 not using 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.

 

Auto-Discovery Options

 

•Skip offline databases - 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 read-only databases - When enabled, discovered user databases that are in the read-only state will be skipped. Requires SQL Server 2008 or later.

•Skip log backups for databases in 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.

•Skip for all transaction log backups - Extends the preceding option to all user databases (not just auto-discovered ones) associated with the backup job.

•Fail backup if no databases are discovered - By default, backup job execution will fail if auto-discovery is enabled and no databases are found.

•Use minimal logging for skipped databases - By default, a separate backup log entry will be created for every database that is skipped (based on the configuration options shown above). Enabling this option will cause a simple summary entry to be logged instead, resulting in fewer log entries.