• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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