Restoration of Synapse after disappearing 1 year of database history
+
Restoration of Synapse after losing 1 year of database history
-
Introduction
In July 2025, my PostgreSQL had broken, so I needed to restore it from my 1-y.o. backup. I was thinking about what to do, and my friend sent me this article, so we understood what to do!
For example, there is a room called #example:example.org (roomid !example:example.org), whose member was @user:example.net.
+
Introduction
In July 2025, my Synapse PostgreSQL had broken, so I needed to restore it from my 1-y.o. backup. I was thinking about what to do, and my friend sent me this article, so we understood what to do!
For example, there is a room called #example:example.org (roomid !example:example.org), whose member was @user:example.net.
The problem is that every server knows @user:example.net is in the room #example:example.org. But our server doesn’t! So that is what we should aim at solving the problem.
Architecture
We get 2 types of error messages:
synapse.handlers.receipts: [PUT-...] Ignoring receipt for room '!example:example.org' from server example.org as we're not in the room (there is the same error message, but when you get a typing event from an unknown room)
synapse.federation.federation_server: [PUT-...] Ignoring PDU for unknown room_id: !example:example.org