Data(base) backup and restore

[jpprost]

Hello,

would there be a --preferably automated-- procedure to backup the content data (i.e., presumably the db), then to restore it in a fresh install?
If not, what would be the best (cleanest, easiest, etc.) option for that?

The best couple of ways I can think of are:
I/
(a) to manually dump the db regularly,
(b) (in case restoring is required) run the installer in a fresh environment, then restore the dump manually in the newly installed Postgres instance.

The problem is, could the manual process mess with settings, or config files that would not be adequately updated?

Alternatively:
II/
(a) dump the db
(b) the dump is restored in a new Postgres instance first, then
(c) the installer is run, assuming it can be forced to use this db instance.

But a similar question occurs with regard to the internal settings and config files.

Sorry for cross-posting in the Consul/Community, but I can not find the topic being addressed anywhere. Apologies if that is the case. If so, it would be very kind of you to point me in the right direction.

Cheers,
JP

[javierm]

Hi, @jpprost 😄.

We currently don't provide a mechanism to automate backups. The reason is that most institutions using Consul Democracy already have their own backup systems that work for pretty much every application.

Between the methods you suggest, method I would work. Method II might work as well (we've done it in the past) but it isn't officially supported / actively tested, so there's a chance you run into some issues when the installer tries to setup the database. It will also overwrite everything you've changed in the settings table (the only gotcha I'm aware of, by the way).

In both cases, make sure you install the same version of Consul Democracy that you are using in the old instance.

Regarding content, you probably want to include files attached by people using the application. The full list of files and folders that might be affected are in config/deploy.rb (linked_files and linked_dirs). Note that not all of them need to be included in the backup, though (for example, the tmp folder).

Hope that helps!

[jpprost]

Works fine with an ubuntu 22.04 and python3.13.

[jpprost]

HURRAY! :-) backup and restoration processes implemented and successfully tested (bash scripts).
A few drawbacks left, but nothing important.
I'll make a pull request as soon as I have got my own fork ready, if you are happy with that.

[javierm]

Works fine with an ubuntu 22.04 and python3.13.

Which system were you using when you got the error? Just curious.

I'll make a pull request as soon as I have got my own fork ready, if you are happy with that.

By all means 👍. Sorry in advance if starting the review takes us a while 🙏.

[jpprost]

Which system were you using when you got the error? Just curious.

The brand new Ubuntu 24.04 :-)

[javierm]

Good to know! As you've probably already noticed, this version isn't supported yet. It looks like adding support for it will require some changes then 😌.