About file checkpointing with NetBackup for SQL Server
Use file checkpointing if you need to perform a large backup and want to save completed work in case the operation fails before it completes. When file checkpointing is enabled, the database or filegroup is divided into file sets and backed up as separate units. The following batch file command initiates file checkpointing:
MAXRESTARTSETS integer
The backup operation is split into the number of operations equal to the integer value. If the number of files is less than the integer value, then the number of separate operations is equal to the number of files.
File checkpointing is available for databases and filegroups that are backed up as streams or with the snapshot option. However, the following restrictions exist:
The backup object must contain at least two files.
The recovery model of the database cannot be "simple".
If the snapshot option is used for backup, then the method cannot be Instant Recovery. However, file checkpointing that uses Instant Recovery to a storage unit is supported.
The batch file that you use for a file checkpoint backup can specify only one database or filegroup. You cannot use the
DATABASE $ALLoption.
When you use file checkpointing for backing up a full database, NetBackup for SQL Server automatically splits the database into fileset components. Recovering the database from components requires a restore of the transaction log. NetBackup for SQL Server automatically includes a backup log directive in the generated batch file when you choose file checkpointing from the backup dialog box.