SQL Backup Master allows you to optionally compress and/or encrypt your database backups before sending them to one or more backup destinations.
Compression method - Choose between Disable (the archive file is created), Zip, and 7-Zip (LZMA) compression methods. When choosing, please keep in mind that the 7-Zip file format will generally provide better compression ratios, but will also usually be significantly slower (and consume more memory). If you don't want compression applied at all, select "Disabled" from the list of options.
In general, we recommend using the Zip compression method unless you have a specific reason for choosing otherwise.
Important: If you elect to disable compression entirely (by seeing the compression method to "disabled"), archive encryption options will no longer be available.
Compression level - Determines the amount of compression applied to database backup files. Higher compression generally occurs at the expense of computational resources.
Encrypt compression backup file - Allows you to encrypt compressed database backup files with AES-256 using the specified password.
Important: If you decide to make use of AES-256 archive encryption, be sure to retain a secure record of your password. The associated database backups cannot be recovered without it.
Limit zip compression to a single CPU core - When enabled, prevents zip format encryption from utilizing multiple cores. Note that this option applies to zip archives only.
Verify checksum immediately after compression - Normally a zip archive's checksum is not verified until extraction. Use this option to verify the archive checksum immediately upon file file addition. This option has the potential to slow compression considerably, and applies to zip archives only.
Use SQL Server native backup compression when available - When enabled, uses SQL Server's native backup compression feature to reduce file system I/O, usually resulting in faster backups. Note that native backup compression is only available in the Standard edition (or better) of SQL Server 2014 and later.