Restoring my backup - currently just playing around with container on docker(windows)
I set up docker environment with the folder called immich-app , then i pulled the compose files and env files from github for immich.
Uploaded a folder and notice it is in the upload folder.
Currently I am trying to create a backup ( just wish you can force an update as soon as you want)
But I want to know how would I first backup everything then restore it.
From the docs it says to back up
UPLOAD_LOCATION/library
UPLOAD_LOCATION/upload
UPLOAD_LOCATION/profile
no idea what profile is for because I have nothing inside of it but ok.
Next is says to run a
[System.IO.File]::WriteAllLines("C:\absolute\path\to\backup\dump.sql", (docker exec -t immich_postgres pg_dumpall --clean --if-exists --username=postgres))
Do I actually have to do this? how about if the last thing I did before my hdd got blown up was just copy and paste the dump.sql file ? so I would not even be able to run this command right?
Like what does this line even do?
ok now to the restore part
Restore
(((( THE COMMANDS FROM THE WEBSITE))))
https://immich.app/docs/administration/backup-and-restore/
All this is directly from the docks
In the part where it says
Remove-Item -Recurse -Force DB_DATA_LOCATION # CAUTION! Deletes all Immich data to start from scratch
Do I have to adjust something in this line? or is this going to do it automatically?
My question is while running the restore item do I have to be already in the path that my compose and env file is in?
then run all these commands right?
But how is it going to know exactly where
UPLOAD_LOCATION/library
UPLOAD_LOCATION/upload
UPLOAD_LOCATION/profile
is
Because it seems like one of these commands states it will Delete all immich data to start from scratch so I posted these 3 folders in the immich-app folder wouldn't it delete the photos inside them?
2 Replies
:wave: Hey @SWISS CHEEKS,
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.You would substitute in your DB_DATA_LOCATION from env to delete that folder before restoring
You would be on your own to restore the UPLOAD_LOCATION