Skip to content
  • Solutions
    By Role
    • For Developers
    • For Content Managers
    • For Agencies
    • For IT Admins
    • For Web Hosters
    • For Developers
    • For Content Managers
    • For Agencies
    • For IT Admins
    • For Web Hosters
    By Infrastructure
    • Overview
    • AWS
    • Microsoft Azure
    • Alibaba Cloud
    • Google Cloud Platform
    • Vultr
    • Overview
    • AWS
    • Microsoft Azure
    • Alibaba Cloud
    • Google Cloud Platform
    • Vultr
    • Digital Ocean
    • Linode
    • Upcloud
    • Oracle
    • OVH
    • Digital Ocean
    • Linode
    • Upcloud
    • Oracle
    • OVH
  • Product
    • Plesk Features
    • Plesk Editions
    • What’s new
    • Pricing
    • Roadmap
    • Lifecycle Policy
    • Extensions Catalogue
  • Pricing
  • Extensions
    Featured Extensions
    • SocialBee
    • WP Toolkit
    • Sitejet Builder for Plesk
    • SEO Toolkit
    • Joomla! Toolkit
    • Premium Email
    • Email Security
    • SocialBee
    • WP Toolkit
    • Sitejet Builder for Plesk
    • SEO Toolkit
    • Joomla! Toolkit
    • Premium Email
    • Email Security
    Bundles and packs:
    • Business and Collaboration Edition
    • WP pack
    • Hosting pack
    • Power pack
    • Language pack
    • Business and Collaboration Edition
    • WP pack
    • Hosting pack
    • Power pack
    • Language pack

    See all Extensions

  • For Partners
    • Plesk Contributor Program
    • Plesk Partner Program
    • Affiliate program
    • Plesk University
  • Help Center
    • Documentation
    • Professional Services
    • Support
    • Contact Us
    • Wiki
    • Forum
  • Plesk 360 login
  • Free Trial
  • Pricing
  • Solutions
    • By Role
      • For Developers
      • For Content Managers
      • For Agencies
      • For IT Admins
      • For Web Hosters
    • By Infrastructure
      • Overview
      • Plesk on Amazon Web Services (AWS & Lightsail)
      • Microsoft Azure
      • Alibaba Cloud
      • Google Cloud Platform
      • Vultr
      • DigitalOcean
      • Linode
      • UpCloud
      • Oracle
      • OVH
  • Products
  • Pricing
  • Extensions
    • Featured Extensions
      • SocialBee
      • WP Toolkit
      • Sitejet Builder for Plesk
      • SEO Toolkit
      • Joomla! Toolkit
      • Premium Email
      • Email Security
    • Bundles and packs:
      • Business and Collaboration Edition
      • WP pack
      • Hosting pack
      • Power pack
      • Language pack
      • See all Extensions
  • For Partners
    • Plesk Contributor Program
    • Plesk Partner Program
    • Affiliate Program
    • Plesk University
  • Help Center
    • Documentation
    • Professional Services
    • Support
    • Contact Us
    • Wiki
    • Forum
  • Plesk 360 login
  • Free Trial
  • Pricing
  • Solutions
    • By Role
      • For Developers
      • For Content Managers
      • For Agencies
      • For IT Admins
      • For Web Hosters
    • By Infrastructure
      • Overview
      • Plesk on Amazon Web Services (AWS & Lightsail)
      • Microsoft Azure
      • Alibaba Cloud
      • Google Cloud Platform
      • Vultr
      • DigitalOcean
      • Linode
      • UpCloud
      • Oracle
      • OVH
  • Products
  • Pricing
  • Extensions
    • Featured Extensions
      • SocialBee
      • WP Toolkit
      • Sitejet Builder for Plesk
      • SEO Toolkit
      • Joomla! Toolkit
      • Premium Email
      • Email Security
    • Bundles and packs:
      • Business and Collaboration Edition
      • WP pack
      • Hosting pack
      • Power pack
      • Language pack
      • See all Extensions
  • For Partners
    • Plesk Contributor Program
    • Plesk Partner Program
    • Affiliate Program
    • Plesk University
  • Help Center
    • Documentation
    • Professional Services
    • Support
    • Contact Us
    • Wiki
    • Forum
  • Plesk 360 login
  • Free Trial
Plesk 360 login
Free Trial

Knowledge Base

Rules

 
advanced administration guide winbacking up restoring and migrating dataconflict resolution rules and policiescustom conflict resolutionsresolutions description format

The file should be structured as follows.

image 63394

  • conflict-resolution-rules
    Required, document root element.

    • policy
      Required, contains the policies descriptions. For details on the
      node format, refer to the section Resolutions Description Format:
      Policies
      .
      The element content must reflect the conditions under which the
      conflicts were detected.

    • rule
      Optional, contains a rule description.
      Must be present in the document when defining conflict
      resolution rules. Should be present as many times as the number
      of unresolved conflicts.

      At least one of the attributes (conflict-id,
      conflict-guid) MUST be present.

      • conflict-id
        Optional, defines ID of the conflict being resolved. Value is
        integer.
        The ID should be obtained from the conflict description
        returned by pleskrestore (the
        “/conflicts-description/conflict[@id]” attribute value)
      • conflict-guid
        Optional, defines global ID of the conflict being resolved.
        Value is string.
        The GUID should be obtained from the conflict description
        returned by pleskrestore (the
        “/conflicts-description/conflict[@guid]” attribute value).
        If omitted, the conflict for resolution is identified by ID.
      • dump-objects
        Optional, holds a collection of descriptions of backup objects
        involved into the conflict and taking the same conflict
        resolution
        Must be present in the document in case when different
        objects involved in the same conflict should be resolved in
        different ways.
        May not be present in the document in case when all objects
        involved in the conflict should be resolved the same way.
        See the structure below.
      • resolution
        Required, contains definition of resolution for the conflict,
        see the structure below.

dump-objects structure:

image 62558

  • node
    Required, contains a description of backup object involved in the
    conflict.
    The element contents must be taken from the conflict description
    returned by pleskrestore (the
    “/conflicts-description/conflict/conflicting-objects/node”
    element).
    Structured as follows:

    image 62561

  • name
    Required, specifies the object type, value must be a string.

  • context
    Optional, holds a collection of data specifying the object position
    in backup.

    • path
      Required if the context element is present in the document,
      specifies the location of object definition in the backup
      metadata. Value must be a string conforming to the XPath notation.
  • attributes
    Required, holds a collection of the object properties.

    • attribute
      Required, specifies a particular property of the object (e.g.,
      login, ID, GUID, etc.), empty value.

      • name
        Required, specifies the property name, value must be a string.
      • value
        Required, specifies the property value, value must be a string.

resolution structure:

image 62555

The resolution element must not be empty, it is required that it
contains one, and only one of its children elements:

  • do-not-restore
    Sets the Do Not Restore resolution for the conflict, empty value.
  • proceed-with-current
    Sets the Proceed With Current resolution for the conflict, empty
    value.
  • automatic
    Sets the Automatic resolution for the conflict, empty value.
  • overuse
    Sets the Overuse resolution for the conflict, empty value.
  • overwrite
    Sets the Overwrite resolution for the conflict, empty value.
  • rename
    Sets the Rename resolution for the conflict, empty value.

    • new-name
      Required, specifies a name of unique resource that should be
      assigned to the conflicting objects, value must be a string.
      Makes sense only for unique resource usage conflicts (mapping of
      IP, database server, object owner).
Tweet
Share
Share
Email
0 Shares
Read the full article
Related Posts
Knowledge Base

Database Server – Using MariaDB or Percona as the Default Database Server

Read More »

Downloading Backup Files from Server

Read More »

Uploading Backup Files to Server

Read More »

Removing Backup Files from Server

Read More »

Hosting Wiki

  • Server Redundancy
  • Bare Metal Server
  • Backup
  • Oracle VM Server
  • Server Virtualization Software
  • Windows Server
  • JavaScript
  • SQL database
  • NoSQL Database
  • Web Server
  • DNS Server
  • IPv6
  • IPv4
  • SIP
  • UDP/IP
  • TCP/IP
X-twitter Linkedin Youtube Reddit Github
  • Product
  • Login
  • Pricing
  • Editions
  • For Partners
  • Partner Program
  • Contributor Program
  • Affiliate Program
  • Plesk University
  • Company
  • Blog
  • Careers
  • Events
  • About Plesk
  • Our Brand
  • Resources
  • User and Admin guides
  • Help Center
  • Migrate to Plesk
  • Contact Us
  • Hosting Wiki
  • Forum
  • Legal
  • Legal
  • Privacy Policy
  • Imprint

© 2025 WebPros International GmbH

Part of the WebPros®  Family