PVC Backup Flow

The plugin has the ability to incorporate multiple pathways in order to enhance reader comprehension. They are:

Pod annotations:
- If the parameter pvcdata is defined in fileset and a pod has bacula annotations referencing to pvc backup, these pvcs in the pod annotations will be backed up, even if they are not defined in pvcdata parameter.
- The plugin looks for all the pods in the namespace specified in the fileset, if they have pod annotation, the plugin includes the persistent volumes in pod annotation with their respective backup_mode.
- If a pvc is defined in a pod annotation, the plugin will use the backup mode specified in the pod annotation.
- If pvcdata* parameter is defined in fileset without any pvc specified, the plugin will perform backup of all pvc inside the defined namespaces.
- If a persistent volume is included in both pod annotation and the FileSet pvcdata option, the pod annotation takes precedence over the FileSet pvcdata option.
Backup mode:
- By default, the backup mode is snapshot.
- The priority of the backup mode defined in the pod annotation takes precedence over the backup mode defined in the fileset. This priority is applicable only to the persistent volume claim (PVC) that is annotated in the pod.
- In case that the pvc is not compatible with snapshot, the plugin will try to perform the backup with clone mode.
- If the pvc clone does not have any data (the backup result of the pvc clone is empty), the plugin will attempt to perform the backup using the standard mode, as long as the pvc is not compatible with the clone.
- The best option to get consistent data is the snapshot mode.

From Bacula Enterprise version 16.0.14, the plugin does not perform a backup of pvc data when they are in Pending state.