Pre-migration Checks

Various issues may occur during the transfer of domains, and some of them can be detected before a migration is started. Using the migration tool, you can check the following areas that might be a source of most common issues:

To run these checks, issue the corresponding command.

The following explains in detail all checks performed by the migration tool.

Target Plesk Services

For each service, the following is checked: the process is running on the system, it is listening on certain ports, and it is possible to connect to the target server (specified in the configuration file) on these ports (except for database services, as availability check is not performed for them). The following services are checked: Web, FTP, mail, DNS, and databases. Database services are checked only if the corresponding database server exists in Plesk, it is local, and credentials are specified for access to it. For example, if there are no PostgreSQL database servers registered in target Plesk, the corresponding service will not be checked.

Note that if any of these services are bound to a non-default port, the corresponding check will report an error. You can ignore it if you are sure that the service in question is functioning and is available.

The migration tool also does not check external services, only local ones. For example, if you have an external MS SQL database server, registered in target Plesk, it will not be checked. At the same time, if you have an external DNS server in Plesk and the local DNS service is turned off, the corresponding check will report an error. You can ignore it if you are sure that the service is functioning and is available.

Specific checks are different on Unix and Windows and are listed below.

Unix service checks

On Unix, the “ps ax” command is used to retrieve a list of running system processes and “netstat -tpln” to retrieve the binding between processes and ports. The following is checked for each service:

Windows service checks

On Windows, the “tasklist” command is used to retrieve a list of running system processes and “netstat -an” to retrieve the binding between processes and ports. The following is checked for each service:

Plesk Control Panel

The process of checking Plesk is similar to service checks, the only difference is the checking whether Plesk is available via XML-API. The following items are checked:

There is no checking whether the Plesk license allows creating the necessary number of domains, so no errors will be shown even if a trial license key is installed in Plesk.

Business Model Consistency

In addition to domains, the migration tool also transfers all business objects associated with them, such as domain owners (resellers), customers, and service plans. Such objects will be created on the target server if they do not exist, but if an object with the same name already exists in target Plesk, it will not be changed and a transferred domain will be associated with it. To avoid this, you can perform various checks for each business object.

Reseller checks
Customer checks
Service plan check
Infrastructure

One of the main purposes of the migration tool is to initiate and track the process of copying domains with web content between source and target servers. To ensure that all content can be transferred successfully, the following checks should be performed: