If PostgreSQL is also shut down and you dont start the backup before its completely stopped it should be ok. You might need to restore to the same version of PostgreSQL and make sure it is setup the same way.
If you dump the data, it is safer, both that you get a known good state, and that it can be restored to any new database.
Grabbing the files as you suggest should be ok at least 90 percent of the time. But why risk it?
I do this always for any service but also do a dump of the db in the top directory to keep a clean copy to could be version independent. They wont take much more space ho estly
It’s the way I do all of my service backups. One separate DB container per docker stack so nothing else is in there, all the data in one folder, and off we go at 1AM.
Yeah, also I don’t run the latest version of the app in order to avoid breakage. I pin some tag so the app version so there shouldn’t be a significant version mismatch during restore. I think @Esquero’s suggestion to also dump the db just in case makes sense too. I’m gonna be writing a backup script / systemd unit anyways, might as well as a couple of lines for that.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !selfhosted@lemmy.world
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don’t control.
Rules:
Be civil: we’re here to support and learn from one another. Insults won’t be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it’s not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don’t duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
If PostgreSQL is also shut down and you dont start the backup before its completely stopped it should be ok. You might need to restore to the same version of PostgreSQL and make sure it is setup the same way. If you dump the data, it is safer, both that you get a known good state, and that it can be restored to any new database. Grabbing the files as you suggest should be ok at least 90 percent of the time. But why risk it?
I do this always for any service but also do a dump of the db in the top directory to keep a clean copy to could be version independent. They wont take much more space ho estly
It’s the way I do all of my service backups. One separate DB container per docker stack so nothing else is in there, all the data in one folder, and off we go at 1AM.
Yeah, also I don’t run the
latestversion of the app in order to avoid breakage. I pin some tag so the app version so there shouldn’t be a significant version mismatch during restore. I think @Esquero’s suggestion to also dump the db just in case makes sense too. I’m gonna be writing a backup script / systemd unit anyways, might as well as a couple of lines for that.They do have a doc for this. https://immich.app/docs/administration/backup-and-restore/
I dump my immich db weekly and every 2 weeks sync the media folders to a remote destination
Thanks all for the comments and suggestions!