Loading...

Automatic Conversion of Non-Full Backups into Full Backups

A non-full backup is automatically converted to a full backup in the following situations:
  • First backup operation of a subclient.
  • Backup operation run after promoting a secondary storage policy copy that is not synchronized with a primary copy for all the subclients of a storage policy.
  • Backup operation run after a backup job of the recent backup cycle was pruned or disabled from a primary copy.
  • First backup operation run after switching from a SnapProtect backup to a traditional backup or vice-versa.
  • First backup operation run after a CommCell migration operation.
  • Backup operation run on databases after the following restore jobs were run on those databases:
    • Point in time restore
    • Transaction mark restore
    • Partial or Piecemeal restore
  • Backup operation run on a database after switching the recovery model for that database from simple to either full or bulk-logged.
  • Transaction log backup is converted to a full backup if a broken chain was detected during the previous transaction log backup operation.
  • Transaction log backup is converted to a full backup for a database that already performed the transaction log backup before it received a suspension request.