In addition to the rdb snapshot and M/S Master/Slave, aof logs, there are no other

The latest project uses a pure Redis database with a data volume of more than 5 Gb. The rdb snapshot is scheduled every day, 1

The latest project uses a pure Redis database with a data volume of more than 5 Gb. The rdb snapshot is scheduled every day and the service is denied for 1-2 minutes, which is a bit intolerable. There is no M/S master-slave machine budget; AOF log stream, testing is not very reliable; previously saw the ppt of wooga (www.wooga.com), they used a regular backup, active in the past 10 minutes

The latest project uses a pure Redis database with a data volume of more than 5 Gb. The rdb snapshot is scheduled every day and the service is denied for 1-2 minutes, which is a bit intolerable.

There is no master-slave machine budget for M/S;
AOF log stream is not reliable after tests;

I have read the ppt at wooga (www.wooga.com) before. They adopt regular backup and export the active data in the past 10 minutes as yml files.

In addition to this solution, do you have any suggestions for Redis disaster recovery?

Original article address: Redis disaster recovery solution, in addition to rdb snapshot and M/S Master/Slave, aof log, is there any other feasible solution ?, Thanks to the original author.