Restore

Restore process is triggered by Velero CLI command or by Velero Restore K8s custom resource object (Velero Docs - Restore API Type).

Velero by default never updates or replaces existing objects and existing objects are skipped.

Example of restoration process via Velero CLI command:

velero restore create --from-backup nameOfBackup

Example of restoration process via Restore K8s custom resource object:

apiVersion: velero.io/v1
kind: Restore
metadata:
  name: uniqueNameOfRestore
  namespace: veleroInstalledNamespace
spec:
  backupName: nameOfBackup
  includedNamespaces:
  - restoredNamespace

Restore of volume with file system backup

Restore of volume requires extra steps to be done before the start of the restoration process.

To be able to restore volume with file system backup Velero requires deleting other K8s objects.

When backup of volume was part of K8s Deployment object there was a need to delete Deployment and Pod and PersistenceVolumeClaim and PersistenceVolume related to restored volume.

When backup of volume was part of K8s Statefulset object there is need to delete Statefulset and Pod and PersistenceVolumeClaim and PersistenceVolume related to restored volume.

After removal of needed objects other steps are the same as a typical restoration process.

Restore hooks

Restore with restore hooks (Velero Docs - Restore Hooks) is similar to the backup hooks.

Restore process usually is more complex than backup in terms of restore specific command than need to adjust for specific needs (like restore only specific data table) and error handling if something goes wrong and because of that automated process with restore hooks is not always the best choice to do so. Simpler approach is just to commit to repository commented out examples of restore hooks and treat them as one of possible options, not a universal solution to solve all problems.