Advanced Backup Options (Data) - SQL Server Agent

You can select advanced backup data options for the operation.

Start Log Backup after Successful Backup

Specifies that a Transaction Log backup will start automatically after a successful Full or Differential backup operation is completed. This is useful when you want to back up logs immediately after a data backup, and allows you to do so without creating two scheduled jobs.

Partial (Excludes read-only Filegroups)

A partial backup resembles a full database backup, but does not contain all the filegroups. Instead, it contains all the data in the primary filegroup, every read/write filegroup, and any optionally-specified read-only files. Partial backups are useful whenever you want to exclude read-only filegroups. A partial backup of a read-only database contains only the primary filegroup.

Tail-log Backup (database is left in restoring state)

This advanced backup option is only available if the Transaction Log option was selected in the Backup Option dialog box. Specifies to back up the tail of the log and to leave the database in the RESTORING state.

SQL Native Backup Compression

SQL Server 2008 Enterprise or later editions of SQL Server specifies that the backup will be compressed by a SQL Server before being backed up. The size of the backup will be smaller than an uncompressed backup of the same data. Typically, compressing a backup will require less device I/O which should increase backup speed significantly. However, CPU usage may increase for compressed backups and you may want to evaluate performance counters. Scheduling the backup during off-peak hours or compressing only low-priority backups may be desirable. When using the SQL Native Backup Compression option, there is no need for deduplication as the data will be compressed with this option and deduplication will not consequently save any more space.

VSS-enabled and SnapProtect backups are not supported backup types for compression.

Copy Only

A copy-only backup is an independent backup and does not affect the usual chaining involved in traditional backups. This type of backup can be performed for a special purpose and does not affect the overall backup and restore procedures. It applies to full backups, full Volume Shadow Services (VSS)-enabled backups, and full SnapProtect backups.

After taking a full copy-only backup, log backups cannot be run unless a traditional full backup is present. Differential backups can be run but they cannot be restored unless a traditional full backup exists prior to the differential.

Perform Snap Integrity Check

Select this option to run integrity check of a hardware snap during an SnapProtect backup. The check verifies the integrity of the captured data files by mounting them to a proxy, attaching and detaching the database to the SQL Server.

Checksum

Select this option to calculate the checksum on a page during backup as it writes to a disk and then calculates the checksum on the page during restore as it reads from disk. Mismatched values returned during the validation are indicative of corrupted database or page corruption on disk.

Continue After Error

Select this option to configure the SQL server to ignore the errors encountered during backups and restores and continue till the job completes.

Create Backup Copy Immediately

Select to create an inline backup copy to start movement of snapshot to media, immediately after the completion of SnapProtect backup job.