Backuply Server 1.3.9 Launched

Hi,

We have released Backuply Server version 1.3.9
The following are the list of features, improvements and bug fixes :

- [Feature] OS Backups - BTRFS/ZFS snapshots and ReaR.

- [Feature] backuply --reverify CLI utility added to check that the backups of the backup records actually exist on the backup location (local and remote) and to remove the records of the backups which are missing. Check backuply --reverify -h or --help.

- [Improvement] Borg error message improved. Earlier, if Borg was broken, it showed that Borg is not installed. Now it says Borg is not installed or not working.

- [Improvement] Borg install check improved. Earlier the local check only looked for the Borg binary. Now it runs borg --version to verify that Borg is installed and working. A failed Borg install is retried.

- [Improvement] Google Drive quota is checked before the upload starts, temporary errors (5xx / connection errors) are retried by resuming the upload, the actual Google Drive error message is shown, and errors while uploading the last part of the file now fail the backup instead of being missed.

- [Improvement] Remote upload errors improved for account and directory backups. The "Failed to open streams for uploading" error now shows the reason (e.g. Drive quota exceeded, no shell access for SFTP).

- [Improvement] Reading files from S3 (restore / download) now fetches 8 MB per request instead of PHP small 8 KB pieces, which makes it much faster. Each open file now keeps track of its own read position: earlier all open S3 files shared one.

- [Improvement] When an end user restores selected files, the ownership of the restored files is now corrected in one run of the fix_ownership CLI instead of once per file, which is much faster when many files are restored.

- [Improvement] install_packages CLI will not generate an alert if the OS does not provide that package. Existing alerts for such packages are dismissed.

- [Bug-fix] Improved reading of S3 backup locations. PHP memory was exhausted when the S3 backup location had a huge number of files, because the S3 code loaded every object of the location.

- [Bug-fix] On EL7 servers, Borg failed on files and folders with non-ASCII names, as the panel strips the locale and Python < 3.7 then uses ASCII. Borg now always runs with a UTF-8 locale.

- [Bug-fix] If /tmp is noexec, Borg could not unpack its libraries and the backup failed with missing Borg libs. This is fixed.

- [Bug-fix] Incremental backup check fixed for free license users. The Add Backup page allowed free license users to create rsync, restic and Borg incremental backup jobs.

- [Bug-fix] The cached connection of SSH/SFTP backup servers is now checked to see if it is still connected. If the remote server dropped it, Backuply reconnects instead of failing.

- [Bug-fix] Browsing (mounting) a restic / Borg backup stored on an SSH server used the SSH connection shared with the backups of that server. When a backup to that server finished, it closed the shared connection and the mounted backup stopped working. Mounts now use a connection of their own.

- [Bug-fix] Durring Account and directory backups, the last part of the file is uploaded when the upload stream is closed, and errors at that point were missed for all remote backup locations. Now such errors fail the backup.

- [Bug-fix] On cPanel servers, the nobody user was being backed up. Now nobody, root and system users are ignored in the users list.

- [Bug-fix] On cPanel servers, the timezone was not reflected in Backuply task logs and UI. This is fixed now.

- [Bug-fix] On DirectAdmin servers, long DNS TXT records (e.g. DKIM) were backed up with an opening parenthesis at the start and only the first part of the record. Now the full record is backed up.

- [Bug-fix] Admin file browser (Directories, Add Directory Backup and OS backup browsing) now shows file and folder names as plain text. Names containing characters like < or & were shown wrongly.

Launched in RELEASE : (29-10-2026)

We are constantly working on improving Backuply Server, if you have any suggestion or feedback, write us at [email protected]

Regards,
Backuply Team