Skip to content

Commit

Permalink
Getting Started: Add -f flag to backup command usage examples
Browse files Browse the repository at this point in the history
  • Loading branch information
@lastzero
lastzero committed Nov 21, 2024
1 parent 10f4306 commit 65b492b
Show file tree
Hide file tree
Showing 4 changed files with 8 additions and 8 deletions.
4 changes: 2 additions & 2 deletions docs/getting-started/docker-compose.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -345,8 +345,8 @@ The currently supported user ID ranges are 0, 33, 50-99, 500-600, 900-1250, and
| *Show Migration Status* | `docker compose exec photoprism photoprism migrations ls` |
| *Repeat Failed Migrations* | `docker compose exec photoprism photoprism migrations run -f` |
| *Reset Database* | `docker compose exec photoprism photoprism reset --yes` |
| *Backup Database* | `docker compose exec photoprism photoprism backup -a -i` |
| *Restore Database* | `docker compose exec photoprism photoprism restore -a -i` |
| *Backup Database* | `docker compose exec photoprism photoprism backup -i -f` |
| *Restore Database* | `docker compose exec photoprism photoprism restore -i -f` |
| *Change Password* | `docker compose exec photoprism photoprism passwd [username]` |
| *Show User Management Commands* | `docker compose exec photoprism photoprism users help` |
| *Reset User Accounts* | `docker compose exec photoprism photoprism users reset --yes` |
Expand Down
4 changes: 2 additions & 2 deletions docs/getting-started/docker.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -237,8 +237,8 @@ The currently supported user ID ranges are 0, 33, 50-99, 500-600, 900-1250, and
| *Show Migration Status* | `docker exec -ti photoprism photoprism migrations ls` |
| *Repeat Failed Migrations* | `docker exec -ti photoprism photoprism migrations run -f` |
| *Reset Database* | `docker exec -ti photoprism photoprism reset --yes` |
| *Backup Database* | `docker exec -ti photoprism photoprism backup -a -i` |
| *Restore Database* | `docker exec -ti photoprism photoprism restore -a -i` |
| *Backup Database* | `docker exec -ti photoprism photoprism backup -i -f` |
| *Restore Database* | `docker exec -ti photoprism photoprism restore -i -f` |
| *Change Password* | `docker exec -ti photoprism photoprism passwd [username]` |
| *Show User Management Commands* | `docker exec -ti photoprism photoprism users help` |
| *Reset User Accounts* | `docker exec -ti photoprism photoprism users reset --yes` |
Expand Down
4 changes: 2 additions & 2 deletions docs/getting-started/portainer/index.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -188,8 +188,8 @@ The command-line interface is also well suited for job automation using a [sched
| *Show Migration Status* | `photoprism migrations ls` |
| *Repeat Failed Migrations* | `photoprism migrations run -f` |
| *Reset Database* | `photoprism reset --yes` |
| *Backup Database* | `photoprism backup -a -i` |
| *Restore Database* | `photoprism restore -a -i` |
| *Backup Database* | `photoprism backup -i -f` |
| *Restore Database* | `photoprism restore -i -f` |
| *Change Password* | `photoprism passwd [username]` |
| *Show User Management Commands* | `photoprism users help` |
| *Reset Users* | `photoprism users reset --yes` |
Expand Down
4 changes: 2 additions & 2 deletions docs/getting-started/troubleshooting/mariadb.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -171,12 +171,12 @@ If you want to move your MariaDB database to another server or virtual machine:
To create a database backup:

- [ ] In case the MariaDB version and system architecture match, you can shut down your existing PhotoPrism instance and the database server, and then copy the [entire *database* storage folder](../../user-guide/backups/folders.md#database) without changing any file or folder permissions
- [ ] Alternatively, you can use the built-in [`photoprism backup -i`](../../user-guide/backups/index.md#backup-command) [CLI command](../docker-compose.md#opening-a-terminal), or backup the database with a [manually created SQL dump](https://mariadb.com/kb/en/mariadb-dump/) (backup file)
- [ ] Alternatively, you can use the built-in [`photoprism backup -i -f`](../../user-guide/backups/index.md#backup-command) [CLI command](../docker-compose.md#opening-a-terminal), or backup the database with a [manually created SQL dump](https://mariadb.com/kb/en/mariadb-dump/) (backup file)

On the new server:

- [ ] If you copied the entire *database* storage folder, start the MariaDB server and make sure PhotoPrism can [access the new database](#cannot-connect) by updating its configuration or your network settings if necessary
- [ ] To restore the database from a backup dump ([either manually](https://mariadb.com/kb/en/restoring-data-from-dump-files/) or [using the `photoprism restore -i`](../../user-guide/backups/restore.md#restore-command) [CLI command](../docker-compose.md#opening-a-terminal)), the MariaDB server must be running and PhotoPrism must be restarted after the backup has been restored
- [ ] To restore the database from a backup dump ([either manually](https://mariadb.com/kb/en/restoring-data-from-dump-files/) or [using the `photoprism restore -i -f`](../../user-guide/backups/restore.md#restore-command) [CLI command](../docker-compose.md#opening-a-terminal)), the MariaDB server must be running and PhotoPrism must be restarted after the backup has been restored
- [ ] Be sure to [never expose your database](#cannot-connect) to the public Internet, and [use strong passwords](#wrong-password) if the database is exposed to an external network

## Server Crashes
Expand Down

0 comments on commit 65b492b

Please sign in to comment.