:wave: Hi! I’ve successfully followed the upgrade ...
# community-help
d
👋 Hi! I’ve successfully followed the upgrade steps for a self-hosted Typesense server (on RHEL), and everything worked as expected — thank you for the great documentation. However, as part of testing our rollback procedures, I tried restoring a snapshot (taken before the upgrade) after downgrading to the previous version, but it seems the
/snapshot
endpoint does not support backward compatibility. Is there an official or recommended process for performing a version downgrade using existing data? Would appreciate any guidance or clarification on the proper downgrade procedure
k
What version did you try downgrading to? Some versions cannot be downgraded because of rocksdb disk format change. In such chase, we always publish a point release that has only a rocksdb version update so that you can safely downgrade to that minor version with the rocksdb version change.
This is documented in the release notes upgrade/downgrade section clearly.
d
My current version is 27.1 and I'm upgrading to version 28. I actually checked the documentation to see which version you recommended and I saw that it says 27. But I can't find how to do it. I tried to restore from the generated snapshot but when I start the node with that snapshot I see that it's still on version 28. Thanks for the reply, best regards.
k
I think we have 27.2 which will be compatible
Actually no, v28 is already fully backward compatible. So I am surprised that the snapshot does not work.
28 -> 27.1 should work.
d
Maybe for the downgrade I should have the entire cluster shut down, apply the snapshot, and power it on? Because the method I used is the same as for the upgrade, node by node and ending with the leader.
k
Not needed. What error did you get?
d
None really. I just powered on the node, saw that it started normally, but both in the log when I started the node and in the debug endpoint I see that it's v28.
k
Check the /debug API response. What version does it return?
d
Copy code
{
  "state": 4,
  "version": "28.0"
}
Sólo he probado en ese follower
k
Then it's the v28 binary you are using.
d
Could you explain a little more about what you mean by the rpm I use? What are the possibilities? Thanks in advance.
k
Hmm that's really odd. Can you try extracting the v27 RPM and running the binary inside manually to check what version it says?
d
Would it be possible to downgrade if, having the RPM for the version I want to go back to (as long as it's compatible), I followed the upgrade procedure in reverse? Do you mean I should try that?
k
Yes using the RPM of the version you want to downgrade to will work.
d
In the end we solved it by running a downgrade from the repository, having the binary of the version we want to download
👍 1