You can select advanced options for the backup operation.
Start Log Backup After Successful Backup
Starts the transaction log backup automatically after a successful full or differential backup operation is completed. Enable this option when you want to back up logs immediately after a data backup without creating two scheduled jobs.
Copy Only
Applies to full backups, full Volume Shadow Services (VSS)-enabled backups, and full IntelliSnap backups. Creates an independent backup that does not affect the usual chaining involved in traditional backups. Does not affect the overall backup and restore procedures.
After taking a full copy-only backup, you cannot run log backups unless a traditional full backup is present. You can run differential backups; however, you cannot restore them unless a traditional full backup exists prior to the differential.
Perform Snap Integrity Check
Run an integrity check on a hardware snap during an IntelliSnap backup. The check verifies the integrity of the captured data files by mounting them to a proxy and attaching and detaching the database to the SQL Server.
Allow differential backup for read-only databases
The software makes the check box available when you perform a differential backup. Select this check box to allow differential backups on read-only databases.
This check box does not apply to IntelliSnap or block-level backups.
Partial (Excludes read-only Filegroups)
If you want to exclude read-only filegroups from the backed up data, run a partial backup job.
A partial backup contains data in the primary filegroup, read-and-write filegroup and any optionally-specified read-only files. Partial backup of a read-only database contains only the primary filegroup.
Tail Log Backup (on a Damaged Database)
Available only for a transaction log backup.
Backs up tail of the log to capture the log records that have not yet been backed up. A tail log backup recovers a database to the point-of-failure. If you do not select this option, you can recover a database only to the end of the last backup that was created before the failure.
For example, if a database was damaged or a data file was deleted, start a tail log backup before attempting a file or filegroup restore operation. After the log tail is backed up, the database is left in the RESTORING state.
Before starting the tail log backup, verify that the SQL Server database is set to a full or a bulk-logged recovery model.
SQL Native Backup Compression
Specifies that the SQL Server compresses the backup before the database is backed up by Commvault.
You may want to schedule the backup during off-peak hours or compress only low-priority backups.
Notes:
-
SQL Server 2008 Enterprise or later supports backup compression.
-
VSS-enabled and IntelliSnap backups are not supported.
-
Use a non-deduplicated storage policy with software compression to back up the transaction logs.
-
Do not use Native SQL backup compression when using deduplication. To improve the SQL backup performance with deduplication, ensure that the Native SQL backup compression option is disabled.
Checksum
Runs checksum validation during a backup operation to identify corrupt databases. Mismatched values returned during checksum validation indicate a corrupt database or page corruption on disk.
Continue After Error
Ignores errors encountered during a backup operation and completes the job. By default, a backup job fails if the SQL Server encounters an error during a backup operation.