• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

Problem with full PSA backup restore

calderwood

Regular Pleskian
I upgraded to 8.4, the server failed, so I re-formated server and re-installed a fresh OS with PSA 8.3 the did a full restore using the most recent backup. Do I need to update to 8.4 again before restoring as I got these errors:

WARNING: Backup file has wrong signature for this server

WARNING! Restore with "-level server" switch brings server to exactly the same
state, as was saved in backup file. All objects, not presented in the backup
file (clients or domains) will be deleted. Proceed? [yes/no]: yes
Failed validation of the document with external DTD /usr/local/psa/PMM/plesk.dtd. The errors are: Element mailsystem content does not follow the DTD, expecting (status , mailuser* , catch-all?), got (status mailuser catch-all domain-keys )No declaration for element domain-keysNo declaration for attribute public-key of element domain-keysNo declaration for attribute private-key of element domain-keysNo declaration for attribute state of element domain-keysElement mailsystem content does not follow the DTD, expecting (status , mailuser* , catch-all?), got (status mailuser mailuser catch-all domain-keys )No declaration for element domain-keysNo declaration for attribute public-key of ....

There is another 3 pages of error messages.
 
Hello!

Looks like the backup was made by Plesk 8.4.

Thanks.
 
Upgrade

Yes I did in fact have to update the system to 8.4 before restoring the files. Of the backups from the last three days, the most recent 8.4 backup was in fact corrupt and the only one that worked was an older 8.3 backup. So whatever happened to the system after updating was captured in the backup files. All seems to be running ok now.
 
Back
Top