Article ID: 126481, created on Aug 7, 2015, last review on Aug 7, 2015

  • Applies to:
  • Plesk 11.0 for Linux


"Unable to resolve all conflicts" while trying to restore domain backup from CLI:

/usr/local/psa/bin/pleskrestore --restore /var/lib/psa/dumps/domains/<domain_name>/<damain_backup>.xml -level domains
Unable to resolve all conflicts

While trying to restore from Plesk GUI restoration doesn't go beyond IP mapping page.

Several conflicts in output xml log if aforementioned command run with -verbose option:

   <node name="domain">
     <attribute name="id" value="123"/>
     <attribute name="guid" value="e7a6d663-7295-43ad-99b3-9e6a882a678d"/>
     <attribute name="owner-guid" value="f3335088-4627-4bdf-80c1-60b80490be0e"/>
     <attribute name="name" value=""/>
   <node name="phosting">
     <attribute name="guid" value="e7a6d663-7295-43ad-99b3-9e6a882a678d_phosting"/>
     <attribute name="owner-guid" value="e7a6d663-7295-43ad-99b3-9e6a882a678d"/>


Software issue with internal ID PPPM-569. One of the users in database has &(ampersand) symbol in its password.


Try to execute restore command once more(this time with -conflicts-resolution flag):

/usr/local/psa/bin/pleskrestore --restore /var/lib/psa/dumps/domains/<domain_name>/<damain_backup>.xml -level domains -conflicts-resolution conflict_resolution_rules

The error output should refer to a string which contains faulty password. Now you have to change this user's password in Plesk GUI, file of the corresponding domain and the dump.xml file of previously created backup.

  1. Navigate to Domains > find %domain% > Websites&Domains tab> Databases > %domain% > %user% > New Password

  2. Copy password from Step 1 to $database_password field of/var/www/vhosts/%domain%/httpdocs/core/config/ file

  3. Find and replace the old one in /usr/local/psa/PMM/rsessions/%session_id%/dump.xml with the new one

  4. Restore the backup:

    /usr/local/psa/bin/pleskrestore --restore /var/lib/psa/dumps/domains/<domain_name>/domain_backup.xml -level domains -verbose

Search Words

ampersand bug

unable to resolve all conflicts


unsupported password

domain doesn't restore


ampersand passwords

29d1e90fd304f01e6420fbe60f66f838 56797cefb1efc9130f7c48a7d1db0f0c a914db3fdc7a53ddcfd1b2db8f5a1b9c aea4cd7bfd353ad7a1341a257ad4724a 0a53c5a9ca65a74d37ef5c5eaeb55d7f

Email subscription for changes to this article
Save as PDF