Use DUMP to serialize the value stored at a key into a portable, Redis-specific binary blob.
The blob carries the value together with a version stamp and a checksum, but not the key name and not its time to live. Feeding it to RESTORE recreates the value under any key name, in the same database or in another one, which makes the pair the standard way to move or back up individual keys. A missing key returns null.
The reply is raw binary data, not text: keep it in a byte-safe container and avoid string encodings that would corrupt it.
Syntax#
Arguments#
| Argument | Required | Repeatable | Description |
|---|---|---|---|
<key> | Yes | No | Redis key targeted by the command. |
Response#
The reply reports the result of the operation. Error replies have the same shape in RESP2 and RESP3 and are surfaced as exceptions by the SDKs below.
| Protocol | Reply |
|---|---|
| RESP2 | Bulk string or Null bulk string or null array |
| RESP3 | Bulk string or Null |
Client libraries often decode bulk strings, maps, sets, and numeric strings into language-native values. The table describes the Redis wire reply.
Examples#
TCP examples use the TLS REDIS_URL from the Upstash console. REST examples use UPSTASH_REDIS_REST_URL and UPSTASH_REDIS_REST_TOKEN.
Redis CLI
@upstash/redis
This command is not supported yet in @upstash/redis.
upstash_redis
This command is not supported yet in upstash_redis.