Persistence and backups

Durability on Valkey is a property of the instance's purpose, set at creation:

• Cache instances keep data in memory only. A restart starts empty. This is the honest shape for data you can rebuild — there is nothing to back up.
• Store instances persist to disk and can be backed up. The rest of this page is about them.

How a store persists

A store instance writes both a periodic snapshot and an append-only log of writes to its storage volume. After a restart, the node replays them and comes back with its data — this is what makes a single-tier store viable, and what replicas on the HA and sharded tiers recover from.

You size the volume with the storage setting (in GB, per node, billed per region). Size it comfortably above your memory setting — the snapshot and the append-only log together need room to grow between compactions.

Backups

Store instances can take scheduled backups. They are free — enabled with a toggle, no separate charge:

• Schedule — a cron expression; the default takes one snapshot daily at 02:00.
• Retention — the last seven days of snapshots are kept.
• Scope — each region's copy is backed up independently, like everything else about a multi-region instance.

Backups are snapshots, not a continuous log: the recovery point is your backup interval. There is no point-in-time recovery — with the default daily schedule, a restore returns the instance to some point in the last 24 hours.

Restoring

To restore from a snapshot, raise a support ticket naming the instance and the snapshot date — our team performs the restore for you. Self-service restore from the console is planned.

What deletion means

Deleting an instance deletes its data and its volume. For store instances, backups taken before deletion are the recovery path — which is why the console asks you to confirm, and why noeviction is the store default: the platform never silently discards store data, whether by eviction or by teardown.

Sizing guidance