Conflict Resolution Rules and Policies

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

Types of Conflicts

The restoration process can encounter several types of conflicts, as
follows:

• 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 limit for
    this particular user (for example, disk space limit).
  • Unique resource usage conflict: An object being restored requires
    a unique resource which is already being used by another object in
    the system or does not exist (for example, domain).
• Configuration conflicts. It might happen that the configuration being
  restored is not enabled on the destination server. Two situations can
  arise here:
  • Configuration options are not enabled for the domain.
  • Required configuration options are not available (for example, web
    applications are not available for the customer, database server
    is not configured on the host, no IP address is allocated to the
    reseller, and so on).

Conflict Resolutions

The following conflict resolutions options are possible:

• Overwrite. This 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 or a setting from backup does not exist in Plesk, it
    is created.
  • If an object or a setting from backup exists in Plesk, it replaces
    the existing object or a setting.
  • If an object or a setting exists in Plesk but is missing in a
    backup, the existing object or a setting remains.
• Proceed with current. This means that objects that are currently
  present in the system will not be affected by the restoration
  process. The restoration process will proceed to the objects
  belonging to the object that already exists in Plesk, without making
  modifications to that object.
• Do not restore. This means that the objects that are currently
  present in the system or were deleted after the backup will not be
  restored with the lower level objects.
• Automatic. This means that configuration option that should be
  enabled for domain is enabled automatically.
• Overuse. This means that objects are restored even when the resources
  are overused. Can be applied only…