Scheduled BorgBackup failing after update to AIO v12.6.0 Beta

[vawaver]

Bug Report: Scheduled BorgBackup failing after update to AIO v12.6.0 Beta

Description:

Since updating Nextcloud AIO to v12.6.0 (Beta channel), the automated daily BorgBackup has stopped working. The backup process does not trigger automatically at the scheduled time, forcing me to start it manually.

Steps to reproduce:

1. Switch to the Beta channel.

2. Update to AIO v12.6.0 Beta

3. Observe that the automated daily backup is not triggered at the scheduled time.

Expected behavior:

The BorgBackup should run automatically every day at the configured time.

Actual behavior:

Automated backups are not triggered. Only manual backups work.

Additional context:

• I have verified that the backup schedule settings remained intact after the update; the scheduled time is still correctly saved and did not need to be re-entered.

• I am planning to test whether this issue is caused by the ClamAV container, which I re-enabled at the same time I switched to the Beta channel. I will update this post once I have tested if the automated backup works with ClamAV disabled.

Environment:

• Nextcloud AIO Version: 12.6.0 Beta

• Channel: Beta

• OS: Ubuntu 24.04.3 LTS (Running as a Proxmox VM)

• Hardware Resources: 16 GB RAM / 12 CPU Threads

• Backup: Integrated BorgBackup

[szaimen]

Hi, please report this to GitHub · Where software is built

[vawaver]

Consider it done, buddy!

[szaimen]

Lets continue in Scheduled BorgBackup failing after update to AIO v12.6.0 Beta · Issue #7533 · nextcloud/all-in-one · GitHub

[vawaver]

Feedback: Issue resolved in v12.6.1

I can confirm that the issue has been resolved with the release of v12.6.1 Beta.
After updating, the automated daily BorgBackup is once again triggering and running without any problems.

Glad for the quick fix!

Environment tested:

• Nextcloud AIO Version: 12.6.1 Beta
• OS: Ubuntu 24.04.3 LTS (Proxmox VM)