Stay organized with collections
Save and categorize content based on your preferences.
Backups let you restore your Memorystore for Valkey instances to a specific
point in time. In addition, you can use backups to export and analyze data.
Backups are useful for the following scenarios:
Disaster recovery: use backups as part of a disaster recovery plan. If a
disaster occurs, then you can restore your data to a new Memorystore for Valkey
instance.
Data migration: migrate data between different Memorystore for Valkey
instances. You can consolidate data or move it to a different region. You can
also restore backups from Memorystore for Valkey instances.
Data sharing: share data between different teams or applications, enabling collaboration, offline data analytics, and data exchange.
Compliance: create periodic backups of cache data 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 Memorystore for Valkey instance. If you delete an instance, then Memorystore for Valkey doesn't delete the corresponding backup collection automatically.
You can set a time to live (TTL) for a backup by setting a retention period.
After the backup exceeds its TTL, Memorystore for Valkey deletes the backup
automatically.
To recover data in a backup, you can create an instance and seed the instance with data from the backup. However, you
can't import data into an existing instance.
Automated and on-demand backups
You can create backups in the following ways:
Automated backups (Recommended): configure a backup schedule for an
instance. As a result, Memorystore for Valkey initiates periodic backups
for the instance.
On-demand backups: initiate a backup operation that begins immediately.
For more information about setting an automated backup schedule or initiating a
backup, see Manage backups.
Costs
Based on the size of a backup and the region where the backup is located, you're
charged storage costs for the backup. For each backup, there's a minimum 24-hour
charge. For more information, see Memorystore for Valkey 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,["# About backups\n\nBackups let you restore your Memorystore for Valkey instances to a specific\npoint in time. In addition, you can use backups to export and analyze data.\n\nBackups are useful for the following scenarios:\n\n- **Disaster recovery**: use backups as part of a disaster recovery plan. If a\n disaster occurs, then you can restore your data to a new Memorystore for Valkey\n instance.\n\n- **Data migration**: migrate data between different Memorystore for Valkey\n instances. You can consolidate data or move it to a different region. You can\n also restore backups from Memorystore for Valkey instances.\n\n- **Data sharing**: share data between different teams or applications, enabling collaboration, offline data analytics, and data exchange.\n\n- **Compliance**: create periodic backups of cache data 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 Memorystore for Valkey instance. If you delete an instance, then Memorystore for Valkey doesn't delete the corresponding backup collection automatically.\n\nYou can set a time to live (TTL) for a backup by setting a retention period.\nAfter the backup exceeds its TTL, Memorystore for Valkey deletes the backup\nautomatically.\n\nTo recover data in a backup, you can [create an instance](/memorystore/docs/valkey/create-instances) and seed the instance with data from the backup. However, you\ncan't import data into an existing instance.\n\nAutomated and on-demand backups\n-------------------------------\n\nYou can create backups in the following ways:\n\n- **Automated backups** (Recommended): configure a backup schedule for an\n instance. As a result, Memorystore for Valkey initiates periodic backups\n for the instance.\n\n- **On-demand backups**: initiate a backup operation that begins immediately.\n\nFor more information about setting an automated backup schedule or initiating a\nbackup, see [Manage backups](/memorystore/docs/valkey/manage-backups).\n\nCosts\n-----\n\nBased on the size of a backup and the region where the backup is located, you're\ncharged storage costs for the backup. For each backup, there's a minimum 24-hour\ncharge. For more information, see [Memorystore for Valkey pricing](/memorystore/docs/valkey/pricing#backups_pricing)."]]
