• 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 Plesk database crashed - no backups of project databases

EDWERB

New Pleskian
Hey there,

yesterday we had a datacrash of the plesk database. Now Plesk is running. but all the databases of our projects are emty. Our serviceparter didn‘t setup the backup system.

Do anybody have an idea to restore the databases? At the moment the hole database files are lost.

Thanks a lot

Martin
 
Do you have another idea to restore the databases?
If you haven't created backups of client sites and their databases, I'm afraid there is no way to restore them. There is nothing from which it could be made.
 
How did a crash of the database result in a total loss of the db tables? If the database crashes, the files may be corrupted but in many cases can be rolled back/recovered.

Was it a drive/hardware issue? If so, consider sending the drive to a forensics lab if the data is really of importance. But then again, if it was, you'd have backups right?
 
Back
Top