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

backup__restore__conflict_configuration_reason_ip

M

MOUCHONS

Guest
Hello,

I church to use the -conflicts-resolution option on pleskrestore command.

I make :

/usr/local/psa/bin/pleskrestore --restore ns_back_domain.pl_info_1005052351.xml -level domains -conflits-resolution /root/conflicts-plesk -debug

I have this error :

<message>backup__restore__conflict_configuration_reason_ip</message>
<param name="ip-address" value="xx.xx.xx.xx"/>
<param name="ip-type" value="shared"/>
<param name="type" value="backup__restore__object_plesk_admin"/>
<param name="name" value="backup__restore__object_plesk_admin"/>

It is due that the backup is provided since an other server.

I want use the the conflicts-resolution option to make a generic option datafile:

My file /root/conflicts-plesk contain :

the generic content resolution rules:
<conflict-resolution-rules>
<policy>
<timing>
<resolution>
<proceed-with-current />
</resolution>
</timing>
<resource-usage>
<resolution>
<overuse />
</resolution>
</resource-usage>
<configuration>
<resolution>
<automatic />
</resolution>
</configuration>
</policy>
</conflict-resolution-rules>

and I have find the domain specific data

<resolve-conflicts-task-description>
<conflict-resolution-rules>
<policy />
<rule conflict-id="0">
<dump-objects>
<node name="my_specific_domain.tld">
<attributes>
<attribute name="id" value="25"></attribute>
<attribute name="guid" value="0822c175-a10d-459e-bd3a-e5cbc497e1f0"></attribute>
<attribute name="owner-guid" value="93dbe1b1-cff5-430f-8466-5b810099772f"></attribute>
<attribute name="name" value="my_specific_domain.tld"></attribute>
</attributes>
</node>
</dump-objects>
<resolution>
<!-- beginning of the conflict resolution definition: IP mapping: upon restore, the conflicting domain example.com should have hosting configured on IP 192.0.2.34 -->
<rename new-name="ip-type:shared:ip-address:xx.xx.xx.22"/>
</resolution>
<!-- end of the conflict resolution definition -->
</rule>
</conflict-resolution-rules>
</resolve-conflicts-task-description>

But it is still en error.

I want to put renew new-name to the generic resolution conflicts .


I need to help because I don't find some information about this and I am very far of the resolution ^^

Can you provide me a specific xml text file to apply on the generic rules to use on a global restore backup ?

or can you give a runway to help ?

Very thanks for your time.

regards
 
Hello,

Nobody knows how repair the error :

backup__restore__conflict_configuration_reason_ip

???

Thanks for your help. This post can be used for all the search on internet. There is 3 responses on google with this search :

backup__restore__conflict_configuration_reason_ip

Best regards
 
I got it working.

/usr/local/psa/bin/pleskrestore --restore /var/lib/psa/dumps/clients/[Clientname]/converted_[Clientname]_info_1005261607.xml -level clients -debug -conflicts-resolution conflict-file

Content of conflict-file:
<?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:[new-ip-address]"/>
</resolution>

</rule>

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