Skip to content

Tools

Rewinding writes

Undo that restores the exact prior value and expiry, not a guessed reverse command.

What rewind is

Most “undo” features guess a reverse command: they saw SET, so they try to SET back. Varc doesn’t guess. While a debug session records, every write captures a before-image — the exact value and TTL the key had before the command ran.

Rewinding restores that before-image byte-for-byte, expiry included.

Rewind a single write

  1. Find the write in the session timeline — filter by key, command, or time.
  2. Select it and choose Rewind this write.
  3. Varc shows you exactly what will be restored before you confirm.

Roll back to a point in time

Select a moment in the timeline and choose Roll back to here. Varc replays the captured before-images in reverse order, restoring every affected key to its state at that instant.

Transactions are undone as one unit — a MULTI/EXEC block is never left half-rewound.

Honest limits

Rewind is scoped to what the session recorded. Writes that happened outside the proxy, or after another client changed the key again, are flagged so you can decide per key. Varc reports the consistency level for every restore rather than pretending conflicts don’t exist.

Recordings and security

Session recordings can contain production data, so they are encrypted on disk with a per-session key held in your OS keychain, and credentials are redacted irreversibly at capture time. See the connection and data foundations for the native product direction.