Devolutions Server scheduled backup failed

Hello,

Thanks for the details — the fact that the .bak file is created but only manual backups get zipped is a strong pointer to account permissions rather than a bug.

Devolutions Server backups involve a few different accounts. SQL Server always writes the initial .bak file on its own. From there, whichever account triggered the backup is responsible for reading that .bak, compressing it into the .zip, and deleting the original: for a manual "Backup Now," that's the IIS application pool identity; for a scheduled backup, that's the account running the Devolutions Server Scheduler Windows service. If the Scheduler service account doesn't have Modify permission (read, write, delete) on the destination folder, this step fails quietly — you get the .bak, but never the .zip.

Could you check the following on the Devolutions Server machine:

1. Open Services (services.msc) and note the account the "Devolutions Server Scheduler" service runs under.
2. Open the Security tab on your backup destination folder and confirm that account has Modify permission — the same level your IIS application pool identity already has, since manual backups work fine.

A very common cause here is the Scheduler service still running under a built-in account like Local Service or Network Service, which has very limited file and network access. Switching it to a dedicated account with Modify rights on the backup folder usually resolves this right away.

Our documentation on backup account requirements has more detail: https://docs.devolutions.net/server/web-interface/administration/backup/backup-manager/#account-permissions-and-other-considerations

Let us know what you find, and if it's still failing after adjusting the permissions we can enable Scheduler logging to look closer.

Best regards,
Stephan

ok , your suggestion fixed the issue.