• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Resolved multi-run plesk migration manager

gijsbert

Basic Pleskian
I have a server that needs to be migated using the plesk migration manager. I noticed that the manager is using rsync. Because this server has a lot of data, I'm wondering if I can run the migration manager multiple times?

I mean, I like to run the migration manager and put all data on a new server. Because it's a lot of data, I like to run the migration manager for a 2nd or 3rd time, so only modified files will be transferred. This way, I can initiate a first migration without really switching to the new environment and the "final" migration will be much faster because most of the data will be there allready.

Is this possible?
 
Hello!
Migration manager allows to run only one migration per server, but it runs a lot of operations in multithreading mode.
There are 2 options to configure multithreading mode in config.ini(both should be specified in [GLOBAL] section):
1. multithreading-status
"disabed" - that means that only one action for only one subscription can be running at the same time. Most of the actions are from that category.
"default" - that means if "full" config option is specified, then action could be running at the same time for multiple subscriptions. Copy content actions are from that category
"full" - that means if "default" or "full" config option is specified, then action could be running at the same time for multiple subscriptions. Create subscription in target Plesk action is from that category

2. multithreading-num-workers - number of subscription threads running at the same time. Default is 5 workers.

So, you can play with settings, maybe it helps.
Also, to play with settings in config.ini use CLI described here
 
Back
Top