Selfhosted

39893 readers

462 users here now

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).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

Backing up Immich (lemmy.ca)

submitted 7 months ago* (last edited 7 months ago) by [email protected] to c/[email protected]

6 comments fedilink hide all child comments

The backup doc from Immich states that one should use Postgres' dump functionality to backup the database, as well as copy the upload location.

Is there any counter indication to doing this instead:

Create a dir immich with subdirs db and library
Mount the db dir as a volume for the database
Mount the library dir as a volume for the upload location
Backup the whole immich dir without dumping the Postgres db. (Stop Immich while before doing this)

top 6 comments

sorted by: hot top controversial new old

[–] [email protected] 12 points 7 months ago

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?

[–] [email protected] 5 points 7 months ago

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

[–] [email protected] 3 points 7 months ago

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

[–] [email protected] 2 points 7 months ago (1 children)

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.

[–] [email protected] 1 points 7 months ago

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.

[–] [email protected] 2 points 7 months ago

Thanks all for the comments and suggestions!