The backup plan that you select for SQL Server manages scheduled backups. You can also perform on-demand backups of a SQL instance or a SQL database.
You can perform the following backups:
-
Block-level backups
-
Differential backups
-
Full backups
-
Full backups, using IntelliSnap
-
IntelliSnap backup copy
-
Transaction log backups
Conversion of Transaction Log Backups to Full Backups
Transaction log backups may be converted to full backups, for various reasons. If a transaction log backup is converted to a full backup, the backup is handled as follows.
The backup operation allows transaction log backups to continue running even though a subset of the databases being backed up requires a full backup. Instead of continuing the transaction log backups for databases that have been converted from a transaction log backup to a full backup, a new differential backup job is started and proceeds with the backup. The full backup which was required for databases that were marked for conversion from a transaction log backup to a full backup are performed as part of the new differential backup job.
For information about the reasons why a transaction log backup is converted to a full backup, see Automatic Conversion of Non-Full Backups into Full Backups.
Related Topics
For a video about VSA App-Aware backup, see How to protect Microsoft SQL using VSA App-Aware backup.