Documentation: Structure backup section more clearly (#4559)

---------

Co-authored-by: shamoon <4887959+shamoon@users.noreply.github.com>
This commit is contained in:
quantenProjects 2023-11-16 01:26:52 +01:00 committed by GitHub
parent 07989bc2fa
commit 0d92648d62
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 46 additions and 38 deletions

View File

@ -7,7 +7,7 @@
"trailingComma": "es5",
"overrides": [
{
"files": "index.md",
"files": ["index.md", "administration.md"],
"options": {
"tabWidth": 4
}

View File

@ -5,7 +5,8 @@
Multiple options exist for making backups of your paperless instance,
depending on how you installed paperless.
Before making backups, make sure that paperless is not running.
Before making a backup, it's probably best to make sure that paperless is not actively
consuming documents at that time.
Options available to any installation of paperless:
@ -13,7 +14,8 @@ Options available to any installation of paperless:
thumbnails, metadata, and database contents to a specific folder. You may import your
documents and settings into a fresh instance of paperless again or store your
documents in another DMS with this export.
- The document exporter is also able to update an already existing
The document exporter is also able to update an already existing
export. Therefore, incremental backups with `rsync` are entirely
possible.
@ -50,6 +52,12 @@ Options available to bare-metal and non-docker installations:
### Restoring {#migrating-restoring}
If you've backed-up Paperless-ngx using the [document exporter](#exporter),
restoring can simply be done with the [document importer](#importer).
Of course, other backup strategies require restoring any volumes, folders and database
copies you created in the steps above.
## Updating Paperless {#updating}
### Docker Route {#docker-updating}