Sometimes it is required to replace hardware or upgrade/change the OS distribution of a Plesk server registered in OBAS.
After OBAS is upgarded, there are two ways to replace a Plesk node.
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.
- Let's upgrade/migrate/transfer an old Plesk node called "Hosting".
- Create a new Plesk node "Hosting-new" with a temporary IP address.
- Detach the old node from OBAS temporarily and enable Do not allow customers to manage their domains from CP for that node.
- Transfer/migrate all objects from "Hosting" to "Hosting-new" node with the Plesk migration utility.
- Move IP addresses of the "Hosting" node to "Hosting-new" during the migration (it means no IP mapping changes for customer domains).
- Stop the old "Hosting" node and rename the new node to "Hosting"
- Enable/attach the "Hosting" Plesk node object in OBAS again.
- Run "Update Plesk nodes stats info" task.
- Migration is ready, no need for manual conflict resolution.
How to replace IP addresses in Plesk for Linux to have the same IPs as on the source node.