Data Rollback
The master-replica version of Redis provides a second-level data rollback function. AOnce the rollback feature is enabled, you can restore the entire instance’s data to a specific second-level time point (restoring to a new instance). This functionality offers highly granular data recovery, providing maximum protection for your data security. Currently, data rollback is supported for master-replica instance versions 4.0, 5.0, and 6.0.
Overview of Data Rollback Function
To safeguard business data, the master-replica version of Redis supports a data rollback feature based on the AOF (Append-Only File) persistence mechanism. Incremental AOF data is archived, enabling second-level recovery and enhancing operational convenience.
Enable Data Rollback Function
Adjust Rollback Space Size
When the archived AOF incremental data exceeds the purchased storage limit, older AOF incremental data files will be deleted. To retain more data, you can increase the rollback storage space when the current space is insufficient.
Select Specified Files for Rollback
To perform a rollback, select a specific AOF file and choose the rollback time. Please ensure that the rollback time falls within the time range covered by the selected AOF file.
Precautions
- After downsizing an instance, performing a data rollback might encounter capacity issues if the memory data at the selected rollback time exceeds the current instance specifications. Thus, please choose an appropriate instance specification for the rollback to avoid operation failure.
- In the console, the status of a new instance created by data rollback will display as "Running"; however, during this time, the service may still be loading AOF data and is not yet available. Depending on the actual size of the AOF file, it may take approximately 1-10 minutes for the Redis service to become fully available.
