Backuply Server 1.2.8 Launched

Hi,

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

- [Task] Added gzip_level setting for database backup compression.

- [Task] Added max_allowed_packet size setting for MySQL database dumps.

- [Task] Added SFTP timeout setting for SSH/SFTP backup servers. When not set, it defaults to the PHP socket timeout.

- [Improvement] The clean_backups CLI command now supports both --only_count and --only_count=1 arguments.

- [Improvement] Improved rsync flags for backup locations that are mounted and do not support symlinks.

- [Bug-fix] Fixed Transport endpoint is not connected - errors by detecting and automatically unmounting broken FUSE mounts (Restic/Borg/Rsync) before new operations and during cron
 cleanup.
 
- [Bug-fix] Restic updates were incorrectly triggered when the "Disable Restic Updates" setting was enabled. This is now fixed.

- [Bug-fix] On cPanel servers, Backuply chroot environments are now hidden from the host to prevent them from leaking into newly created cPanel users paths.

- [Bug-fix] Fixed restoration of Full type backups created with older versions.

- [Bug-fix] Fixed failure in temporary MySQL user creation during database restoration.

- [Bug-fix] Fixed Selective DB restore failure caused by download issues from the backup location.

- [Bug-fix] Fixed Borg installation checks on remote servers for non-root SSH/SFTP users with restricted shells.

- [Bug-fix] Backup sync from S3 servers was scanning all files recursively. This is now fixed.

- [Bug-fix] Fixed the --exclude_files argument in the backup CLI when passed exclusively in the command.

- [Bug-fix] Fixed backuply --backup_status not showing tasks when the process PID was missing from records.

- [Bug-fix] Fixed MySQL connection recreation failure on cPanel servers after dumping large databases.

- [Bug-fix] Fixed psql not found logs appearing on cPanel servers.

- [Bug-fix] Fixed Backup cron scheduler showing 0 instead of * in certain fields during edits.

- [Bug-fix] Backup jobs for deleted users were not being cleaned up properly and could still run, generating false failure alerts. This is now fixed.

Launched in RELEASE : (11-06-2026)
Launched in STABLE : (11-06-2026)

We are constantly working on improving Backuply Server, if you have any suggestion or feedback, write us at support@backuply.com

Regards,
Backuply Team