O.k., so we have ruled out issues with crontab and with the configuration files as well as issues with backupmng and the backup job itself. Your backup is scheduled, it is active, the system is checking for active, scheduled backups every 15 minutes, no errors are logged - and it is still not running the backup?
Very vague, but in my opinion the only cause that is left is a broken database table or maybe a wrong field format. Could it be possible that at the time when the backup stopped you made changes to your MySQL/MariaDB installation on your server, e.g. made a custom update from MySQL 5.5 to MySQL 5.7?
If I was you, next I'd probably take a closer look at the BackupsScheduled table in the database:
# plesk db
MariaDB [psa]> select * from BackupsScheduled;
should display your scheduled backup (maybe along with others). Is it there? Is the "active" field of the dataset "true"?
Then I'd check whether all fields have the format they ought to have:
MariaDB [psa]> describe BackupsScheduled;
should yield:
Code:
+----------------------+---------------------------------------------------------------------------------------------+------+-----+------------------------------+----------------+
| Field | Type | Null | Key | Default | Extra |
+----------------------+---------------------------------------------------------------------------------------------+------+-----+------------------------------+----------------+
| id | int(10) unsigned | NO | PRI | NULL | auto_increment |
| obj_id | int(10) unsigned | NO | | 0 | |
| obj_type | enum('server','reseller','client','domain') | NO | | NULL | |
| repository | enum('local','ftp') | NO | | local | |
| last | datetime | YES | | NULL | |
| period | int(10) unsigned | NO | | 0 | |
| active | enum('false','true') | NO | | NULL | |
| processed | enum('false','true') | NO | | NULL | |
| rotation | int(11) | NO | | 0 | |
| prefix | varchar(255) | YES | | NULL | |
| email | varchar(255) | YES | | NULL | |
| split_size | bigint(20) unsigned | NO | | 0 | |
| suspend | enum('false','true') | NO | | false | |
| with_content | enum('false','true') | NO | | true | |
| backup_day | int(10) unsigned | NO | | 0 | |
| backup_time | varchar(8) | NO | | 00:00:00 | |
| content_type | enum('backup_content_all_at_domain','backup_content_vhost_only','backup_content_mail_only') | NO | | backup_content_all_at_domain | |
| full_backup_period | int(11) unsigned | NO | | 0 | |
| mssql_native_backup | int(1) | NO | | 1 | |
| backupExcludeFilesId | int(10) unsigned | YES | | NULL | |
| backupExcludeLogs | int(1) | NO | | 0 | |
+----------------------+---------------------------------------------------------------------------------------------+------+-----+------------------------------+----------------+
21 rows in set (0.00 sec)
(Compare yours against this table.)
If all that is fine, matches the structure, then I am out of ideas and suggest to
- run # plesk repair installation
- open a support ticket with Plesk support