Redis › Redis Backup & Disaster Recovery
What considerations are important when backing up a very large Redis dataset without significantly impacting production performance during the backup process?
AdvancedAnswer
You should use BGSAVE rather than SAVE to avoid blocking the main Redis process during the snapshot, be aware that BGSAVE forks a child process which briefly needs additional memory roughly equal to the size of changes since the last save, schedule backups during lower traffic periods when possible, and monitor memory usage closely during backups to avoid triggering unexpected eviction or out of memory conditions.
-- Monitor memory during backup operations
INFO memory
BGSAVEReal-world example A team backing up a very large Redis dataset schedules their BGSAVE operations during their lowest traffic period each day, carefully monitoring memory usage to ensure the temporary overhead from the backup process does not cause unexpected issues.