Restoring from a backup into a new cache - Amazon ElastiCache (Redis OSS)
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).

Restoring from a backup into a new cache

You can restore an existing backup into a new serverless cache or a self-designed cluster.

Note

ElastiCache Serverless supports RDB files compatible with Redis OSS versions between 5.0 and the latest version available.

To restore a backup to a serverless cache (console)

  1. Sign in to the Amazon Web Services Management Console and open the ElastiCache console at https://console.amazonaws.cn/elasticache/.

  2. From the navigation pane, choose Backups.

  3. In the list of backups, choose the box to the left of the backup name that you want to restore.

  4. Choose Actions and then Restore.

  5. Enter a name for the new serverless cache, and an optional description.

  6. Click Create to create your new cache and import data from your backup.

To restore a backup to a self-designed cluster (console)

  1. Sign in to the Amazon Web Services Management Console and open the ElastiCache console at https://console.amazonaws.cn/elasticache/.

  2. From the navigation pane, choose Backups.

  3. In the list of backups, choose the box to the left of the backup name you want to restore from.

  4. Choose Actions and then Restore.

  5. Choose Design your own cache and customize the cluster settings, such as node type, sizes, number of shards, replicas, AZ placement, and security settings.

  6. Choose Create to create your new self-designed cache and import data from your backup.

Note

ElastiCache Serverless supports RDB files compatible with Redis OSS versions between 5.0 and the latest version available.

To restore a backup to a new serverless cache (Amazon CLI)

The following Amazon CLI example creates a new cache using create-serverless-cache and imports data from a backup.

For Linux, OS X, or Unix:

aws elasticache create-serverless-cache \
    --serverless-cache-name CacheName \
    --engine redis
    --snapshot-arns-to-restore Snapshot-ARN

For Windows:

aws elasticache create-serverless-cache ^
    --serverless-cache-name CacheName ^
    --engine redis ^
    --snapshot-arns-to-restore Snapshot-ARN

For Windows:

To restore a backup to a self-designed cluster (Amazon CLI)

You can restore a Redis OSS serverless cache backup, and you can also resotore a Redis OSS self-designed cluster.

You can restore a Redis OSS serverless cache backup in two ways.

  • You can restore to a single-node Redis OSS (cluster mode disabled) cluster using the Amazon CLI operation create-cache-cluster.

  • You can restore to a Redis OSS cluster with read replicas (a replication group). To do this, you can use either Redis OSS (cluster mode disabled) or Redis OSS (cluster mode enabled) with the Amazon CLI operation create-replication-group. In this case, you seed the restore with a Redis OSS .rdb file. For more information on seeding a new self-designed cluster, see Seeding a new self-designed cluster with an externally created backup.

You can restore a Redis OSS (cluster mode disabled) backup in two ways.

  • You can restore to a single-node Redis OSS (cluster mode disabled) cluster using the Amazon CLI operation create-cache-cluster.

  • You can restore to a Redis OSS cluster with read replicas (a replication group). To do this, you can use either Redis OSS (cluster mode disabled) or Redis OSS (cluster mode enabled) with the Amazon CLI operation create-replication-group. In this case, you seed the restore with a Redis OSS .rdb file. For more information on seeding a new self-designed cluster, see Seeding a new self-designed cluster with an externally created backup.

When using either the create-cache-cluster or create-replication-group operation, be sure to include the parameter --snapshot-name or --snapshot-arns to seed the new cluster or replication group with the data from the backup.