Help on setting up borg backup
Hi, I have immich running on a raspberry pi 5 and it is working well, with my photos and videos stored on a connected ssd drive. I'd now like to start backing up the database and the library. As a first step I am adding a second connected drive, and want to create a backup there. I am looking at the sample script in the docs, which starts with:
UPLOAD_LOCATION="/path/to/immich/directory" # Immich database location, as set in your .env file
BACKUP_PATH="/path/to/local/backup/directory"
I assume the BACKUP_PATH should be set to a directory on the new hard drive. The UPLOAD_LOCATION though I am not sure. In my .env file, I have configured immich as
The location where your uploaded files are stored
UPLOAD_LOCATION="/media/balents/Extreme Pro/library"
The location where your database files are stored
DB_DATA_LOCATION=./postgres
So the immich database is not in the same location as the library. I am guessing that if I for example set UPLOAD_LOCATION to the match the one in my .env, my library will be backed up but not the database? Do I need to just create two different backups?
Thanks!
Thanks!
1 Reply
:wave: Hey @balentsucsb,
Thanks for reaching out to us. Please carefully read this message and follow the recommended actions. This will help us be more effective in our support effort and leave more time for building Immich :immich:.
References
- Container Logs:
docker compose logs docs
- Container Status: docker ps -a docs
- Reverse Proxy: https://immich.app/docs/administration/reverse-proxy
- Code Formatting https://support.discord.com/hc/en-us/articles/210298617-Markdown-Text-101-Chat-Formatting-Bold-Italic-Underline#h_01GY0DAKGXDEHE263BCAYEGFJA
Checklist
I have...
1. :blue_square: verified I'm on the latest release(note that mobile app releases may take some time).
2. :blue_square: read applicable release notes.
3. :blue_square: reviewed the FAQs for known issues.
4. :blue_square: reviewed Github for known issues.
5. :blue_square: tried accessing Immich via local ip (without a custom reverse proxy).
6. :blue_square: uploaded the relevant information (see below).
7. :blue_square: tried an incognito window, disabled extensions, cleared mobile app cache, logged out and back in, different browsers, etc. as applicable
(an item can be marked as "complete" by reacting with the appropriate number)
Information
In order to be able to effectively help you, we need you to provide clear information to show what the problem is. The exact details needed vary per case, but here is a list of things to consider:
- Your docker-compose.yml and .env files.
- Logs from all the containers and their status (see above).
- All the troubleshooting steps you've tried so far.
- Any recent changes you've made to Immich or your system.
- Details about your system (both software/OS and hardware).
- Details about your storage (filesystems, type of disks, output of commands like fdisk -l and df -h).
- The version of the Immich server, mobile app, and other relevant pieces.
- Any other information that you think might be relevant.
Please paste files and logs with proper code formatting, and especially avoid blurry screenshots.
Without the right information we can't work out what the problem is. Help us help you ;)
If this ticket can be closed you can use the /close command, and re-open it later if needed.
https://immich.app/docs/administration/backup-and-restore
This thread has been closed. To re-open, use the button below.