• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Best practises Server migration

Hello there,

I'll have to migrate all my existing clients and their whole data to a new server-hardware.
This is neccessary to extend performance and capacity.

So I've been investigating about how to do this with a minimum of downtime.
Overview of the current setup:

1x old Plesk-Server 9.2.3 with CentOS 5.3 64Bit
1x new Plesk-Server 9.3.0 with CentOS 5.4 64 Bit

Both machines are in the same subnet and accessible via console-switches from remote.

The goal is to migrate all old IP-Addresses to the new system because the old server is used as primary DNS-Server.

I'll be very happy about any suggestions as well as success-/problem-reports.

A "simple" Image-Backup/-Restore is not possible.


Thank you very much and best regards


Thorsten
 
What about using IP mapping file as it is described in Plesk documentation?
 
I'm not sure about the IP addresses, but I would suggest upgrading your current server to 9.3 before migrating. Personally, I've always had the most success migrating from/to the same version of Plesk. In fact, it's usually flawless that way.
 
Back
Top