Managed Valkey Backups
Each Managed Database plan includes automated backups. A new service gets its first backup shortly after it's created, and then one every 12 hours. If you set a backup time through the API with the backup_hour and backup_minute properties (UTC), the service backs up once a day at that time instead. The number of backups the service keeps depends on the plan:
- 2 backups for 1-node plans
- 3 backups for 2-node plans
- 7 backups for 3-node plans
With the default 12-hour schedule, that's up to 24, 36 or 84 hours of backups. With a daily backup time, it's up to 2, 3 or 7 days.
All backups are encrypted and stored separately from the database, so they don't use the cluster's storage capacity.
Backups are taken using RDB snapshots and might cause minor performance degradation. If the backups are not required, you can disable them completely by setting "valkey_persistence" to "off" from the "Properties" tab via the UpCloud Control Panel or API. A service with persistence off has no backups, so it can't be restored. Turning persistence off also deletes the service's existing backups, and the service is empty when it's started again after a shutdown.
Where backups are stored
By design, backups are kept off-site, in another location in the same region as the database. This keeps them available even in the unlikely event that the database's whole location goes down. Databases in Singapore and Chicago are the exception: their backups are stored in the same location as the database.
| Database location | Backups stored in |
|---|---|
| Amsterdam (NL-AMS1) London (UK-LON1) Madrid (ES-MAD1) Warsaw (PL-WAW1) | Frankfurt (DE-FRA1) |
| Frankfurt (DE-FRA1) Helsinki (FI-HEL1) Stockholm (SE-STO1) | Helsinki (FI-HEL2) |
| Copenhagen (DK-CPH1) Helsinki (FI-HEL2) Stavanger (NO-SVG1) | Stockholm (SE-STO1) |
| Chicago (US-CHI1) New York (US-NYC1) San Jose (US-SJO1) | Chicago (US-CHI1) |
| Singapore (SG-SIN1) Sydney (AU-SYD1) | Singapore (SG-SIN1) |
Restore a backup
You can restore any of the stored backups, but not a point in time between them. The restore creates a new service with the data as it was when the backup was taken, and leaves the original as it is. The new service has its own hostname, and it keeps the original's users and passwords, its properties, its allowed IP addresses, its SDN Private Networks and its termination protection setting.
In the Control Panel, the new service is created in the original's location and on the original's plan. Through the API, you can choose another location and plan.
To restore a backup, see How to restore Managed Valkey from a backup.
* Valkey and the Valkey logo are trademarks of LF Projects, LLC. Any rights therein are reserved to LF Projects, LLC. Any use by UpCloud is for referential purposes only and does not indicate any sponsorship, endorsement or affiliation between Valkey and UpCloud.