BACKUP LIST
List the immutable backup file paths pinned so far.
Browse all commands · Upstream source documentation
| Reference field | Value |
|---|---|
| Canonical name | BACKUP LIST |
| Catalog group | Server commands |
| Upstream since | 8.10.0 — upstream Redis/module version, not an ffkv release |
| Pinned catalog | Redis 8.10.0 |
Syntax
Section titled “Syntax”BACKUP LISTffkv behavior and limits
Section titled “ffkv behavior and limits”Server introspection describes ffkv, not a Redis process. MEMORY reports owned-allocation estimates, not jemalloc accounting. Administrative changes can affect all clients or persistent data; consult the scenario and operations guide before using destructive forms.
Source: README.md:393–395, 601–642; tests/bdd/features/server.feature; tests/bdd/features/catalog.feature.
Data-changing administration: use an isolated dataset or a verified backup. Lost replies have an unknown outcome; never blindly replay a destructive operation.
All requests share the 8 MiB framing/1,024-argument ingress limit; normal RESP replies have 64 MiB wire/logical budgets with bounded nesting/value counts. Management and Lua origins impose smaller budgets. These are not a process RSS cap. Catalog inclusion is not exhaustive option or wire-format parity. See limits and compatibility.
Upstream metadata
Section titled “Upstream metadata”The following fields come from the pinned Redis metadata, not measured ffkv performance or an assertion that ffkv enforces every upstream flag. Running COMMAND INFO/COMMAND DOCS describe the current engine.
Upstream Redis complexity: O(1)
Upstream arity: 2 (includes the command name; a negative number is a minimum).
Command flags: ADMIN, STALE.
Additional pinned upstream metadata
{ "group": "server", "since": "8.10.0"}Metadata source · Local snapshot: src/command_metadata.json, key backup|list.
BDD coverage and source examples
Section titled “BDD coverage and source examples”These are source observations, not a test run performed by this documentation build. A tag identifies scenario intent; an extracted vector identifies a command invocation, which may intentionally produce an error. Scenarios may require setup, multiple connections, persistence, cluster nodes or native-module fixtures.
- Sealed backup restores the seal boundary including incremental writes —
tests/bdd/features/server.feature:164; command tag and invocation observed. - Aborting an unsealed backup releases it for a new complete lifecycle —
tests/bdd/features/server.feature:206; invocation observed.
Extracted command vectors
Section titled “Extracted command vectors”The following JSON arrays are the test harness’s argument vectors, not shell commands. Numeric arguments are converted by the harness; objects of the form {"base64":"…"} represent decoded binary bytes, not a literal JSON command argument. Preserve scenario setup and connection ordering. See the CLI guide for shell quoting and binary stdin. No reply is invented or inferred.
Aborting an unsealed backup releases it for a new complete lifecycle — tests/bdd/features/server.feature:253 (I execute:)
[ "BACKUP", "LIST"]Next source assertion: the reply equals:
[]