How to sync content between source and destination servers after migration

Created:

2016-11-16 13:15:01 UTC

Modified:

2017-06-21 12:07:14 UTC

11

Was this article helpful?


Have more questions?

Submit a request

How to sync content between source and destination servers after migration

Applicable to:

  • Plesk 12.5 for Linux
  • Plesk Onyx for Linux
  • Plesk Onyx for Windows
  • Plesk 12.5 for Windows

Question

How to sync files, emails and database content between a source and a destination servers after migration?

Answer

The synchronization helps to update already migrated data with a new data from a source server when DNS is not yet switched.

Starting from Plesk Migrator version 2.0, data synchronization for migrated subscriptions can be done from Plesk interface ( Re-sync option, available from Overview and Subscription List tabs):

alttext

When re-sync is done, it will bring in only files and emails that have been created or updated on a source server after the migration is finished. Databases are re-migrated completely.

Also, it is possible to synchronize content via command-line:

Synchronizing all content

To sync content of all domains use the following commands:

Linux:

# cd /usr/local/psa/var/modules/panel-migrator/sessions/<session_dir_name>/
# /usr/local/psa/admin/sbin/modules/panel-migrator/plesk-migrator copy-content

Windows:

cd C:\\Program Files (x86)\\Plesk\\var\\modules\\panel-migrator\\sessions\\<session_dir_name>
"%plesk_dir%/admin/plib/modules/panel-migrator/backend/plesk-migrator.bat" copy-content

If initial migration was done via Plesk interface, it is required to modify config.ini file in order to synchronize content via CLI. Add the following line in both [plesk] for target and [source] for source server directives in %plesk_dir%\\var\\modules\\panel-migrator\\conf\\config.ini file:

windows-password-type = "plain"

As a result, config.ini will look like:

[GLOBAL]
target-type = "plesk"
session-dir = "<session_dir_name>"
skip-log-priority-check = "1"
skip-migrator-updates = "1"
skip-set-session-directory-permissions = "1"
use-separate-log = "1"
source-type = "plesk"
sources = "source"
skip-rpc-agent-deployment = "false"
adjust-applications = "true"

[plesk]
ip = "10.10.10.10"
os = "windows"
windows-username = "Administrator"
windows-password = "*******"
windows-password-type = "plain"

[source]
ip = "20.20.20.20"
os = "windows"
windows-username = "Administrator"
windows-password = "*******"
windows-password-type = "plain"
session-dir = "C:\\panel_migrator"
copy-mail-content = "full"
copy-web-content = "full"
copy-db-content = "full"

[ui]
data-import-type = "selected"
timing-policy = "false"
resync-content = "true"
operability-check = "true"

Otherwise, the following error will appear:

"%plesk_dir%/admin/plib/modules/panel-migrator/backend/plesk-migrator.bat" copy-content
[INFO] Initialize Plesk Migrator
[INFO] Load configuration
[ERROR] The encrypted password is specified in the configuration option 'windows-password' of section 'plesk'. Migration with encrypted passwords is not supported by CLI interface. Replace the encrypted password by plain one (also change the password type to "plain") or set up the plain password in the environment variable 'PLESK_WINDOWS_PASSWORD'.

Synchronizing content separately

Also, content can be synchronized separately. There are three types of content:

  • Mail content
  • Database content
  • Web content

During Mail content synchronization, all mail content is copied from a source server. New mail on a destination server will not be overwritten.

During Database content synchronization, content of a user's database (MySQL/MS SQL) on a destination server is replaced by content from a source server.

During Web content synchronization, files on a destination server are replaced by files from a source server.

For a specific type of content use the following options to sync web, mail and database content accordingly:

  • copy-web-content
  • copy-mail-content
  • copy-db-content

Note : such commands synchronize already migrated objects' content. If during or after a migration, a new database or a mail account is created, it will not be synchronized.

To sync content of certain domains only, use the following instruction:

  • Prepare a migration list containing domains that should be synchronized.

    The list format should be as follows:

    Customer: customer
    example.com
  • Plesk Migrator should be pointed to that migration list directly when executed. For example, to sync web content:

    Linux:

    # /usr/local/psa/admin/sbin/modules/panel-migrator/plesk-migrator copy-web-content --migration-list-file <path-to-the-migration-list>

    Windows:

    "%plesk_dir%admin/plib/modules/panel-migrator/backend/plesk-migrator.bat" copy-web-content --migration-list-file <path-to-the-migration-list>

Additional information

For information about starting migration from CLI, refer to Plesk Migration Guide .

Have more questions? Submit a request

2 Comments

  • 0
    Avatar
    poh inah

     

    Hi
    Can you say, what does mean these asterisks in the string below?

    cd C:\\Program Files (x86)\\Plesk\\var\\modules\\panel-migrator\\sessions\\*****
    C:\\Program Files (x86)\\Plesk\\var\\modules\\panel-migrator\\sessions\\*****>"%plesk_dir%admin/plib/modules/panel-migrator/backend/plesk-migrator.bat" copy-content
  • 0
    Avatar
    Anton Maslov

    @poh inah thank you for the comment!**** - means directory name for the specific session, changed to <session_dir_name> to make the article more

    **** - means directory name for the specific migration session, changed to <session_dir_name> to make the article more informative.

Please sign in to leave a comment.