-
1.0.2
StableCI / unit (8.2) (push) Has been cancelledCI / unit (8.3) (push) Has been cancelledCI / unit (8.4) (push) Has been cancelledCI / psalm (push) Has been cancelledCI / frontend (push) Has been cancelledCI / integration (mariadb, 32) (push) Has been cancelledCI / integration (mariadb, 33) (push) Has been cancelledCI / integration (mariadb, 34) (push) Has been cancelledCI / integration (mariadb, 35) (push) Has been cancelledCI / integration (pgsql, 32) (push) Has been cancelledCI / integration (pgsql, 33) (push) Has been cancelledCI / integration (pgsql, 34) (push) Has been cancelledCI / integration (pgsql, 35) (push) Has been cancelledCI / integration (sqlite, 32) (push) Has been cancelledCI / integration (sqlite, 33) (push) Has been cancelledCI / integration (sqlite, 34) (push) Has been cancelledCI / integration (sqlite, 35) (push) Has been cancelledCI / integration-targets (push) Has been cancelledCI / integration-user (32) (push) Has been cancelledCI / integration-user (33) (push) Has been cancelledCI / integration-user (34) (push) Has been cancelledCI / integration-user (35) (push) Has been cancelledCI / integration-full-restore (push) Has been cancelledreleased this
2026-11-06 11:29:18 +01:00 | 38 commits to main since this releaseFaster 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
--salvageforocc backup:restoreandocc 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:statuswhen 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).
Downloads