mirror of
https://github.com/vmware-tanzu/velero.git
synced 2026-08-15 11:46:06 +00:00
Steve KrissandNolan Brubaker
411d44a673
* allow individual backup storage locations to be read-only Signed-off-by: Steve Kriss <krisss@vmware.com>
40 lines
1.4 KiB
Markdown
40 lines
1.4 KiB
Markdown
# Disaster recovery
|
|
|
|
*Using Schedules and Read-Only Backup Storage Locations*
|
|
|
|
If you periodically back up your cluster's resources, you are able to return to a previous state in case of some unexpected mishap, such as a service outage. Doing so with Velero looks like the following:
|
|
|
|
1. After you first run the Velero server on your cluster, set up a daily backup (replacing `<SCHEDULE NAME>` in the command as desired):
|
|
|
|
```
|
|
velero schedule create <SCHEDULE NAME> --schedule "0 7 * * *"
|
|
```
|
|
|
|
This creates a Backup object with the name `<SCHEDULE NAME>-<TIMESTAMP>`.
|
|
|
|
1. A disaster happens and you need to recreate your resources.
|
|
|
|
1. Update your backup storage location to read-only mode (this prevents backup objects from being created or deleted in the backup storage location during the restore process):
|
|
|
|
```bash
|
|
kubectl patch backupstoragelocation <STORAGE LOCATION NAME> \
|
|
--namespace velero \
|
|
--type merge \
|
|
--patch '{"spec":{"accessMode":"ReadOnly"}}'
|
|
```
|
|
|
|
1. Create a restore with your most recent Velero Backup:
|
|
|
|
```
|
|
velero restore create --from-backup <SCHEDULE NAME>-<TIMESTAMP>
|
|
```
|
|
|
|
1. When ready, revert your backup storage location to read-write mode:
|
|
|
|
```bash
|
|
kubectl patch backupstoragelocation <STORAGE LOCATION NAME> \
|
|
--namespace velero \
|
|
--type merge \
|
|
--patch '{"spec":{"accessMode":"ReadWrite"}}'
|
|
```
|