Skip to content

1.0.3

Choose a tag to compare

View all tags
@dillardblom dillardblom released this 06 Nov 19:30
· 21 commits to main since this release
v1.0.3
f81c5e1
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Empty folders now come back, and a full disk during a restore no longer looks like a damaged backup. Nothing changes in your settings.

Fixed

  • Empty folders are backed up and restored (#27), in occ backup:restore, occ backup:restore:full and the restore page. They come back from the first backup made with this version; older restore points do not contain them.
  • A full disk, or other trouble writing to the restore directory, stops a restore with a clear message, also with --salvage.
  • A file or folder whose name a restore point cannot hold (a backslash, a control character, not UTF-8) is left out and reported as unreadable. Before, such a name could make a whole restore point unreadable, or make the backup fail.
  • After a restore that was killed and ran again, a backup no longer has to wait up to two hours for its locks.
  • A database restore that fails no longer leaves tables behind that could stop an app's installation later.
  • The Bin tab shows how far it is while it reads the removed restore points, and shows when it cannot read a location.
  • Smaller fixes, see CHANGELOG.md.

Tested with three small full disaster recoveries on Nextcloud 34: as planned, with the restore killed halfway, and with a disk that runs full.

Known limitation: folders with files in them show the time of the restore, not their original modification time. The files keep theirs. On the roadmap.

Assets 4
Loading