Define backup rules
You’ll create a backup schedule that says what to protect, how often, and how long to keep copies.
Before you start
- Cluster connected with Velero backups available
- At least one backup storage location configured
- Clear list of environments / apps that matter
- Enough space on the backup target
Where to configure
| Scope | Where in the dashboard |
|---|---|
| Entire environment | Backups → expand the environment → Backup schedule |
| Specific app or managed DB | Open the app → Backup tab → Backup schedule |
Retention strategies
Grandfather-Father-Son (recommended)
Enable Grandfather-Father-Son to create three Velero schedules:
| Tier | Default cron | Default keep |
|---|---|---|
| Son (daily) | 0 2 * * * | 7 daily copies |
| Father (weekly) | 0 3 * * 0 | 4 weekly copies |
| Grandfather (monthly) | 0 4 1 * * | 6 monthly copies |
You can change the keep counts; retention TTL is derived from them.
Custom cron
Choose Custom cron to set a single crontab and a flat retention TTL (for example 720h ≈ 30 days). Use this when GFS is more than you need.
Switching strategy replaces the other mode’s schedules for that scope.
Create a schedule
- Open the scope (environment card or app Backup tab).
- Choose Grandfather-Father-Son or Custom cron.
- Pick the storage location.
- Save. Confirm the active schedules appear in the list.
- Optionally run Backup once manually to validate storage and permissions.
Restore from a backup
- Pick a successful backup from the list.
- Start restore and wait for completion.
- Verify apps and databases before pointing users at them.
You’re done when
- Active schedules show for the environment or app.
- A completed backup run shows success.
- Restore options appear for that backup.
If it fails
| Symptom | Fix |
|---|---|
| Cannot save schedule | Add a backup storage location first |
| Backups fail immediately | Check backup target credentials and network |
| Restore missing data | Confirm you backed up the right environment or app |