• 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 10.1.1 to 10.4.4 some domains changed htype to none

SPeter

New Pleskian
Hey there

We have the annoying problem that after the migration from Plesk 10.1.1 to 10.4.4 some domains (79) changed their hosting type from vrt_hst to none.

The logfile conflict-detect.log says:
Error: Dump is not valid due to internal unique resources conflict (Class [SystemUser] value [])

Those domains now have for example no entry in the sys_users table.

We've done the migration as following:
1. Create a config backup of the source server
/opt/psa/bin/pleskbackup server -c -z

2. Convert the config backup on the destination server
/opt/psa/bin/pre10-backup-convert --convert -source ..... -destination .......

3. Restore the config backup on the destination server
/opt/psa/bin/pleskrestore --restore

4. Copy all the content to the new server
rsync -aut /var/www/vhosts/* [email protected]:/var/www/vhosts
rsync -aut /var/qmail/mailnames/* [email protected]:/var/qmail/mailnames
mysqldump -uadmin -p`cat /etc/psa/.psa.shadow` --all-databases > db_backup.sql
mysql -uadmin -p`cat /etc/psa/.psa.shadow` < db_backup.sql

Systems
Old System
Debian 4.1.1
Plesk 10.1.1
Apache 2.2.3
MySQL 5.0.32

New System
Debian 6.0.5
Plesk 10.4.4
Apache 2.2.16
MySQL 5.1.61

Any help or suggestion is appreciated!
 

Attachments

  • conflict-detect.log.txt
    9.1 KB · Views: 1
Strange steps for migration. I do not understand why you have converted backup from Plesk 10 to Plesk 10 format? And why you do not use Plesk Migration Manager for migration?
 
thx for your reply

I know, we've come up with those steps after some tries.

1. The Plesk Migration Manager didn't work at all, my predecessor told me that the parallels team recommended to deploy the migration with backup/restore.

2. When we tried to restore the backup without converting it, it didn't work at all. We found the article (http://kb.parallels.com/en/9578) which says that you should convert Versions >=10.1. And after converting it, we were able to restore it.
 
What do you mean "The Plesk Migration Manager didn't work at all"? What exactly doesn't work there?
Did you try our Plesk Mass Migration Script?
I do not understand why you use strange methods instead of special migration tools?
 
Back
Top