Warning: Migration Manager does not migrate everything!

[dietcheese]

I've read many posts about the Migration Manager failing to migrate e-mail accounts, but I have noticed other problems as well:

I am attempting to migrate from 7.5.4->8.1.

1) It does not migrate cron jobs. This includes cron jobs entered via Plesk and cron jobs created manually in /etc/cron.whatever.

2) It fails to migrate any custom directories created within a domain (i.e. /httpd/vhosts/mydomain.com/custom_folder/).

3) The migration manager sometimes hangs on domains containing large files or a large number of files. When this happens it eats up CPU and can bring services to a halt. At least it did for me.

I am looking for a better way. If anyone has any information I would appreciate it.

DC

 

[brainlag]

migration with Plesk is a pain in the ......ss

Please report those exact errors to Plesk Support team so they can fix it within the next Plesk Releases. It is always better to let them know than hoping that they will find them by themselves.

We had similar issues with migrating and it has been a real nightmare. You cannot imagine......

 

[thewolf]

Hi,

Does anyone know if these bugs are fixed is the current migration manager build is reliable?

Thanks.

 

[dietcheese]

They are not fixed. The migration manager will not copy root cron jobs (it may copy jobs from specific domains) and it will not copy custom directories. Just tried a migration last week...

Have fun doing it all manually.

DC

 

[thewolf]

Hi,

Are the backup/restore utilities a better way to migrate to a new server then?

Thanks.

 

[dietcheese]

script

Since Plesk's migration manager is completely borked, I created a simple script which will rsync any Plesk directories you choose and any custom directories (directories within domain root that are not created by plesk) you have created.

I take no responsibility for any problems with this only to say it works for me. Hopefully it will help someone dealing with the same migration nightmares that I am.

(Also, make sure you have your root public key in authorized_keys on the sending server or you will be constantly prompted for it)



#!/bin/sh

# If you want to TEST this script without actually syncing, add -n [dry-run] to both rsync statements

################
# EDIT THESE #
################

# OLD server path to domains
REMOTE_PATH='/home/httpd/vhosts'

# NEW server path to domains
LOCAL_PATH='/var/www/vhosts'

# Put your custom directories that exist on the OLD server, but not the NEW, here:

CUSTOM_DIRECTORIES="
mydomain.com/customdirectory1
mydomain.com/customdirectory2
"

# Put the Plesk directories you want synced here. I do not recommend adding the vhost.conf directory to this list.

PLESK_DIRECTORIES="httpdocs httpsdocs"

RSYNC=/usr/bin/rsync
RSYNC_USER=root
RHOST=server1.yourserver.com


#########################
# DON'T EDIT BELOW HERE #
# UNLESS YOU KNOW WHAT #
# YOU ARE DOING #
#########################

# dirty way to get all the .com names on the NEW server

DOMAINS=`ls -A $LOCAL_PATH | grep '.com'`

# this will recursively sync all directories listed in PLESK_DIRECTORIES

echo "************* COPYING PLESK DIRECTORIES *************"
for d in $DOMAINS;
do
for p in $PLESK_DIRECTORIES;
do
echo "***** copying $REMOTE_PATH/$d/$p/ to $LOCAL_PATH/$d/$p *****"

# $RSYNC -pog -vv --recursive --port 2233 $RSYNC_USER@$RHOST:$REMOTE_PATH/$d/$p/ $LOCAL_PATH/$d/$p
echo $RSYNC -n -pog -vv --recursive --port 2233 $RSYNC_USER@$RHOST:$REMOTE_PATH/$d/$p/ $LOCAL_PATH/$d/$p
done
done


# this will sync your custom directories, listed in CUSTOM_DIRECTORIES

echo "************* COPYING CUSTOM DIRECTORIES *************"
for d in $CUSTOM_DIRECTORIES;
do
echo "***** copying $REMOTE_PATH/$d/ to $LOCAL_PATH/$d *****\n"
$RSYNC -pog -vv --recursive --port 2233 $RSYNC_USER@$RHOST:$REMOTE_PATH/$d/ $LOCAL_PATH/$d

done

 

[dietcheese]

more migration manager warnings

2 more migration manager problems:

1) Double-check your DNS settings after they have been migrated. 4 (out of about 100) of my domains had their DNS settings totally wiped out except for one CNAME record.

2) On any domains that are using external email services (mail not served by Plesk) make sure to check that a) the mail service is turned off for those domains and b) your dns records are correct BOTH in Plesk AND on the server.

On my server e-mail was turned ON for all domains using external mail, even though it was set to OFF on the old server. Also, the DNS records in Plesk did not match the DNS records when you "dig domain.com"

Hope that helps someone...

DC

 

[dietcheese]

more...

Triple-check your DNS settings.

About 15 domains, although correctly configured in Plesk, had DNS entries consisting only of ns.domainname.com after migrating. To be clear: the entries in Plesk all LOOK correct but a "dig" on the server shows they are wrong.

Now I am screwed again as these incorrect DNS entries have already began to propagate.

<vent>
Plesk SUCKS.
</vent>

DC

 

[brainlag]

let them know

hey dietcheese

u made us covered with cold sweat.....

pls tell SWsoft about those errors

thanks