Backup before minor upgrade
Hello, hello. I'm starting to use 1.0.1 for Production. I see there is a newer 1.0.3.
I exported my People records to CSV.
From this guide: https://twenty.com/developers/section/self-hosting/upgrade-guide, I can backup the whole database.
My questions is: since the psql backup creates tables and schema, what happens if there is a mismatch between verions? The old backup without the new schema will be used, and I'm sure it will cause chaos.
Any advice?
3 Replies
Hello there
Patch upgrade won't involve upgrade or migrations commands meaning that you can switch from them on the go
Indeed if you restore a backup made from twenty version X you will have to use it along a twenty X instance
And upgrade to Y incrementally
Thanks @prastoin . I'll update .env to 1.0.3 and do the patch upgrade without worrying too much then.
BTW, I've revised the data models. What can I do before any upgrade(s) so that I can be sure my data models can be restored should something happens?
We do recommend dumping a backup before major/minor upgrade, if the upgrade fails then you can downgrade your twenty version and restore your previous backup and ask for help