• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue problem on one table => no database backup?

sebgonzes

Silver Pleskian
Hello

On our servers, we have always an daily plesk backup incremental.
In some case, some tables of an database are corrupt (wordfence is dirty on this sometime) and seem that database backup fail :

Unable to make database dump. Error: Failed to exec mysqldump: Exit code: 2:
mysqldump: Got error: 1146: "Table 'bdd.wp_wfNet404s' doesn't exist" when using LOCK TABLES

Is there some way to "just" not backup this table but still have an backup of the other tables?
 
There is no way to backup and restore the database partially. If for some reason the database cannot be correctly backed up, then the entire backup will fail.
 
There is no way to backup and restore the database partially. If for some reason the database cannot be correctly backed up, then the entire backup will fail.
Ok for this point, other thing is that we not recieve in this case an backup fail message and only have an warning message in plesk backup utility, it's not easy to detect problem in case having a lot of server, is there some way to custom mail notificacion of error?
 
Back
Top