How synchronization and backup are implemented - Amazon ElastiCache for Redis
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).

How synchronization and backup are implemented

All supported versions of Redis support backup and synchronization between the primary and replica nodes. However, the way that backup and synchronization is implemented varies depending on the Redis version.

Redis Version 2.8.22 and Later

Redis replication, in versions 2.8.22 and later, choose between two methods. For more information, see Redis Versions Before 2.8.22 and Snapshot and restore.

During the forkless process, if the write loads are heavy, writes to the cluster are delayed to ensure that you don't accumulate too many changes and thus prevent a successful snapshot.

Redis Versions Before 2.8.22

Redis backup and synchronization in versions before 2.8.22 is a three-step process.

  1. Fork, and in the background process, serialize the cluster data to disk. This creates a point-in-time snapshot.

  2. In the foreground, accumulate a change log in the client output buffer.


    If the change log exceeds the client output buffer size, the backup or synchronization fails. For more information, see Ensuring that you have enough memory to create a Redis snapshot.

  3. Finally, transmit the cache data and then the change log to the replica node.