• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Resolved Restart a Plesk migration ( Plesk Migrator after 1 week )

Jhow Plug

Basic Pleskian
Server operating system version
Windows 2019
Plesk version and microupdate number
Plesk Obsedian 18
Well then.

I started a migration, and the report gave some problems.
However, I let it finish for fear of "cancelling" and generating dirt on windows, banks, etc.. etc..

Now One (1) Week later I want to start migration again
I already fixed the problems, but obviously everything is out of date.

So I need to know which is the best way to do this, since everything is already created, but everything is outdated.

I can just start over and then the "plesk migrator"
Does this guarantee that Plesk will do it right, even if content already exists?

plesk migrator will for sure..

- Reset all email files and index files ?
- Reset all site and bank files ?

What is the best way to restart a migration?
Thank you
 
Back
Top