• 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.

Migration Tool Issue: Transferred Disk Usage & DBs Not The Same Size?

BernieG

Basic Pleskian
Hi,

I've transferred my domains from Plesk 11.5 (CentOS 5) to Plesk 12 (CentOS7) using the migration tool, and when I check the disk usage and DBs I'm seeing that they don't match up.

For example, the disk usage for some domains don't have the same exact size on my new server. It seems like all the data did not get transferred over.

And then when I check some DBs I have some databases that have the same number of tables which is good but then I notice within the tables they don't have the same number of rows and the total size of the DBs are different.

I also have DBs that have less tables than what my old server shows; so it looks like all the tables did not get transferred.

Why is this issue happening with Plesk migration tool? Is there another way I can do this so it works properly?

Thank you!
 
Hi. I have the same remark. the size in the source server is greater than the size in the taget server
 
the diskspace can e.g. be different because backups are calculated for the source but not for the target because the plesk migrator does not take over any backups.
I can't say anything about possible database problems with the migrator. we migrated thousands of databases during server changes and did not find any problems.
 
the diskspace can e.g. be different because backups are calculated for the source but not for the target because the plesk migrator does not take over any backups.
I can't say anything about possible database problems with the migrator. we migrated thousands of databases during server changes and did not find any problems.
I figured the probel was the backup. Backup is a limitation on Plesk migrator. I copy it manulaly . Thanks
 
Back
Top