Jump toSuggest an edit

Ensuring data persistence

Reviewed on 15 April 2024

Data persistence ensures that the data from your applications is saved, in memory or on a disk, even when there are no ongoing sessions where the data is treated. The method used to preserve data between sessions and avoid data loss varies depending on the compute resource you use to treat your data. It also depends on the way your data is stored.

When data is stored in memory, and no data persistence strategy is put in place, the data will be gone any time the compute process is stopped.

To avoid this, Redis™ natively supports persistence by performing snapshots.

This feature is supported and managed by Scaleway with Managed Databases for Redis™.

Furthermore, you can leverage the cluster mode to ensure the durability of your data.


Scaleway Managed Database for Redis™ is currently best suited for caching use cases. The data persistence mechanism presented on this page do not guarantee data recovery in case of incident.


Snapshots are available by default with a fixed configuration.

When you create a new Redis™ Database Instance, a Redis™ snapshot is also automatically created within specified intervals. These are:

  • 900 seconds if one key has been updated
  • 300 seconds if 10 keys have been updated
  • 60 seconds if 10 000 keys have been updated

The snapshot configuration is managed by Scaleway and cannot be edited. If you feel this configuration does not represent your use case, please let us know via the #databases channel of the Scaleway Slack community.

Cluster mode

If you want to benefit from fault-tolerant architecture in some use cases, we recommend you deploy Redis™ in cluster mode, where each primary node is deployed with a replica node.

A Redis cluster contains a minimum of three nodes and up to six nodes. Each node contains a source and a replica. The cluster nodes use hash partitioning to split the keyspace into key slots. Each replica copies the data of a specific source and can be reassigned to replicate another source or be elected as a source node if needed. This is recommended for scaling as the operation is spread across multiple nodes instead of having a single entry point.

High Availability

The Scaleway Managed Databases team is currently working on a High Availability configuration that will allow standalone nodes to be deployed with a replica node.

This feature is expected in October 2023.

Follow our changelog to remain up-to-date with the latest improvements in Managed Databases for Redis™.

Docs APIScaleway consoleDedibox consoleScaleway LearningScaleway.comPricingBlogCarreer
© 2023-2024 – Scaleway