How to Process Migration Reports

After each step of the migration, the tool generates a report. Reports are useful for determining if a migration step was successful and if you can proceed to the next step. If there are errors, you need to evaluate the results and decide whether to resolve issues, or proceed to the next step and resolve the issues later.

When evaluating the results, issue severity levels are useful. This is a list of available severity levels:

Error. This issue is a sign of major loss of functionality. You should resolve it before proceeding to the next migration step.
Warning. This kind of issues, in general, should not be skipped, but the next migration step will succeed. You should prepare for reviewing and resolving this issue after migration has completed.
Info. Either this type of issue does not lead to a loss of functionality, or it has a workaround that you can apply after migration is completed.

The migration report is a plain text file. Each report contains a list of found issues with each issue described in detail, and a summary, which counts issues by severity and type.

In addition to the report itself, there is also a report summary, which the migration tool writes to stdout at the end of command execution.

In the report, the issues are organized as a tree that represents the hierarchy of customers, subscriptions, and subscription's services.

Reports are generated as a results of the following operations:

Checking of services on the target server
Infrastructure check
Transfer of accounts
Post-migration check

Checking of Services on the Target Server

This is an example of a report:

[root@pp3 plesk115]# cat session/test_service_report.2015.06.10.13.52.59

Services' Issues

¦

+ Service 'web on target Plesk server'

¦

+ Service 'ftp on target Plesk server'

¦

+ Service 'mail on target Plesk server'

¦

+ Service 'dns on target Plesk server'

¦ ¦

¦ L error: Service 'dns' is not started on target Plesk server.

¦   Make sure that the service is started.

¦

+ Service 'mysql on target Plesk server'

¦

L Service 'plesk on target Plesk server (192.168.111.170)'

In this example, there is an issue with the "error" severity, which notifies the user of the migration tool about the failed DNS service. In such a case, you should find the cause of this failure and resolve the problem before starting to transfer hosting data, as it is very likely that the absence of DNS service will affect other steps of the migration.

Infrastructure Checks

The migration tool automatically performs infrastructure checks as a part of the command panel-migrator transfer-content. The resulting report contains information about the available amount of disk space, the connections that should be opened and the database settings required for migration to proceed.

Transfer of Accounts

After panel-migrator transfer-accounts config.ini command is completed, it produces a report that includes all the issues that the migration tool has encountered during the transfer of hosting data.

This is an example of the report:

Detailed Migration Status

¦

+ Client 'client1 (John Smith, jsmith@example.com)'

¦ ¦

¦ L Subscription 'replaceddomain.pfu115'

¦

L Administrator

¦

  + Subscription 'admindomain.example.com'

¦

  + Subscription 'another.example.com'

¦

  + Auxiliary user 'some@user.domain.test'

  ¦ ¦

  ¦ L info: User password does not meet Plesk requirements. A temporary password is generated: 'PkL25F-%a!z4znJ265'

¦

  L Auxiliary user 'another@user.domain.test'

¦

    L info: User password does not meet Plesk requirements. A temporary password is generated: 'aj!n-50%g2M5GzF7I8'

This example report contains two issues with the "info" severity level, caused by incompatible security policies set in source and target Plesk installations. The solution in this case depends on the number of such issues. If the number of issues is small enough, you may choose to notify affected customers about changed passwords. If there are many customers with changed passwords, you may prefer to temporarily lower the security policies on the target server and retry the transfer-account command.

Post-migration Check

An example of a report created by a post-migration check (the command panel-migrator test-all):

Transferred Domains' Functional Issues

¦

L Source server 'plesk115'

¦

  + Client 'pleskclient1'

  ¦ ¦

  ¦ L Subscription 'client1domain.test'

  ¦   ¦

  ¦   + Mail domain 'client1domain.test'

  ¦   ¦

  ¦   + Database service 'client1domain.test'

  ¦   ¦

  ¦   + SSH service 'client1domain.test'

  ¦   ¦

  ¦   + DNS zone 'client1domain.test'

  ¦   ¦ ¦

  ¦   ¦ + error: The DNS server at 192.168.111.170 returned incorrect DNS records. Here is an example of differing records:

  ¦   ¦ ¦ expected record(s) 'client1domain.test. A 192.168.111.170', got no records

  ¦   ¦ ¦ expected record(s) 'client1domain.test. MX 10 mail.client1domain.test.', got no records

  ¦   ¦ ¦ expected record(s) 'client1domain.test. TXT v=spf1 +a +mx -all', got no records

  ¦   ¦ ¦ All information about the differences is saved to the file /opt/panel-migrator/sessions/migration-session/dns.target.192.168.111.170.difference.client1domain.test

  ¦   ¦ ¦ Make sure that:

  ¦   ¦ ¦ 1. The DNS zone of this domain exists in target Plesk and is enabled.

  ¦   ¦ ¦ 2. All desired DNS records exist in target Plesk and are active.

  ¦   ¦ ¦

  ¦   ¦ ¦ Ignore this warning if you have changed DNS zone after migration and the resolved records look fine.

  ¦   ¦ ¦

  ¦   ¦ L info: External DNS servers have no information about the domain. It is possible that the domain name is not registered. Checking by external DNS will be skipped.

  ¦   ¦

  ¦   ¦

  ¦   + Apache web site 'client1domain.test'

  ¦   ¦ ¦

  ¦   ¦ L error: The title of a web page has changed after the migration.

  ¦   ¦   The web page URL: 'https://client1domain.test/'

  ¦   ¦   The page title on the source server: 'Domain Default page'

  ¦   ¦   The page title on the target server: 'Default Parallels Plesk Page'

  ¦   ¦   A changed page title might signify the target web server misconfiguration.

  ¦   ¦

  ¦   ¦   Open the migrated site in a web browser and check it for errors.

  ¦   ¦

  ¦   L FTP service 'client1domain.test'

  ¦     ¦

  ¦     L error: Failed to log in over FTP to the web server at 192.168.111.170 as the user pleskclient1: 530 Login incorrect.

  ¦       Make sure that:

  ¦       1. The proper username and password are specified for the subscription in the target Plesk.

  ¦       2. The FTP service is operating properly on the target Plesk.

¦

  ¦       Ignore this warning if you have changed login or password of the system user after transfer.

¦

  L Subscription 'client.test'

¦

    + FTP service 'client.test'

¦

    + SSH service 'client.test'

¦

    + Mail domain 'client.test'

¦

    + DNS zone 'client.test'

    ¦ ¦

    ¦ L info: External DNS servers have no information about the domain. It is possible that the domain name is not registered. Checking by external DNS will be skipped.

¦

¦

    + Apache web site 'client.test'

¦

    L Database service 'client.test'

The report above contains errors found while checking DNS and web content of the domain 'client1domain.test'. As the comment to the issue instructs, there could be problems with DNS migration, so it is worth verifying that DNS records were transferred correctly.

There is an "info" level message that mentions a failed attempt to resolve domain names using a public DNS server. This could not be a sign of a problem in the case when DNS servers of domain registrars were not updated and still point to the source server.