Encrypted Redis backups.
xbackupman captures Redis as a point-in-time RDB snapshot pulled directly from your instance, compresses and encrypts it with AES-256-GCM inside the worker, and ships the ciphertext to a bucket you own — on the schedule you set.
What gets captured
- A binary RDB snapshot of the keyspace, produced by redis-cli against your instance.
- The full dataset at a consistent point in time — strings, hashes, sets, sorted sets and streams.
- In-stream gzip compression then AES-256-GCM encryption inside the worker; the plaintext RDB never touches our disk.
- A SHA-256 checksum recorded with every snapshot for on-demand integrity verification.
How it works
Connect your instance
Add a Redis connection with host, port and password. Private instances are reachable over SSH or an allow-listed egress IP.
Pull an RDB snapshot
The worker requests an RDB dump over the Redis protocol and streams it back — no file left behind on your server.
Compress, encrypt, upload
The snapshot is gzipped and sealed with AES-256-GCM in the worker, then the ciphertext is uploaded to your own S3-compatible bucket.
Verify and retain
Every snapshot carries a SHA-256 checksum. Schedule it on any cadence and let retention prune old copies while keeping your last one.
Your storage, your keys
Your Redis snapshots land in a bucket you control — S3, R2, B2 or MinIO. The RDB is encrypted before it leaves the worker, so your storage provider only ever holds ciphertext. You keep full custody of the data.
xbackupman never stores your backups on its own servers. It orchestrates the pipeline and records metadata — the encrypted artifacts live only in the S3-compatible bucket you connect. See how encryption works.
One-click restore
A Redis backup is a standard RDB file: download the decrypted snapshot and load it into any Redis instance by placing it as the dump file and restarting, or replaying it into a fresh instance. Automatic in-place restore into a live instance is intentionally not offered, to avoid clobbering a running cache.
Questions
QDoes the backup block my Redis instance?
The RDB snapshot is produced in the background by Redis itself, so reads and writes continue during the dump.
QWhich data types are captured?
All of them — an RDB snapshot is a complete point-in-time image of the keyspace, so every string, hash, set, sorted set and stream is included.
QCan I restore into a different Redis version?
RDB files are portable across compatible Redis versions; load the snapshot into your target instance to recover the dataset.
Back up more
One engine covers every source you run — on a single schedule, in one dashboard, encrypted into the same storage.