Three schemes exist: forward incremental, forever forward incremental and reverse incremental. The one chosen fixes which files make up a chain and their sequence, and so how heavily and in what way the repository is read and written.
Read more: Veeam Help Center
In the Ultra Transcenders books
Each book explains backup method in context, with comparison tables and the common traps.
Terms in this definition
- forward incremental
A chain beginning with a VBK and followed by VIB increments. Periodic synthetic or active fulls start new, shorter chains.
- forever forward incremental
A chain with one VBK at its start and only VIB increments after it; synthetic or active fulls never occur. When retention is reached, the earliest increment merges into the VBK.
- Deployment modes
The two ways ARM can deploy: Incremental, the default, creates or updates what the template lists and ignores everything else; Complete also removes resource group contents absent from the template.
- SEQUENCE
A schema-bound object that generates values on request via NEXT VALUE FOR without belonging to a table. One can feed several tables, restart, cycle or set aside a block of values; any value drawn inside a transaction that rolls back is gone.
- Repository
A group of images or artefacts in a container registry that share one name and differ by tag. Names can include slash-separated namespaces, but every repository is handled separately.
- CRUD
Shorthand for create, read, update and delete, the four basic things you do with data. Data-plane roles in Azure Cosmos DB, for instance, authorise those operations on items.
Related terms
- backup chain
The set of files a job produces over time, starting with a full backup and followed by incrementals, metadata and other files. Which files appear, and in what order, depends on the backup method chosen.
- LLMNR
A backup method for resolving names on the local subnet when DNS lookups fail. Because replies can be faked, organisations often switch it off through Group Policy.