• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

move clients between 2 plesk servers

Z

zozzi

Guest
hello

how to move clients between 2 plesk 8.3 servers without major blackout ?

old plesk server was running on the peak of resources, so we setup a new machine and i'd like to move couple clients to new server

any ideas? how to setup DNS to minimalise domain time off service ? probably dns is most critical, isn't it?
 
Yes, you need to lower the TTL (which needs time to propagate). When that's done you can use the Plesk Migration Manager.
 
using plesk migration manager 1 domain can take couple minutes - so is it ok to set TTL for example 60 seconds ?
 
You could do that. Just know that if the previous TTL was 24 hours you need to wait for 24 hours for this new TTL to propagate completely.
 
Back
Top