Merge pull request #29 from dillardblom/polish

Docs: --salvage after a stopped restore; a full disk during a restore

CHANGELOG.md

@@ -55,6 +55,9 @@ shown under 1.0.0. The git tag of a release candidate goes after the date.
 
 ### Known issues
 - Empty folders are not backed up or restored; to be fixed in 1.0.3 (#27).
+- A full disk during a restore looks like a damaged backup ("Size mismatch"), and with `--salvage`
+  the restore goes on and lists the remaining files. The backup itself is fine: make room and run
+  the restore again. To be fixed in 1.0.3.
 
 ## [1.0.1] - 2026-11-01
 

README.md

@@ -296,6 +296,9 @@ On the backlog; know them before you rely on NG Backup:
 - **Empty folders do not come back.** A backup only records files, so a folder without files is
   not restored. To be fixed in 1.0.3
   ([#27](https://github.com/dillardblom/ng_backup/issues/27)).
+- **A full disk during a restore looks like a damaged backup.** The reason shown is "Size mismatch",
+  and with `--salvage` the restore goes on and lists the remaining files. The backup itself is fine:
+  make room and run the restore again. To be fixed in 1.0.3.
 - **Only the data directory is backed up.** Object storage as primary storage (`objectstore` in
   `config.php`) is not supported: a backup refuses to start there. Folders mounted through the
   External storage app are not in the data directory and are **not included**, without a warning.

docs/DISASTER-RECOVERY.md

@@ -117,7 +117,16 @@ first. If none is better, `--salvage` restores whatever can be read:
 
     occ backup:restore:full offsite <snapshot> --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 <snapshot> --salvage --force
+
 - Files that cannot be read are left out and listed at the end; everything else is restored.
+- **Check the disk first if the reason is "Size mismatch".** In this version a full disk looks like
+  damaged data: the message then points at `--salvage`, and with `--salvage` the restore goes on and
+  lists the remaining files. The backup itself is fine: make room and run the restore again as in
+  step 8, without `--salvage` unless the backup is damaged as well. To be fixed in 1.0.3.
 - 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
   and config of the backup go to a folder of their own in the data directory,