A restore that stops at a file gone from the location points at --salvage; test a full restore with a damaged and a missing pack

The DR test of 1.0.2 over SMB is done: result in PLAN, empty folders as a known issue (#27).
This commit is contained in:
2026-11-06 10:27:41 +01:00
parent 74bfa7052f
commit b625fe7666
7 changed files with 114 additions and 4 deletions
+5
View File
@@ -50,6 +50,11 @@ shown under 1.0.0. The git tag of a release candidate goes after the date.
- `occ backup:target:add` only estimates the time left for reading the index once enough of it
is in. The first file also carries the time to connect, which made it say "about 642 min left"
for something done within a minute.
- A restore that stops because a file is gone from the location now points at `--salvage`, as it
already did for damaged data.
### Known issues
- Empty folders are not backed up or restored; to be fixed in 1.0.3 (#27).
## [1.0.1] - 2026-11-01