Redis restore proofs

Capture a Redis RDB, verify it can be restored, and choose whether Revenant keeps the snapshot.

Redis may be a rebuildable cache, or it may contain sessions, queues, and other state that matters during an outage. Revenant lets you prove that a Redis RDB can be restored, while leaving the decision to keep snapshot bytes with you.

What a Redis proof does

  • Connects to the Redis instance and records a redacted connection fingerprint.
  • Captures an RDB and restores it in an isolated, temporary Redis server.
  • Checks that the recovered dataset is readable and records restore evidence.
  • Keeps snapshot bytes only when you explicitly enable snapshot storage; otherwise it verifies the restore without retaining the RDB.

Redis proof is its own resource and quota. It does not consume a PostgreSQL workflow, AWS restore drill, or parallel PostgreSQL drill slot.

Use Redis proof in Revenant Cloud

  • Open Redis in the Revenant Cloud dashboard and add the Redis connection URL.
  • Test the connection, then save the Redis resource. Connection credentials are stored separately from the visible resource details.
  • Choose whether to enable snapshot storage. It is optional; when enabled, the plan sets a maximum retention window.
  • Start a restore proof and review its status, restore result, and expiry (when a snapshot was retained) in the Redis proof history.

Plan limits

  • Developer (free): run Redis proof locally with the Revenant CLI; no Revenant Cloud snapshot storage.
  • Starter (₹499/month after the 30-day trial): 1 Redis instance, 4 restore proofs per calendar month, and up to 24 hours of opt-in snapshot retention.
  • Pro (₹1,499/month): 10 Redis instances, 30 restore proofs per calendar month, and up to 7 days of opt-in snapshot retention.
  • Enterprise: contact Revenant for custom limits and retention.
revenant redis-prove --url redis://localhost:6379

The CLI runs the proof from your machine and does not upload Redis data to Revenant. Use a rediss:// URL for TLS-protected connections when your Redis provider requires it.