If you enable image-level backups for a backup policy, Veeam Backup for Google Cloud creates a new backup file in a backup repository during every backup session. A sequence of backup files created during a set of backup sessions makes up a standard backup chain.
The standard backup chain includes backup files of the following types:
- Full — a full backup file stores a copy of the full instance image.
- Incremental — incremental backup files store incremental changes of the instance image.
To create a standard backup chain for an instance (whether it is a VM instance or a Cloud SQL instance) protected by a backup policy, Veeam Backup for Google Cloud implements the forever forward incremental backup method:
- During the first backup session, Veeam Backup for Google Cloud copies the full instance image and creates a full backup file in the backup repository. The full backup file becomes a starting point in the standard backup chain.
- During subsequent backup sessions, Veeam Backup for Google Cloud copies only those data blocks that have changed since the previous backup session, and stores these data blocks to incremental backup files in the backup repository. The content of each incremental backup file depends on the content of the full backup file and the preceding incremental backup files in the standard backup chain.
Full and incremental backup files act as restore points for backed-up instances that let you roll back instance data to the necessary state. To recover an instance to a specific point in time, the chain of backup files created for the instance must contain a full backup file and a set of incremental backup files dependent on the full backup file.
If some file in the standard backup chain is missing, you will not be able to roll back to the necessary state. For this reason, you must not delete individual backup files from the backup repository manually. Instead, you must specify retention policy settings that will let you maintain the necessary number of backup files in the backup repository. For more information, see Retention Policy for Backups.