Persistent Volume backup policy in Velero

[pradeepkchaturvedi]

In Velero, there are are multiple Resource filtering options for K8S resource backup and Restore. When it comes to PVs there not enough options. I would like Velero to allow user to define PV backup strategy/policy for their cluster. For example, I want to below mentioned strategy for PVs backup in below priority order

• First, Backup CSI snapshot complaint PV to backup using CSI volume snapshot: There should be additional option to configure copying the Snapshotted volume to BSL. There should be additional option to skip certain volumes based on size or their storage class

• Second, Backup non-CSI complaint PV using Restic: There should be additional option to skip certain volumes based on type or size or their storage class

There be separate option to mention for how many volume snapshot should be retained. There should be options to define skip volume list from backup based on size, type, storage class etc.

There are ways in Velero to achieve this using defaultVolumesToRestic, annotation of pod volume for Restic etc. however these needs manually tracking PVs in the cluster to add annotations. With Velero supporting PVs backup strategy/policy, i would like to remove need to manually annotating Pod volumes for backup.

This would help K8S operators to better plan PV backup with lesser manual interventions.

[blackpiglet]

Hi, @pradeepkchaturvedi.
There are some points need to confirm with you in the above description.

• There be separate option to mention for how many volume snapshot should be retained.: does this mean needing a option for setting a max number of snapshots including in a backup?
• There should be additional option to configure copying the Snapshotted volume to BSL.: need to wait for the uploader function ready before implementing this.
• There should be additional option to skip certain volumes based on type or size or their storage class.: may give lower priority on filtering by volume type: Need a way to skip backup of volumes based on type #5035 (comment)

[reasonerjt]

There are quite a few different requirements involved in this issue.

#5035 has been opened and we will use that issue to track the requirement to enable the user to select what PVs will be included in the backup, which we are actively planning for v1.11.

For other requirements, let's open new issues after they are clarified and we'll triage them in future releases (after v1.11).