After you have verified that the transferred subscriptions work correctly on the target server, you need to finalize the migration and switch the target server to a production environment.
The finalization steps are:
After migration has been completed, public users continue to access the source server: new email messages arrive, databases records are updated, and so on. To avoid the loss of recent changes, we recommend that you run the content transfer operation one more time before switching entirely to the new server. To do it, issue the following command:
panel-migrator copy-content config.ini
This command synchronizes changes in:
The migration tool uses rsync for the synchronization of web content. This makes the synchronization efficient.
Mail content on Plesk for Unix is also synchronized by using rsync. Mail content on Windows is synchronized using a Plesk utility.
Database content transfer is less efficient: each time you run the copy-content command, the migration tool creates a dump, transfers, and restores each database. A new database dump overwrites the existing databases on the target server.
There are commands that you can use to transfer only one type of hosting content. The commands are:
copy-web-content — copies only the web content
copy-mail-content — transfers the contents of user mailboxes
copy-db-content — transfers the contents of MySQL and Microsoft SQL Server databases
The final step of the migration is to make DNS queries for the migrated domains resolve to the IP addresses on the target server. In this step, you need to provide customers with the new IP addresses and ask them to contact their registrars so as to point domain name servers to new IP addresses.
Previous page
Next page
Locate page
Link to this page