SQL Backup compression and encryption
SQL Backup Master allows you to optionally compress and/or encrypt your database backups before sending them to one or more backup destinations.
Backup File Compression
Compression method - Choose between Disabled (no 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.
Compression & Encryption
Compression level - Determines the amount of compression applied to database backup files. Higher compression generally occurs at the expense of computational resources.
Encrypt compressed backup file - Allows you to encrypt compressed database backup files with AES-256 using the specified password.
Advanced Options
Limit compression to a single CPU core - When enabled, prevents compression from utilizing multiple cores. Use of this option will decrease compression performance while also reducing overall CPU load.
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 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 available in the Standard edition (or better) of SQL Server 2014 and later. This option will be ignored for versions of SQL Server that do not support it.