Add note on RDB version import error#419
Conversation
While migrating Redis 8.6.1 to Valkey 9.0.3 on FreeBSD 15.0-p4 amd64, I ran into the following error ```log 6431:M 07 Mar 2026 09:37:43.232 # Can't handle RDB format version 12 ```` Document the simple fix. Signed-off-by: Bernard Spil <Sp1l@users.noreply.github.com>
zuiderkwast
left a comment
zuiderkwast
left a comment
There was a problem hiding this comment.
Thanks! This page as a whole currently doesn't describe the challenges with migrating from Redis > 7.2. The page as a whole needs more love. The simple note can help some but it can also give false hopes in the situations where it doesn't work.
| |-----------------------|--------| | ||
| | OSS 2.x - 7.2.x | 7.2.x | | ||
| | OSS 2.x - 7.2.x | 8.0 | | ||
| | CE 7.4 | n/a | |
There was a problem hiding this comment.
This table and the whole page needs some updates. Currently, it only describes a plain upgrade from Redis 7.2 before the two projects started to diverge.
This page doesn't describe the relaxed RDB version check. It should, and it the limitations need to be clearly explained, i.e. that it no new keys like Redis hash-field expiration can be present, and that reading the RDB file may or may not work depending on what Redis added in their RDB files. This matrix should describe the versions we have tested and confirmed.
| 9. Start Valkey: | ||
| > NOTE: If you enabled AOF in your Valkey configuration, disable it on the first start. Otherwise, the copied RDB file will not be imported into Valkey. | ||
|
|
||
| > NOTE: Set `rdb-version-check relaxed` for the first start to prevent "RDB format version" errors. |
There was a problem hiding this comment.
Loading an RDB with the relaxed check can easily fail when an unknown RDB opcode is encountered, and then this page is not of much help. We need more elaborate documentation.
2 participants
While migrating Redis 8.6.1 to Valkey 9.0.3 on FreeBSD 15.0-p4 amd64, I ran into the following error
Document the simple fix.