Plesk 18.0.28 update 3
CentOS Linux 7.8.2003
I have daily scheduled backups running at 01:15 in the morning but the last scheduled backup to run was on the 2nd July before the 18.0.28 Update 1 ran which may or may not be coincidental.
I have checked for stuck jobs of which there were none, I have checked the plesk-backup-manager-task & its permissions which were fine but deleted & recreated with the correct permissions, rebooted the server, changed the permitters of the backup ie time, local storage only, remote storage only, what it backs up etc but nothing seems to kick off the backup.
Manual backups run fine.
When I run:
grep backupmng /var/log/cron via ssh
i get
Jul 19 03:37:01 anim CROND[21689]: (root) CMD ([ -x /usr/local/psa/admin/sbin/backupmng ] && /usr/local/psa/admin/sbin/backupmng >/dev/null 2>&1)
& this seems to run every 15 minutes but I have to admit I have no idea what it means.
CentOS Linux 7.8.2003
I have daily scheduled backups running at 01:15 in the morning but the last scheduled backup to run was on the 2nd July before the 18.0.28 Update 1 ran which may or may not be coincidental.
I have checked for stuck jobs of which there were none, I have checked the plesk-backup-manager-task & its permissions which were fine but deleted & recreated with the correct permissions, rebooted the server, changed the permitters of the backup ie time, local storage only, remote storage only, what it backs up etc but nothing seems to kick off the backup.
Manual backups run fine.
When I run:
grep backupmng /var/log/cron via ssh
i get
Jul 19 03:37:01 anim CROND[21689]: (root) CMD ([ -x /usr/local/psa/admin/sbin/backupmng ] && /usr/local/psa/admin/sbin/backupmng >/dev/null 2>&1)
& this seems to run every 15 minutes but I have to admit I have no idea what it means.
Last edited: