# Resolving Data Conflicts

The Parallels Business Automation - Standard provides special tools for fixing the data synchronization problems between the Parallels Business Automation - Standard database and both Virtuozzo and Plesk nodes.

How conflicts occur?

Conflicts can occur in two cases:

1. New node registration. You are registering a Hardware Node that carries the information that is either absent or differs from the data in the Parallels Business Automation - Standard database.

   Strictly speaking, in this case the situation (a conflict) is just the Parallels Business Automation - Standard offer to import Virtuozzo Containers or Plesk domains found on a node being registered. When you register a Virtuozzo or Plesk server, Parallels Business Automation - Standard fetches the configuration of a node itself and Containers or Plesk domains/clients existing on a node. And you can assign Containers or Plesk domains to an Parallels Business Automation - Standard account, select one of Parallels Business Automation - Standard Hosting plans, and create subscriptions, so that Container or Plesk domain could be managed and billed by Parallels Business Automation - Standard tools.

   Note: Registration conflicts do not affect a Hardware Node availability. And such conflicts can occur only if you are registering a node that runs Virtuozzo or Plesk and already hosts Virtuozzo Containers or Plesk clients/domains. In general, you can establish connection with a node and start creating Virtuozzo Containers or Plesk domains right after the registration is finished. And conflicting Containers or Plesk domains can be imported later.

   Servers that run some third-party software can be just registered and offered as a simple dedicated subscription for automated billing, in this case Parallels Business Automation - Standard does not concerned in the data a node carries, so there are no registration conflicts occur with third-party servers.

2. Data mismatch with a registered node.

   The information in the Parallels Business Automation - Standard database and on a Hardware Node has became different. For example, a Plesk domain or a Container was deleted on a hosting node and Parallels Business Automation - Standard database on a Management Node still contains the record about this subscription. Or conversely: a subscription exists on a node, but there are no records about it in the database on the Management Node. The data on a Hardware Node and a Management Node is being periodically checked. If data mismatch takes place, a conflict occurs, and you can see it in a Hardware Node properties (for Container conflicts) or in a Plesk client/domain properties. You can resolve a conflict by recreating either Container or Plesk domain/client or deleting it.

To resolve the Container conflicts, go to the Service Director - Virtuozzo Manager - Nodes.

To resolve the Plesk domains or clients conflicts, go to the Service Director - Plesk Manager - Plesk Domains or - Plesk Clients respectively.

In This Chapter Resolving Container Subscriptions Registration Conflicts Synchronizing the Plesk Subscription on a Node and in Parallels Business Automation - Standard Database

Please send us your feedback on this help page