Page History
...
The options for each backup type are hidden unless the backup type is selected for the policy. For more information about backup types, see Understand understand backup types.
What types of compression algorithms are available?
...
For more information about backup compression, see How how to choose compression and encryption.
...
If your SQL Server environment requires FIPS compliance , use the AES encryption option. For more information, see Ensure ensure FIPS compliance.
| Warning |
|---|
When you choose to encrypt an archive, you must designate a password. For security reasons, SQL Safe does not store this password. Ensure you remember the password you select. |
...
| Options | Description |
|---|---|
| Verify the integrity of the backup when complete | Performs a data integrity check after the backup is created. SQL Safe verifies the integrity of the data files in the backup set created by this backup. Verifying the backup helps identify potential issues that could occur when restoring these data files. |
| Generate maps | 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 backup 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 ensure the security of your SQL Server database, SQL Safe encrypts the login information. This option is available for full backups only. |
Thread Count | Allows you to specify how many threads you want SQL Safe to use to distribute the backup operation across multiple processors on the target SQL Server computer. Use this setting to optimize backup performance. When the resultant backup file is restored, SQL Safe uses the same thread setting to ensure consistent performance. Select Auto to have SQL Safe determine the optimal thread count for your environment. |
Transaction Log | Removes all completed transactions, inactive entries, from the transaction log after SQL Safe finishes the backup. |
Checksum: Generate | Generates a checksum for the backup file. |
Checksum: Ignore Errors | Ignores any errors from the generated checksum. If checksum errors are encountered , this option indicates that SQL Safe should continue to back up this database. |
Backup: Copy only | Specifies a copy-only backup. This is a copy of the database and cannot be used as part of a restore strategy. It will allow you to take a "snapshot" backup of your database without interferring the LSN (log sequence number) order of your backup strategy. |
Backup: Read-write filegroups | Specifies a partial backup, which includes the primary filegroup and any read-write secondary filegroups. Read-write filegroups are not supported by SQL virtual database. If this option is selected , the Generate metadata option (Generate maps for InstantRestore and SQL virtual database) will be disabled. Additionally, backups created with the read-write filegroups option cannot be used by SQL virtual database to create virtual databases. |