How to check Plesk migration status

Question

How to check a migration session status? 

Answer

The status can be checked in log files. 

Migration is performed in several parallel threads (by default, 5). So, it is not correct just to open the log file and check the last entry to get the migration status.

To check the migration status:

1. Log in to the target server via SSH

2. Open progressfile. It will contain information like:

   Subscription migration status:
   CONFIG_TEXT: +-----------------------------------------------+------------------------+--------+
   | Subscription | Status | Action |
   +-----------------------------------------------+------------------------+--------+
   | example.com | In Progress | |
   +-----------------------------------------------+------------------------+--------+
   | example2.com | Finished with warnings | |
   +-----------------------------------------------+------------------------+--------+
   | example3.com | Finished with warnings | |
   +-----------------------------------------------+------------------------+--------+
   | example4.com | Finished with warnings | |
+-----------------------------------------------+------------------------+--------+


3. Find the task that has the In Progress status and remember the name of subscription it handles.

4. Open debug.log and find the subscription name from step the step 3. Check the number of thread that is handling the subscription (ST1...ST5). For example:

   CONFIG_TEXT: =|2019-07-18_04:55:20,456|I|ST1|core.reports.printer|example.com||Subscription 'example.com'

5. Filter debug.logby the thread number and check the last entry to find out the task status:

   For Windows:
   

   C:\> findstr ST1 debug.log

   For Linux:
   

   # grep ST1 debug.log

Migration of a big domain or a significant number of mailboxes may take several hours. In such cases, no changes may be seen in the log files, but continually decreasing free disk space on disk drive will indicate that the process is running. If no changes are seen in the aforementioned files for hours and no changes on the file system/mailboxes, it is likely that the migration process got hung up. Restart the session according to this article.