Snapshot and restore - Amazon ElastiCache
Constraints
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Snapshot and restore

Amazon ElastiCache caches running Serverless Memcached can back up their data by creating a snapshot. You can use the backup to restore a cache or seed data to a new cache. The backup consists of the cache’s metadata, along with all of the data in the cache. All backups are written to Amazon Simple Storage Service (Amazon S3), which provides durable storage. At any time, you can restore your data by creating a new Serverless Memcached cache and populating it with data from a backup. With ElastiCache, you can manage backups using the Amazon Web Services Management Console, the Amazon Command Line Interface (Amazon CLI), and the ElastiCache API.

If you plan to delete a cache and it's important to preserve the data, you can take an extra precaution. To do this, create a manual backup first, verify that its status is available, and then delete the cache. Doing this makes sure that if the backup fails, you still have the cache data available. You can retry making a backup, following the best practices outlined preceding.

Topics

Backup constraints

Consider the following constraints when planning or making backups:

  • Backup and restore are supported only for caches running on Redis or Serverless Memcached.

  • During any contiguous 24-hour period, you can create no more than 24 manual backups per serverless cache.

  • During the backup process, you can't run any other API or CLI operations on serverless cache.