Scheduled Redis backups to cloud storage
An RDB snapshot of your Redis server, fetched over the network and kept in Google Drive, Amazon S3, OneDrive or any other cloud, as often as every 6 hours.
How it works
Redis can hand a copy of its data to a client the same way it feeds a replica. redis-cli --rdb asks for that copy and writes it as an RDB file, which is what we run, then gzip and save it:
redis-cli -h host -p 6379 --user backup --pass "$REDIS_PASSWORD" --rdb dump.rdb
Steps
- Sign in, open Databases and press Connect a database. Choose Redis, or your hosting service by name.
- Paste the connection string (
redis://user:password@host:6379, orrediss://for TLS), or fill in the server, database, username and password one by one. - If the database only answers on its own server, fill in the SSH server fields too; it is then reached through that server, and the database address is usually
localhost. - Press Schedule on its card. Choose the cloud and folder, how many backups to keep (1 to 365), and how often: every 6 hours, every 12 hours, every day, every Sunday or on the 1st of every month.
- Save. The first backup starts at once, and its progress shows in the job list.
Hosted Redis that refuses
Some hosted services do not let a client take a snapshot: Amazon ElastiCache, Upstash and Azure Cache for Redis among them. The connection check passes, and the backup says the server refused. For those, use the service's own export, and copy its files with a schedule from the bucket it writes to.
Encrypted backups
Give the database a backup passphrase (12 characters or more) and every backup is encrypted with AES-256 before it leaves our server; its name gains .enc. The cloud you save into then holds nothing readable. To open one on your own computer, with the OpenSSL that comes with macOS, Linux and Git for Windows:
openssl enc -d -aes-256-cbc -pbkdf2 -iter 600000 -in cache-2026-11-04-020000.rdb.gz.enc -out cache-2026-11-04-020000.rdb.gz
Keep the passphrase somewhere safe. Without it nobody, including us, can open the backups.
Loading a snapshot back
An RDB file is loaded by the Redis server itself when it starts, so it cannot be restored over the network from here. On the server:
- Find the data directory and file name:
redis-cli CONFIG GET dirandCONFIG GET dbfilename. - Stop Redis. A running Redis writes its own snapshot on shutdown and would overwrite the file you put there.
gunzip -c cache-2026-11-04-020000.rdb.gz > /var/lib/redis/dump.rdb- If
appendonlyis on, Redis loads the append-only file instead; turn it off for this start, then back on withCONFIG SET appendonly yes. - Start Redis.
Limits
- A backup is the data at one moment, not a continuous replica or point-in-time recovery.
- A backup stops after 2 hours, or past 20 GB compressed, unless the operator has changed those limits.
- Each backup's size counts towards your transfer allowance.
Questions
Does taking a snapshot slow Redis down?
Redis forks to write the snapshot, as it does for its own saves and for a new replica. On a large dataset the fork takes a moment and uses extra memory while it runs, so schedule it for a quiet hour.
Try it
Prepaid: 30 GB free, then 500 GB for ₹100 or 2,500 GB for ₹500, each valid a year. No card is asked for to start.