Skip to content

1.0.2

Choose a tag to compare

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

Faster and more robust full restores, and a way to get back what can be read from a damaged backup. Nothing changes in your backups or settings.

Added

  • --salvage for occ backup:restore and occ backup:restore:full: files that cannot be read are left out and listed, everything else is restored (exit code 2).
  • A warning on the admin page and in occ backup:status when background jobs do not run on a system cron. Without one, a backup started with "Back up now" moves on while the NG Backup page stays open (#13).
  • The trash of restore points has a tab of its own, "Bin".

Changed

  • Full restores from S3 read ahead, and over SMB in larger reads. Reading the index over SMB takes fewer round trips.
  • A full restore that stopped goes on where it was (--force): files already in place are left.
  • A backup in its database phase shows how far it is.

Fixed

  • A full restore over SMB could hang at 100% CPU when the connection dropped.
  • A restore that stops because a file is gone from the location now points at --salvage.
  • Smaller fixes, see CHANGELOG.md.

Tested with a full disaster recovery of about 1 TB over SMB, see the README.

Known issue: empty folders are not backed up or restored; to be fixed in 1.0.3 (#27).

Assets 4
Loading