Options | SQL Safe | SQL Server | Description |
|---|
| Use compression | Not availableAvailable | Available | - You designate the compression rate necessary to match your storage needs.
|
| Encryption | Available | Not available | - Select the level of encryption you need to ensure data security within your environment.
|
| Verify the integrity of the backup when complete | Available | Available | - Verifies the integrity of the backup set data files created by this backup.
- Verifying the backup helps identify potential issues that could occur when restoring these data files.
|
| Generate maps | Available | Not available | - Generates maps containing metadata for each database included in your backup file. This option is selected by default.
- 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 it should 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 tcreation of the virtual database.
- For more information, see recover objects using Virtual Database.
|
| Report T-Log operations that are skipped as SUCCESS | Available | Available | - Allows SQL Safe to report SKIPPED T-Log operations as SUCCESS.
- Avoids backup policies from reporting a warning status when T-Log operations are skipped for databases that are in simple recovery.
|
| Include database logins in backup file | Available | Not available | - 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 | Available | Not available | - 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 | Available | Available | - Removes all completed transactions and inactive entries from the transaction log after SQL Safe finishes the backup.
|
Checksum: Generate | Available | Available | - Generates a checksum for the backup file.
- It must be enabled to allow the Checksum: Ignore Errors availability.
|
Checksum: Ignore Errors | Available | Available | - If the Checksum: Generate option is enabled, then either format is available.
- If checksum errors are encountered, this option determines that SQL Safe should continue to backup process.
|
Backup: Copy only | Available | Available | - Specifies a copy-only backup. This is a copy of the database and cannot be used as part of a restore strategy.
- Allows to take a "snapshot" backup of your database without interfering the LSN (log sequence number) order of your backup strategy.
|
Backup: Read-write filegroups | Available | Available | - Specifies a partial backup, which includes the primary filegroup and any read-write secondary filegroups.
- If this option is selected, the Generate metadata option (Generate maps for InstantRestore and SQL virtual database) will be disabled.
- Backups created with the read-write filegroups option cannot be used by SQL virtual database to create virtual databases.
|