Applicable to:
- Plesk for Linux
Symptoms
- Scheduled backup does not start at the scheduled time
-
Backup manager cron task is missing / has incorrect permissions (not 0644) / has incorrect content or is empty:
# ls /etc/cron.d/plesk-backup-manager-task
ls: cannot access /etc/cron.d/plesk-backup-manager-task: No such file or directory# stat /etc/cron.d/plesk-backup-manager-task | grep Access
Access: (0400-r--------) Uid: ( 0/ root) Gid: ( 0/ root)# cat /etc/cron.d/plesk-backup-manager-task
(empty output)
Cause
Corrupted backup manager cron task.
Resolution
-
Connect to the server via SSH
Note: if direct SSH access to the server is not possible, contact server administrator for further assistance.
-
Create backup manager cron task file if it does not exist:
# touch /etc/cron.d/plesk-backup-manager-task
-
Set correct permissions and ownership:
# chown root.root /etc/cron.d/plesk-backup-manager-task && chmod 0644 /etc/cron.d/plesk-backup-manager-task
-
Set the correct content:
For CentOS/RedHat/CloudLinuxEdit the file
/etc/cron.d/plesk-backup-manager-taskand add the line below at the end:5,20,35,50 * * * * root [ -x /usr/local/psa/admin/sbin/backupmng ] && /usr/local/psa/admin/sbin/backupmng >/dev/null 2>&1
For Debian/UbuntuEdit the file
/etc/cron.d/plesk-backup-manager-taskand add the line below at the end:5,20,35,50 * * * * root [ -x /opt/psa/admin/sbin/backupmng ] && /opt/psa/admin/sbin/backupmng >/dev/null 2>&1
Comments
Please sign in to leave a comment.