Post-Migration Checks

After migrating from one of the supported source platforms, you can perform a post-migration check to verify that the transferred websites, email accounts, databases, and so on are available on the destination server.

The post-migration check verifies the operability of the following aspects:

For every aspect, service-specific tests are performed for every migrated object (website, mail account, system user, and so on). The details about the tests are given later in this section.

To perform the post-migration check:

/usr/local/psa/admin/sbin/modules/panel-migrator/plesk-migrator test-all

The post-migration check generates a report and saves it to a file named test-all-report.<date> placed in the /usr/local/psa/var/modules/panel-migrator/sessions/migration-session/ directory.

"%plesk_dir%admin/plib/modules/panel-migrator/backend/plesk-migrator.bat" test-all

The post-migration check generates a report and saves it to a file named test-all-report.<date> placed in the <PLESK_DATA_DIRECTORY>/var/modules/panel-migrator/sessions/migration-session/ directory. To find the location of <PLESK_DATA_DIRECTORY> on your server, open the command prompt and run the following command:

reg query "HKLM\SOFTWARE\Plesk\PSA Config\Config" /v PRODUCT_DATA_D /reg:32

The report has a tree structure representing a hierarchy of customer accounts, subscriptions, and services. For every post-migration test that fails, an entry is included in the log, including details about the failure and steps to verify/resolve the potential issue.

Post-migration tests

Websites

For each migrated domain, the following items are checked:

For each website, the index page is requested from the source server and destination server. The contents of the index page are analyzed and all relative links in the form <a href="RELATIVE_URL"> pointing to the same domain are checked. To speed the process up, links are grouped by directory and extension, and a single link is randomly chosen from each group to be checked. For example, if http://DOMAIN/pages/about.php and http://DOMAIN/pages/contacts.php are both on the index page, only one of these links will be checked.

For each selected link, a request is sent to the appropriate address on the source and destination servers (checks follow redirections by 301 and 302 HTTP codes). The resulting web page is analyzed for the presence of HTTP errors. A test is considered successful if both of the following conditions are met:

Otherwise, the test is considered to have failed.

Mail

For each migrated domain, all mail accounts present on the source server must be present on the destination server as well. The following tests are performed:

DNS

For each migrated domain, all resource records must be transferred from the source server to the destination server, and IP addresses from the source server must be replaced with those from the destination server according to the IP mapping rules. The following tests are performed:

Databases

For each migrated domain, all databases present on the source server must be present on the destination server as well. The following tests are performed:

System users

For each migrated domain, all system users (users that can connect to the server via FTP or SSH / RDP) present on the source server must be present on the destination server as well. The following tests are performed: