• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Input Plesk Migrator: One Plesk Server to a New Plesk Server

ict2842

New Pleskian
Hello all. I am running Plesk on a server in Los Angeles and will be setting up a new and replacement server in Dallas. I need to migrate all data (settings, services plans, subscriptions, and client/subscription data) to Dallas. I am in the process of reading the Plesk Migrator docs to see if this is the route I should go and what data would need to be migrated before hand.

I run the latest version of Plesk, currently at "Plesk Obsidian v18.0.32_build1800201204.22 os_CentOS 7". I do plan to use CentOS 8 on the new server, if that matters.

What is the easiest way to do this?

My current thought process here is as follows:
> Install CentOS 8. Perform all upgrades & updates.
> Install Plesk. Install Components and Extensions. Perform any upgrades & updates, if necessary.
> Go through each and every link/button in "Tools & Settings" and manually duplicate settings on the "current" server. (Please tell me there is a better way to do this.)
> Transfer data (services plans, subscriptions, and client/subscription data) using either Plesk Migrator or manually downloading everything and reuploading it onto the new server, assuming the Plesk Migrator is the way to go here.
 
> Go through each and every link/button in "Tools & Settings" and manually duplicate settings on the "current" server. (Please tell me there is a better way to do this.)
No better way.
> Transfer data (services plans, subscriptions, and client/subscription data) using either Plesk Migrator or manually downloading everything and reuploading it onto the new server, assuming the Plesk Migrator is the way to go here.
Use Plesk Migrator.
 
Yep, we do the same. In terms of copying settings, we built a standardization script that uses Plesk CLI and DB updates to configure each server exactly as we like it. That saves a huge chunk of time, though it definitely took a while to build.

We use Plesk Migrator for the data transfer. Then block web and email access to the source server at the firewall level, run a re-sync (differential), move the live IPs to the destination server, run reconfigurator to remap the IPs to the original/live ones. That way the IPs don't even need to change.
 
Yep, we do the same. In terms of copying settings, we built a standardization script that uses Plesk CLI and DB updates to configure each server exactly as we like it. That saves a huge chunk of time, though it definitely took a while to build.

We use Plesk Migrator for the data transfer. Then block web and email access to the source server at the firewall level, run a re-sync (differential), move the live IPs to the destination server, run reconfigurator to remap the IPs to the original/live ones. That way the IPs don't even need to change.
Thank you!
 
Back
Top