Article ID: 6080, created on Nov 24, 2013, last review on Aug 12, 2014

  • Applies to:
  • Plesk Automation 11.5
  • Plesk 12.5 for Linux
  • Plesk 12.0 for Linux
  • Plesk 11.0 for Linux
  • Plesk 11.5 for Linux
  • Plesk 10.4 for Linux/Unix
  • Plesk 12.5 for Windows
  • Plesk 12.0 for Windows
  • Plesk 11.0 for Windows
  • Plesk 11.5 for Windows


The migration of Plesk data with Plesk Backup Manager is performed according to these articles:

[How to] How can I migrate objects from Parallels Plesk Panel versions 7.5 and 8.x to Parallels Plesk Panel 9?
[How to] How can I migrate Plesk 9 using Backup Manager?

A new backup is shown on the Tools & Settings > Backup Manager page. However, it is marked with a red circle, and the following pop-up is shown when you hover the mouse pointer over the circle:

This is not a valid backup. Data cannot be restored from this file. 


The backup contains invalid records that do not follow the requirements of the current Parallels Plesk Panel version. You must validate the backup according to the current Plesk schema and remove/replace any incorrect records.


If, for example, the name of the invalid backup is 0902260453, you may see files like backup_info_0902260453, converted_info_0902260453, etc., on the Tools & Settings > Backup Manager page in Parallels Plesk Panel. You may validate the backup using the schema "/usr/local/psa/PMM/plesk.xsd". The file is included in the package "psa-migration-manager". Verify that it is installed.

  1. In the backup directory, find all <info>.xml backup metadata files that contain 0902260453.

    ~# find /var/lib/psa/dumps/ -name '*info_0902260453.xml'
  2. Verify the backup files first:

    # cd /var/lib/psa/dumps
    # /usr/local/psa/admin/sbin/backup_sign verify backup_info_0902260453.xml > backup_info_0902260453-verified.xml
  3. Then format them for convenience:

    # xmllint --format backup_info_0902260453-verified.xml > backup_info_0902260453-formatted.xml

    After this command the XML files will be formatted in a user-friendly way which will make working with them much easier.

  4. And finally, use the xmllint utility to validate them. For example:

    ~# cd /usr/bin
    ~# /usr/bin/xmllint --noout --schema /usr/local/psa/PMM/plesk.xsd backup_info_0902260453-formatted.xml
  5. Correct the misconfiguration in invalid xml files, and delete the status cache file status_WRONG-FORMAT from the directory .discovered. If the status file is missing, it will be regenerated when you open Tools & Settings > Backup Manager page.

    After invalid xml files are corrected and the status file status_WRONG-FORMAT is removed, the backup should be shown as valid on Tools & Settings > Backup Manager.

a914db3fdc7a53ddcfd1b2db8f5a1b9c 29d1e90fd304f01e6420fbe60f66f838 56797cefb1efc9130f7c48a7d1db0f0c 0a53c5a9ca65a74d37ef5c5eaeb55d7f aea4cd7bfd353ad7a1341a257ad4724a e8756e9388aeca36710ac39e739b2b37 dd0611b6086474193d9bf78e2b293040 33a70544d00d562bbc5b17762c4ed2b3 e0aff7830fa22f92062ee4db78133079 85a92ca67f2200d36506862eaa6ed6b8 46a8e394d6fa13134808921036a34da8 bd7fc88cf1b01f097749ae6f87272128 01bc4c8cf5b7f01f815a7ada004154a2 2a5151f57629129e26ff206d171fbb5f e335d9adf7edffca6a8af8039031a4c7 caea8340e2d186a540518d08602aa065 742559b1631652fadd74764ae8be475e ed7be2b984f9c27de1d2dc349dc19c6d a766cea0c28e23e978fa78ef81918ab8 8b661cab116c79dbe6c4ac5bbdf1c8cb 514af229ae32522202a910a2649c80fb

Email subscription for changes to this article