Documentation for version v1.3.1 is no longer actively maintained. The version you are currently viewing is a static snapshot. For up-to-date documentation, see the latest version.
After you set up the Velero server, try these examples:
Start the sample nginx app:
kubectl apply -f examples/nginx-app/base.yaml
Create a backup:
velero backup create nginx-backup --include-namespaces nginx-example
Simulate a disaster:
kubectl delete namespaces nginx-example
Wait for the namespace to be deleted.
Restore your lost resources:
velero restore create --from-backup nginx-backup
NOTE: For Azure, you must run Kubernetes version 1.7.2 or later to support PV snapshotting of managed disks.
Start the sample nginx app:
kubectl apply -f examples/nginx-app/with-pv.yaml
Create a backup with PV snapshotting:
velero backup create nginx-backup --include-namespaces nginx-example
Simulate a disaster:
kubectl delete namespaces nginx-example
Because the default reclaim policy for dynamically-provisioned PVs is “Delete”, these commands should trigger your cloud provider to delete the disk that backs the PV. Deletion is asynchronous, so this may take some time. Before continuing to the next step, check your cloud provider to confirm that the disk no longer exists.
Restore your lost resources:
velero restore create --from-backup nginx-backup
To help you get started, see the documentation.