Stay organized with collections
Save and categorize content based on your preferences.
Backups give you the ability to restore to a point in the past and
to export and analyze data. Backups are useful for the following
scenarios:
Disaster recovery: you can use backups as part of a disaster recovery plan.
Restore data in case of a disaster into a new Memorystore for Redis Cluster or another
Redis cluster. Backup schedules give more robust protection than ad hoc exports.
Data migration: migrate data between different Memorystore for Redis Cluster clusters.
Consolidate data or move it to a different region. You can restore backups from Memorystore for Redis Cluster instances or Redis instances.
Data sharing: share data between different teams or applications, enabling collaboration, offline data analytics, and data exchange.
Compliance: periodic backups of cache data can be created for compliance purposes.
Backups and backup collections
A backup is a point-in-time snapshot of your data. Backups are organized into
backup collections. A backup collection includes all backups for a particular
Memorystore for Redis Cluster instance. Deleting a Memorystore for Redis Cluster instance
does not automatically delete the corresponding backup collection.
You can set a time to live (TTL) on a backup by setting a retention period.
Once the backup exceeds it's TTL, Memorystore for Redis Cluster automatically deletes
the backup.
To recover data in a backup, you can create a new Memorystore for Redis Cluster
instance and seed the instance with data from the backup. At this time,
importing data into an existing Memorystore for Redis Cluster instance is not supported.
Automated and on-demand backups
You can initiate backups in two different ways:
Automated backups (Recommended): you can configure a backup schedule for a cluster that
initiates periodic backups.
On-demand backups: you can initiate a backup operation that begins immediately.
To learn how to set an automated backup schedule or to initiate a backup
see Manage backups.
Costs
You are charged storage costs for each backup based on the size of the backup.
There is a minimum 24-hour charge for each backup.
For more details, see Memorystore for Redis Cluster pricing.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[],[],null,["# Backups overview\n\nBackups give you the ability to restore to a point in the past and\nto export and analyze data. Backups are useful for the following\nscenarios:\n\n- **Disaster recovery**: you can use backups as part of a disaster recovery plan.\n Restore data in case of a disaster into a new Memorystore for Redis Cluster or another\n Redis cluster. Backup schedules give more robust protection than ad hoc exports.\n\n- **Data migration**: migrate data between different Memorystore for Redis Cluster clusters.\n Consolidate data or move it to a different region. You can restore backups from Memorystore for Redis Cluster instances or Redis instances.\n\n | **Note:** Memorystore for Redis Cluster backups cannot be imported into Redis instances, because they include multiple RDB files.\n- **Data sharing**: share data between different teams or applications, enabling collaboration, offline data analytics, and data exchange.\n\n- **Compliance**: periodic backups of cache data can be created for compliance purposes.\n\nBackups and backup collections\n------------------------------\n\nA backup is a point-in-time snapshot of your data. Backups are organized into\nbackup collections. A backup collection includes all backups for a particular\nMemorystore for Redis Cluster instance. Deleting a Memorystore for Redis Cluster instance\ndoes not automatically delete the corresponding backup collection.\n\nYou can set a time to live (TTL) on a backup by setting a retention period.\nOnce the backup exceeds it's TTL, Memorystore for Redis Cluster automatically deletes\nthe backup.\n\nTo recover data in a backup, you can create a new Memorystore for Redis Cluster\ninstance and seed the instance with data from the backup. At this time,\nimporting data into an existing Memorystore for Redis Cluster instance is not supported.\n\nAutomated and on-demand backups\n-------------------------------\n\nYou can initiate backups in two different ways:\n\n- **Automated backups** (Recommended): you can configure a backup schedule for a cluster that\n initiates periodic backups.\n\n- **On-demand backups**: you can initiate a backup operation that begins immediately.\n\nTo learn how to set an automated backup schedule or to initiate a backup\nsee [Manage backups](/memorystore/docs/cluster/manage-backups).\n\nCosts\n-----\n\nYou are charged storage costs for each backup based on the size of the backup.\nThere is a minimum 24-hour charge for each backup.\nFor more details, see [Memorystore for Redis Cluster pricing](/memorystore/docs/cluster/pricing#backups_pricing).\n\nWhat's next\n-----------\n\n- Learn how to [Manage backups](/memorystore/docs/cluster/manage-backups).\n- Learn about [Persistence](/memorystore/docs/cluster/persistence-overview)."]]
