Restore

Restore resource #

Restoring from a backup creates an object Restore in the namespace velero. The Velero controller asynchronously applies resources from the selected Backup. Progress and errors are reflected in the status Restore.

The Restore manifest is available on the Manifest tab; after YAML changes, run validation.

After creation, the Restore object is not edited - if necessary, a new one is created. You can delete the Restore resource from the recovery list page, from the view page, or through the manifest.

In the cluster or namespace GUI #

Backup and Restore → Restores → Restore from Backup. The button is active when the current scope has at least one Backup.

Policy for updating existing resources:

More information about the order of applying resources, skipping existing objects and filters is Restore Reference (v1.17) and Reference Information.

Volume restrictions #

PVs that are already mounted into running Pods (Deployment, StatefulSet, Pod) are not restored so as not to disrupt applications.

Recovery hooks #

Velero supports restore hooks (initContainer and exec after the pod starts) to prepare the application after restore. In release 2.14.0, hooks are available only in the restore manifest in the GUI.

Description of annotations and fields spec.hooks - Restore Hooks (v1.17).

Example: Restore (YAML) #

apiVersion: velero.io/v1
kind: Restore
metadata:
  name: restore-my-backup
  namespace: velero
spec:
  backupName: backup-my-namespace
  includedNamespaces:
  - my-app
  restorePVs: true
  existingResourcePolicy: none

• existingResourcePolicy: none - as “Skip”; update - as “Update”.
• restorePVs: restoring PV from a backup (if present in the backup and if there are no conflicts with running volumes).

Import: Import manifests.

Diagnostics: velero restore describe <name> — incl. summary of hooks (Restore Hooks (v1.17)).

Known features of restore on the Kubernetes side (LoadBalancer, admission webhooks) are listed in troubleshooting.