A group of backups to which an individual retention rule can be applied.
For the Custom backup scheme, the backup sets correspond to the backup methods (Full, Differential, and Incremental).
In all other cases, the backup sets are Monthly, Daily, Weekly, and Hourly.
A differential backup stores changes to the data against the latest full backup. You need access to the corresponding full backup to recover the data from a differential backup.
A self-sufficient backup containing all data chosen for backup. You do not need access to any other backup to recover the data from a full backup.
A backup that stores changes to the data against the latest backup. You need access to other backups to recover data from an incremental backup.
A backup location managed by a storage node.
Physically, managed locations can reside on a network share, SAN, NAS, on a hard drive local to the storage node, or on a tape library locally attached to the storage node. The storage node performs cleanup and validation (if those are included in a backup plan) for each backup stored in the managed location. You can specify additional operations that the storage node will perform (deduplication, encryption).
A new backup format, in which the initial full and subsequent incremental backups are saved to a single .tib file, instead of a chain of files. This format leverages the speed of the incremental backup method, while avoiding its main disadvantage–difficult deletion of outdated backups. The software marks the blocks used by outdated backups as "free" and writes new backups to these blocks. This results in extremely fast cleanup, with minimal resource consumption.
The single-file backup format is not available when backing up to locations that do not support random-access reads and writes, for example, SFTP servers.