Backup Strategy for self-hosted sure

[m42cel]

I'm about to setup sure for my personal finances but I want to have some backups enabled right from the start.
The docker compose file has tree volumes volumes app-storage, postgres-data, redis-data. Which of those would I have to backup to restore all needed data? I assume redis-data can be re-built? Would I just need postgres-data or also app-storage? Maybe someone already has a backup script at hand to collect all needed data instead of just backing up the postgres database files.

[sokie]

I'm about to setup sure for my personal finances but I want to have some backups enabled right from the start. The docker compose file has tree volumes volumes app-storage, postgres-data, redis-data. Which of those would I have to backup to restore all needed data? I assume redis-data can be re-built? Would I just need postgres-data or also app-storage? Maybe someone already has a backup script at hand to collect all needed data instead of just backing up the postgres database files.

generally postgresql backup would be enough.
app storage is for uploaded files generally, but I don't think we add anything there.
Redis is fine to ignore, unless you app crashes and you might have events on the fly/in transit still.
In the app there is also an export all functionality which exports most of your data to a csv. This exports your data only, and not of other users on Sure tough, keep that in mind.

[LifeofDan-EL]

For me, I run a Postgres Local Backup container on the same stack that backs up the postgres-data daily.

I have my Docker stacks on an LXC inside Promox, so I have a cron job that also backs up that LXC to two separate drives, daily.

My next plan is to automate backing up the content of the Postgres backup container to Clouflare's R2.

[jjmata]

That looks super-cool. Want to added (commented out, maybe?) to the compose.example.yml so others have it an edit away, @LifeofDan-EL?

[LifeofDan-EL]

Do you mean adding the setup config to the compose.example.yml file on the Sure repo? Yes, I can do that. I can also add it to the compose.example.ai.yml too.

[jjmata]

Exactly! Indeed compose.example.ai.yml should be a super-set of the other one, let's try to keep them in sync.

[LifeofDan-EL]

Great then, let me do it and send in soon.

[LifeofDan-EL]

Made a PR here

[jjmata]

I'm about to setup sure for my personal finances but I want to have some backups enabled right from the start. The docker compose file has tree volumes volumes app-storage, postgres-data, redis-data. Which of those would I have to backup to restore all needed data? I assume redis-data can be re-built? Would I just need postgres-data or also app-storage? Maybe someone already has a backup script at hand to collect all needed data instead of just backing up the postgres database files.

If you deploy using the Helm Chart, which has the ability to do CNPG - has backup strategies in there as well. Like @sokie said ... the other volume is for import/export - which many people do in S3-compatible endpoints anyway.

[m42cel]

Thanks for the insights. I'm just running sure via docker-compose. My simple backup strategy will probably be to include a
docker compose exec db pg_dump -h localhost -U sure_user -d sure_production -Fc > backup.dump in my servers pre-backup script, which is executed before the borg backup copies it to an external disk and / or remote NAS.

As for the approach with the Postgres Local Backup container: Wouldn't it make more sense to mount at least the backup volume from the file system instead of a docker volume? I usually keep all the important data that should even survive a docker factory reset outside of docker volumes. Also makes it easier to copy it somewhere else, unless it's already a remotely mounted docker volume.

[LifeofDan-EL]

You are spot on, better to have it sit on the file system rather than the Docker created volume, modifying that.

[meetKazuki]

I do something like this. A script to dump the db, then restic to backup on Google Drive.

[LifeofDan-EL]

Yeah, I fixed that yesterday. I made a script that gets it, encrypts and sends the data to Cloudinary R2 using rclone.

[parvez-ahammed]

@LifeofDan-EL Thank you for your contribution on the docker compose. The Cloudinary R2 setup you just mentioned looks great as well.

Anyway we can just make it configurable through the UI? As I do something simmilar but using rclone to keep in google drive.

So the current docker flow is keeping the backup but it is keeping the backup in the machine itself so in order tl be double sure I am still requiring to add a seperate process which sends it to another cloud service of our preference.

If it could be done through UI it would be great.

My plan for drive would be, User goes to a backup tab from the settings from there can choose the place where he wants to put the backup in. In case of Google drive user needs to authorize properly while keeping the clientid and secret persisted.

Then based on the backup plan a backup is kept on a folder of google drive which can later be used to restore the pg db.