Page History
...
For more information about backup compression, see How how to choose compression and encryption.
...
- None.
- AES (128-bit).
- AES (256-bit).
If your SQL Server environment requires FIPS compliance, use the AES encryption option. For more information, see Ensure ensure FIPS compliance.
Does encryption require a password?
...
| Options | Description |
|---|---|
| Number of threads | Allows you to specify how many threads you want SQL Safe to use to distribute the backup operation for compression across multiple processors on the target SQL Server computer. Use this setting to optimize backup performance. Select Auto to have SQL Safe determine the optimal thread count for your environment. |
| Remove inactive transaction log entries | Removes all completed transactions from the transaction log after SQL Safe finishes the backup. This option is only available for Log backups. |
| Generate maps (for InstantRestore and SQL virtual database) | Generates maps containing metadata for each database included in your backup file. Depending on the number of transactions completed since your last backup, generating maps may impact the performance of the backup operation. Generating maps is optional but must exist in the backup file for InstantRestore to accept and restore that file. SQL virtual database can attach SQL Safe files without the metadata, but the data files improve SQL VDB performance during creation of the virtual database. For more information, see Recover recover objects using SQL virtual database. This option is selected by default. |
| Include database logins in backup file | Copies SQL login information for the selected databases, including credentials and privileges, when the backup files are written. To help you ensure the security of your SQL Server database, SQL Safe encrypts the login information. This option is available for full backups only. |
...
After configuring the options for your backup, go to Configuring Notificationsconfiguring notifications.