Search Engine: Elastic
  • Article for your preferred language does not exist. Below is international version of the article.

Article ID: 5474, created on Jul 16, 2008, last review on Dec 28, 2016

  • Applies to:
  • Odin Business Automation Standard 4.5

Symptoms

Sometimes it is required to replace hardware or upgrade/change the OS distribution of a Plesk server registered in OBAS.

Resolution

Upgrade OBAS system to the latest available version.

After OBAS is upgarded, there are two ways to replace a Plesk node.

Solution one

Create a new Plesk node with desired parameters and register it in OBAS. Migrate all Plesk domains/clients to that new Plesk node with the Plesk migration utility. After accounts are migrated, please run the periodic task Update Plesk nodes stats info under Top > Configuration Director > Logging and Errors > Action Log > Tasks Queue to make the objects migrated to the new Plesk node appear in Conflicts Resolver (Top > Migration Director > Conflicts Resolver).

Finally, please resolve data conflicts with the Conflicts Resolver

When all data is on the new node, old Plesk node can be removed from OBAS.

Solution two

  1. Let's upgrade/migrate/transfer an old Plesk node called "Hosting".
  2. Create a new Plesk node "Hosting-new" with a temporary IP address.
  3. Detach the old node from OBAS temporarily and enable Do not allow customers to manage their domains from CP for that node.
  4. Transfer/migrate all objects from "Hosting" to "Hosting-new" node with the Plesk migration utility.
  5. Move IP addresses of the "Hosting" node to "Hosting-new" during the migration (it means no IP mapping changes for customer domains).
  6. Stop the old "Hosting" node and rename the new node to "Hosting"
  7. Enable/attach the "Hosting" Plesk node object in OBAS again.
  8. Run "Update Plesk nodes stats info" task.
  9. Migration is ready, no need for manual conflict resolution.

See also

Switching to the new Plesk business model breaks data consistency

How to replace IP addresses in Plesk for Linux to have the same IPs as on the source node.

400e18f6ede9f8be5575a475d2d6b0a6 caea8340e2d186a540518d08602aa065 70a5401e8b9354cd1d64d0346f2c4a3e 624ca542e40215e6f1d39170d8e7ec75

Email subscription for changes to this article
Save as PDF