Scheduled backup: manual backup works fine, scheduled backup fails

Operating system: Debian
OS version: 10 Buster
Virtualmin: 1.971

Issue can be found in older threads, but has never been answered, e.g. here…

In brief: Backups triggered via GUI work fine, cron’d backups stop [somewhere], giving the following error-email:

Subject: Failed backup of Virtualmin on ####.net to local file /dumps
Backup failed! See the progress output above for the reason why. Total backup time was 00 minutes, >23 seconds.

Virtual servers that failed :
*****.com
Sent by Virtualmin at: https://#######.net:10000

Creating backup for virtual server #######.com …
Copying virtual server configuration …
… done

Saving mail aliases …
… done

Saving mail and FTP users …
… done

Backing up mail and FTP user Cron jobs …
… none to backup

Copying Apache aliases …
… done

Creating TAR file of home directory …
… done

… completed in 17 seconds

Creating backup for virtual server #####.com …
Copying virtual server configuration …
… done

Backing up Cron jobs …
… none defined.

Saving mail aliases …
… done

Saving mail and FTP users …
… done

Backing up mail and FTP user Cron jobs …
… none to backup

Copying Apache virtual host configuration …
… done

Copying Apache log files …
… done

Copying Webalizer configuration files …
… done

Copying Logrotate configuration …
… done

Copying Procmail and SpamAssassin configuration files …
… done

Backing up AWstats configuration file …
… done

Backing up PowerDNS database entries for domain …
… done

I deleted the CRON and set up a new one: exactly the same error/behaviour.
What could be the cause?
How to I get cron’d backups to work?
Unfortunately there seems to be no “progress output above for the reason why”

Cheers :slight_smile:
H.

@Hans,

You can create scheduled backups via the GUI, it doesn’t JUST support one-time backups.

Best Regards,
Peter Knowles | TPN Solutions

Need Professional, Affordable Tech Support – Check Out https://tpnassist.com

@Hans its there and its telling you :slight_smile: amend your script and you should be fine…

1 Like

Yes, that’s what I did! :slight_smile: And it’s those scheduled backups which I (created via GUI) used since years on many others servers, who now fail on this box :slight_smile:
One-Time-Backups though work flawlessly.

When it says “none defined” or “none to backup”, this just means that a certain feature of this particular instance/host/server/client which virtualmin’s backup-cron-job is trying to back-up, is “not defined” hence there is “none to backup”.
The message refers only to that particular feature (in this case “mail and FTP user Cron jobs” of virtual server #####.com), not the backup-cron-job :slight_smile: