From b86b07a49c0d8c9a804a8e790761ec49b330426a Mon Sep 17 00:00:00 2001 From: Dillard Blom Date: Fri, 6 Nov 2026 11:56:10 +0100 Subject: [PATCH] Disaster recovery guide: --salvage after a restore that stopped halfway --- docs/DISASTER-RECOVERY.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/DISASTER-RECOVERY.md b/docs/DISASTER-RECOVERY.md index 06a238f..3a2d41d 100644 --- a/docs/DISASTER-RECOVERY.md +++ b/docs/DISASTER-RECOVERY.md @@ -117,6 +117,11 @@ first. If none is better, `--salvage` restores whatever can be read: occ backup:restore:full offsite --install-apps --salvage +If a restore already stopped halfway, run it as in step 8: maintenance mode off, with `--force` and +without `--install-apps`: + + occ maintenance:mode --off && occ backup:restore:full offsite --salvage --force + - Files that cannot be read are left out and listed at the end; everything else is restored. - If the database cannot be restored (its dump is damaged, or it does not fit this installation), the database stays as the fresh installation made it, and the data directory