Ensembia/nextcloud-ng_backup
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 17 Wiki Activity

Merge remote-tracking branch 'github/main' into 1.0.3

Browse Source
This commit is contained in:
Dillard Blom
2026-11-06 12:23:09 +01:00
parent e9592cb6c6 46e0186f35
commit ce40053cec
3 changed files with 15 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGELOG.md
+3
View File
@@ -55,6 +55,9 @@ shown under 1.0.0. The git tag of a release candidate goes after the date.
### Known issues ### Known issues
- Empty folders are not backed up or restored; to be fixed in 1.0.3 (#27). - 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 ## [1.0.1] - 2026-11-01
README.md
+3
View File
@@ -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 - **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 not restored. To be fixed in 1.0.3
([#27](https://github.com/dillardblom/ng_backup/issues/27)). ([#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 - **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 `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. External storage app are not in the data directory and are **not included**, without a warning.
docs/DISASTER-RECOVERY.md
+9
View File
@@ -117,7 +117,16 @@ first. If none is better, `--salvage` restores whatever can be read:
occ backup:restore:full offsite <snapshot> --install-apps --salvage 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. - 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 - 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 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, and config of the backup go to a folder of their own in the data directory,