Immich 2.1 self-hosted photo and video management solution refines slideshow shuffling, adds album notifications, and polishes performance across platforms.
Those who run immich, how have you been backing up your library?
My deployment isn’t anything fancy, it is currently a Raspberry Pi 4 with a 2TB external drive for the photo library. Been running for more than 6 months with minimal issues. Now that we are at a stable release I need to get some kinda backup going for the photos themselves.
I run Immich in a VM on Proxmox which gets backed up every 12 hours and all my photos are on the NAS which gets snapshotted every 12 hours and pushed to an external drive and a Hetzner box.
Translation: “I run immich in a virtual machine, which I can manage from a web browser. The photos themselves are stored on a different device which gets backed up to a remote location twice a day.”
So why run immich in a virtual machine instead of in, say, a docker? Wouldn’t that be way less overhead? (Or is immich the only thing you’re hosting?)
The same way as all other services: all relevant data (compose.yml and all volume mounts) are in a btrfs subvolume. Every night a snapshot gets made and mirrored to a remote server by btrbk.
Those who run immich, how have you been backing up your library?
My deployment isn’t anything fancy, it is currently a Raspberry Pi 4 with a 2TB external drive for the photo library. Been running for more than 6 months with minimal issues. Now that we are at a stable release I need to get some kinda backup going for the photos themselves.
ZFS sending to a remotelab.
I backup the underlying storage (which is a VM) that immich writes to.
In theory it should be a perfect copy that just crashed.
I run Immich in a VM on Proxmox which gets backed up every 12 hours and all my photos are on the NAS which gets snapshotted every 12 hours and pushed to an external drive and a Hetzner box.
Translation: “I run immich in a virtual machine, which I can manage from a web browser. The photos themselves are stored on a different device which gets backed up to a remote location twice a day.”
So why run immich in a virtual machine instead of in, say, a docker? Wouldn’t that be way less overhead? (Or is immich the only thing you’re hosting?)
The same way as all other services: all relevant data (compose.yml and all volume mounts) are in a btrfs subvolume. Every night a snapshot gets made and mirrored to a remote server by btrbk.
how much do you pay for the remote server? was thinking about doing something like this for nextcloud (and i might end up using immich in the future)
That server is also a homeserver I manage for family (in another city). The two homeservers then mutually back up each other.