helpy4/immich
1
0
Fork 0
mirror of https://github.com/immich-app/immich synced 2025-10-17 18:19:27 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

chore: formatting

Browse source
This commit is contained in:
Jason Rasmussen 2025-10-17 11:03:58 -04:00
parent 1bcd5faae9
commit 6d5ed78bc5
No known key found for this signature in database
GPG key ID: 2EF24B77EAFA4A41
1 changed files with 3 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/docs/administration/backup-and-restore.md
View file

@ -77,12 +77,11 @@ gunzip --stdout "/path/to/backup/dump.sql.gz" \
docker compose up -d # Start remainder of Immich apps
```
</TabItem>
</TabItem>
<TabItem value="Windows system (PowerShell)" label="Windows system (PowerShell)">
Replace <DB_USERNAME> with the database username - usually postgres unless you have changed it.
```powershell title='Backup'
# Replace <DB_USERNAME> with the database username - usually postgres unless you have changed it.
[System.IO.File]::WriteAllLines("C:\absolute\path\to\backup\dump.sql", (docker exec -t immich_postgres pg_dumpall --clean --if-exists --username=<DB_USERNAME>))
```
@ -104,7 +103,7 @@ exit # Exit the Docker shell
docker compose up -d # Start remainder of Immich apps
```
</TabItem>
</TabItem>
</Tabs>
Note that for the database restore to proceed properly, it requires a completely fresh install (i.e. the Immich server has never run since creating the Docker containers). If the Immich app has run, Postgres conflicts may be encountered upon database restoration (relation already exists, violated foreign key constraints, multiple primary keys, etc.), in which case you need to delete the `DB_DATA_LOCATION` folder to reset the database.