Article ID: 9343, created on Nov 22, 2010, last review on Mar 6, 2015

  • Applies to:
  • Plesk 9.x for Windows

Symptoms

You can see the following errors when the Parallels Plesk backup convert utility pre9-backup-convert.exe creates an incorrect backup. For example:

1. Convert a Plesk backup from a Plesk 8.x version with the following:
C:\Parallels\Plesk\admin\bin>pre9-backup-convert.exe --source=C:\Users\Administrator\Desktop\psa-8.1-BHL.BHL-2010.03.29.psa --destination=c:\Parallels\Plesk\

Created dump:
converted_info_1003290633.xml


2. Check the converted backup with the following:
C:\Parallels\Plesk\bin>pleskrestore.exe --check-backup "C:\Parallels\Plesk\Backup\converted_info_1003290633.xml"

Backup file has wrong format

3. If you try to validate the backup dump, you receive the following errors:
C:\Parallels\Plesk\bin>%xmllint% --noout --schema C:\Parallels\Plesk\PMM\plesk.xsd C:\Parallels\Plesk\Backup\converted_info_1003290633.xml

file:///C:/Parallels/Plesk/Backup/converted_info_1003290633.xml:1424: element redirect: Schemas validity error : Element 'redirect', attribute 'enabled': [facet 'enumeration'] The value '' is not an element of the set {'true', 'false'}.
file:///C:/Parallels/Plesk/Backup/converted_info_1003290633.xml:1424: element redirect: Schemas validity error : Element 'redirect', attribute 'enabled': '' is not a valid value of the local atomic type.
file:///C:/Parallels/Plesk/Backup/converted_info_1003290633.xml:2159: element redirect: Schemas validity error : Element 'redirect', attribute 'enabled': [facet 'enumeration'] The value '' is not an element of the set {'true', 'false'}.
file:///C:/Parallels/Plesk/Backup/converted_info_1003290633.xml:2159: element redirect: Schemas validity error : Element 'redirect', attribute 'enabled': '' is not a valid value of the local atomic type.
file:///C:/Parallels/Plesk/Backup/converted_info_1003290633.xml:3569: element spamassassin: Schemas validity error : Element 'spamassassin': This element is not expected. Expected is one of ( grey-listing, virusfilter ).
C:\Parallels\Plesk\Backup\converted_info_1003290633.xml fails to validate



Resolution

Note: Carefully read the article How to access the Plesk database before applying the workarounds described below.

An issue with <redirect> is caused by old Plesk 8.x versions, where an empty mail.redirect parameter is used in the Plesk database for the false value.

You can fix the <redirect> issue with the following SQL query before backing up a Plesk 8.x server:
update mail set redirect = 'false' where redirect = '';


An issue with <spamassassin> is caused by old Plesk 8.x versions, where, in some cases, mail-wide spam settings are not deleted from the sa_conf table on mail removal, i.e., the sa_conf table contains records for removed emails.

You can see this in the original Plesk 8.x dump:
<server>
...
    <sa_confs>
      <sa_conf id="219" mailname="" flt_enabled="serv" rw_subject_tag="*****SPAM*****" hits_required="4" spam_action="save">
        <sa_param id="156" conf_id="219" name="report_text" value=""/>
        <sa_param id="157" conf_id="219" name="max_mail" value="204800"/>
        <sa_param id="158" conf_id="219" name="max_spam_threads" value="1"/>
      </sa_conf>
      <sa_conf id="220" mailname="email@domain.com" flt_enabled="" rw_subject_tag="*****SPAM*****" hits_required="7" spam
    </sa_confs>
...


However, the dump doesn't contain the mailname email@domain.com.

You can fix the <spamassassin> issue with the following SQL query before backing up the Plesk 8.x version:
delete from sa_conf where mailname = '<removed mail>';

where <removed mail>  is the name of the removed email address.

You can also use the attached fix, which allows you to restore an incorrectly created backup. The attached pmmcli.py has a --skip-xsd option for disabling dump validation. To fix the installation, simply replace the file in C:\Parallels\Plesk\admin\share\pmmcli\.

Note: Restore a backup with this method at your own risk.

Attachments

aac4a8fcd879de03758354e15495d69a a914db3fdc7a53ddcfd1b2db8f5a1b9c 85a92ca67f2200d36506862eaa6ed6b8 56797cefb1efc9130f7c48a7d1db0f0c

Email subscription for changes to this article
Save as PDF