• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Cannot restore - conflict error

IanT

Basic Pleskian
Hello,

i am trying to run a restore using -resellers as the parameter however it is saying there is a conflict as the data is from another server with a different IP.

I have created a conflict file but i do not know if this is correct as the restore still fails

<?xml version="1.0" encoding="UTF-8"?>
<resolve-conflicts-task-description>
<conflict-resolution-rules>
<policy>
<timing>
<resolution>
<proceed-with-current/>
</resolution>
</timing>
<resource-usage>

<resolution>
<proceed-with-current/>
</resolution>
</resource-usage>
<configuration>
<resolution>
<automatic/>
</resolution>
</configuration>

</policy>

<rule conflict-id="0">
<resolution>
<rename new-name="ip-type:shared:ip-address:*.*.*.*"/>
</resolution>

</rule>

</conflict-resolution-rules>
</resolve-conflicts-task-description>



can anyone advise?

thanks
 
I am also gettiing this conflict

<param name="limit-name" value="max_mssql_db"/>
<param name="limit-requested-value" value="1"/>
<param name="limit-available-value" value="0"/>

how do i add that to the conflict resolution file? i.e. what would be the full content of the file with the IP part aswell.

thanks in advance

Ian
 
Back
Top