• 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.

Restore not possible

P

pro---studio

Guest
Hi,

I need urgent help:

I did a backup of my domains with

/usr/local/psa/bin/pleskbackup all /srv/backup/backup.bkp

I reinstalled the server with the same OS (Suse 10.2 and Plesk) and tried to restore the backup. That is not possible:

/usr/local/psa/bin/pleskrestore --restore psa-backup-190208.bkp -level all -map map.txt
WARNING: Backup file has wrong signature for this server
------------------------------------------------------------------------
Restore has been started
------------------------------------------------------------------------
Vergangene Zeit: 00:00:00
Vergangene Zeit: 00:00:05Failed validation of the document with external DTD /usr/local/psa/PMM/plesk.dtd. The errors are: Value "info_not_required" for attribute name of pinfo is not among the enumerated set.

Anyone with a solution to this? Need it urgent because the server and the domains are not reachable anymore. And of course the Email configration is not set.

Can someone please help me?

Thank you!
 
i don't have a solution but i guess this message can be ignored:

WARNING: Backup file has wrong signature for this server

because i got it too as i restored my backup and it went (mostly) ok.

maybe try to not restore "all" but client after client or single domains.
 
I tried that too, but had no luck.

Even if I try to restore a single domain I get the same error as posted above.

Any solution?
 
hi. the problem is original database has corrupted lines, presumably template, client, domain limits or permissions. they all have trails with whitespaces. this fact influence on the backup can be checked like this:
# zgrep '<permission.*"false[[:space:]]' [backup file] | head -1 | hexdump -bc

how to fix now: try to unzip the file and strip all spaces, then zip back.

the only way to avoid this in future - strip excessive whitespaces from the database. no idea how do they get there, most probably after buggy conversion latin1->utf-8 and reverse
 
I beg to differ

Having a node with a name of 'info_not_required' and a value of 'true' does not a whitespace issue make.
However, simply removing that line from the dump makes the restore work ;-)
Enjoy.
 
Back
Top