• Please be aware: Kaspersky Anti-Virus has been deprecated
    With the upgrade to Plesk Obsidian 18.0.64, "Kaspersky Anti-Virus for Servers" will be automatically removed from the servers it is installed on. We recommend that you migrate to Sophos Anti-Virus for Servers.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Going nuts with pleskbackup and restore in 9.5.4

VirtuMe

New Pleskian
Dear all,

Can you please give me a hand with a simple tasks that I seem to be dumb enough to able to do? I want to automate the copy of the configuration (no data) of a domain in a Plesk 9.5.4 box to a different box using the same Plesk version.

The destination machine will have:
1) A different IP address (so the conflict needs to be fixed)
2) The same existing domain (I want to REPLACE ALL configuration data with the data coming from the original machine)

So in the original machine, I would do:
pleskbackup --domains-name foo.com -c --output-file=/tmp/foo.tgz

And in the destination:
pleskrestore --restore /tmp/foo.tgz -level domains -verbose -conflicts-resolution /tmp/conflicts.xml

After hours (a few thousand mailboxes) the restore ends and everything in the destination server is exactly as it was before the restore, no change.

The conflict file is something like this, not sure it's ok, the manual is not very clear:

<?xml version=1.0 encoding=UTF-8?>
<conflict-resolution-rules>
<policy>
<timing>
<resolution>
<overwrite />
</resolution>
</timing>
<resource-usage>
<resolution>
<overwrite />
</resolution>
</resource-usage>
<configuration>
<resolution>
<overwrite />
</resolution>
</configuration>
</policy>

<rule conflict-id="0">
<node children-processing-type="" name="domain">
<attributes>
<attribute name="name" value="foo.com"/>
</attributes>
</node>
</dump-objects>
<resolution>
<rename new-name="ip-type:shared:ip-address:(NEW IP ADDRESS ON DESTINATION"></rename>
</resolution>
</rule>
</conflict-resolution-rules>


Thanks for your help

Rgds
 
Anyone?

Hi,

Can't this be done? Is there a better approach to this?

BTW, the OS is CentOS 5.5 on both origin and destination

Regards
 
Back
Top