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

17 Releases 18 Tags

RSS Feed
  • v1.0.3 f81c5e13e9
    Compare

    1.0.3
    CI / unit (8.2) (push) Has been cancelled
    Details
    CI / unit (8.3) (push) Has been cancelled
    Details
    CI / unit (8.4) (push) Has been cancelled
    Details
    CI / psalm (push) Has been cancelled
    Details
    CI / frontend (push) Has been cancelled
    Details
    CI / integration (mariadb, 32) (push) Has been cancelled
    Details
    CI / integration (mariadb, 33) (push) Has been cancelled
    Details
    CI / integration (mariadb, 34) (push) Has been cancelled
    Details
    CI / integration (mariadb, 35) (push) Has been cancelled
    Details
    CI / integration (pgsql, 32) (push) Has been cancelled
    Details
    CI / integration (pgsql, 33) (push) Has been cancelled
    Details
    CI / integration (pgsql, 34) (push) Has been cancelled
    Details
    CI / integration (pgsql, 35) (push) Has been cancelled
    Details
    CI / integration (sqlite, 32) (push) Has been cancelled
    Details
    CI / integration (sqlite, 33) (push) Has been cancelled
    Details
    CI / integration (sqlite, 34) (push) Has been cancelled
    Details
    CI / integration (sqlite, 35) (push) Has been cancelled
    Details
    CI / integration-targets (push) Has been cancelled
    Details
    CI / integration-user (32) (push) Has been cancelled
    Details
    CI / integration-user (33) (push) Has been cancelled
    Details
    CI / integration-user (34) (push) Has been cancelled
    Details
    CI / integration-user (35) (push) Has been cancelled
    Details
    CI / integration-full-restore (push) Has been cancelled
    Details
    Stable

    dillard released this 2026-11-06 20:29:12 +01:00 | 21 commits to main since this release

    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.

    Downloads