Article ID: 6194, created on Mar 25, 2009, last review on Jun 17, 2016

  • Applies to:
  • Plesk 12.5 for Linux
  • Plesk 12.0 for Linux
  • Plesk 11.0 for Linux
  • Plesk 11.5 for Linux


Scheduled backup is configured to begin at a specified time Backup Manager -> Scheduled Backup Settings -> Start backup creation at (HH:mm).

However, creation of the backup is not started at the time when it was indicated. Why?


The problem may be:

  1. Incorrect time for backup creation start

  2. Incorrect creation time shown in backup information.

    • Please see article [Info] Incorrect "Creation time" is shown in backup information for details about incorrect creation date shown in backup information.

    • Creation of scheduled backup is started the next time utility backupmng is executed if the scheduled period passed since the time of the latest backup creation. See details below:

    According to the Plesk database, the scheduled backup for the server has the following configuration:

     mysql> select obj_id, obj_type, last, period, active, backup_time from BackupsScheduled where obj_type='server';
     | obj_id | obj_type |      last           | period | active | backup_time |
     |      1 | server   | 2009-02-25 00:00:00 |  86400 | true   | 06:30:00    |
     1 row in set (0.00 sec)

The backup task is executed by Plesk utility backupmng that is launched from root crontab:

    # crontab -l
    1,16,31,46      *       *       *       *       /opt/psa/admin/sbin/backupmng >/dev/null 2>&1

The utility compares values of psa.BackupsScheduled.last and psa.BackupsScheduled.period in Plesk database, then starts backup if current time is more than (BackupsScheduled.last + BackupsScheduled.period), not in time set in BackupsScheduled.backup_time as it is configured.

If there are a lot backup tasks scheduled at the same time then adjust 'Maximum number of simultaneously running scheduled backup processes' in Tools & Settings > Backup settings to appropriate value. By default it is set to '2'. Mind that backup is resource-consuming task and setting this value to a high number may cause downtime.


As a workaround you can empty the value of psa.BackupsScheduled.last for particular backup task.

mysql> begin;
mysql> update psa.BackupsScheduled set last='' where obj_id=1;
mysql> commit;

Search Words


backup schedules process

Too many links: '/usr/local/psa/PMM/logs/backup

scheduled backup not workign

backup not working

backups doesnt created

Scheduled backup doesnt created

not creating backups daily

e0aff7830fa22f92062ee4db78133079 caea8340e2d186a540518d08602aa065 a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c 29d1e90fd304f01e6420fbe60f66f838 2a5151f57629129e26ff206d171fbb5f e335d9adf7edffca6a8af8039031a4c7 aea4cd7bfd353ad7a1341a257ad4724a 0a53c5a9ca65a74d37ef5c5eaeb55d7f 01bc4c8cf5b7f01f815a7ada004154a2 742559b1631652fadd74764ae8be475e

Email subscription for changes to this article
Save as PDF