Simple definition
Forever Forward Incremental is a backup method that creates one initial full backup and then only incremental backups while maintaining retention by merging the oldest restore points.
Technical definition
After the first full backup, each job run writes a new incremental file. When the number of restore points exceeds retention, the oldest changes are merged into the base full and the incremental that is no longer needed is removed.
How it works / role
The method avoids creating new periodic full backups while keeping a controlled chain length. The retention merge, however, generates additional I/O on the backup repository.
What is it used for?
Reduce repeated reads from production after the initial full backup while maintaining a fixed number of restore points in a continuous incremental chain.
Practical example
A policy keeps 14 restore points. After the initial full, one incremental is added each day; when a 15th point is created, the oldest point is merged into the base full.
Common issues
- Repository performance is poor during merge operations
- Heavy chain transformation or storage fragmentation
- Insufficient free space for retention operations
- The method is confused with reverse incremental, synthetic full, or active full
Key takeaway: Forever Forward Incremental reduces repeated production reads, but some of the work is shifted to the repository during retention merges.