Conflict Resolution Rules and Policies

Conflict is a situation when settings in a backup and settings in a
destination Plesk are such that restoring backup objects leads to an
error or unpredictable Plesk behavior.

Types of Conflicts

The restoration process can encounter several types of conflicts, which
are the following:

• Timing conflicts. An object being restored might exist in the system
  and its last modification date might be more recent than the date of
  backup. Or an object could be deleted from the system later than the
  backup was created.
• Resource usage conflicts. There are two groups of resource usage
  conflicts:
  • Common resource usage conflict: The total amount of measurable
    resources after restoration might appear to be over the limits for
    this particular user (e.g., disk space limit).
  • Unique resource usage conflict: An object being restored requires
    a unique resource which is already used by another object in the
    system or does not exist (e.g., domain).
• Configuration conflicts. It might happen that configuration being
  restored is not enabled on the destination server. Two types of cases
  can happen here:
  • Configuration options are not enabled for the domain.
  • Required configuration options are not available (e.g., site
    applications are not available for the customer, database server
    is not configured on the host, IP address is not allocated to the
    reseller, etc.)

Conflict Resolutions

The following types of conflicts resolutions are possible:

• Overwrite. Means that all objects will be restored from the backup
  files regardless of their current presence in the system. Overwrite
  works as follows:
  • If an object/setting from backup does not exist in Plesk, it is
    created.
  • If an object/setting from backup exists in Plesk, it replaces the
    existing.
  • If an object/setting exists in Plesk but is missed in a backup,
    the existing remains.
• Proceed with current. Means that objects which currently present in
  the system won’t be affected by the restoration process. The
  restoration process will move to the objects belonging to that one,
  not touching the object itself.
• Do not restore. Means that the objects which currently present in the
  system or were deleted after the backup won’t be restored together
  with the lower level objects belonging to it.
• Automatic. Means that configuration option that should be enabled for
  domain is enabled automatically.
• Overuse. Means that objects are restored with the resources overuse.
  Can be applied only to objects that belong to a reseller who works in
  the oversell mode.
• Rename. Means that unique resources for the restored domain are
  reassigned with the specified,…