Plesk for Linux: Migration Best Practices and Use Cases

Created:

2016-11-16 12:48:57 UTC

Modified:

2017-04-24 11:14:27 UTC

1

Was this article helpful?


Have more questions?

Submit a request

Plesk for Linux: Migration Best Practices and Use Cases

Applicable to:

  • Plesk for Linux
  • Plesk 12.5 for Windows

Introduction

This article provides best practices and use cases for troubleshooting issues with a Plesk for Linux migration. Each section of this article contains cross-references to the relevant Plesk Knowledgebase (KB) articles for that particular stage of the migration process.

Helpful information relating to Plesk for Windows can be found in the following KB article:

  • 213930805 Plesk for Windows: Migration Best Practices and Usecases

If you prefer to let Plesk professionals handle the migration or upgrade job for you please check out Plesk professional services options on our website: https://www.plesk.com/professional-services/

Table of contents

Migration & Transfer Manager

Since Plesk 12.5 the new Plesk Migrator was implemented.

For more information refer to Migration Guide .

Make sure you have correctly prepared both of your servers for migration:

Refer to the articles below:

  • 213407929 How must a Plesk server be prepared for migration?

Migrating between different versions of Plesk

  • 213902145 Migration between Redhat and Debian
  • 213400309 Is it possible to migrate from Plesk for Windows to Plesk for Linux and vice versa?

Manual migration hints and tips

If a manual transfer is required (for mail content, a complete server after a crash, database moving, etc.), refer to the following sources:

  • 213927465 How to restore a Plesk installation on the new server after a disaster
  • 213396689 How to restore Plesk from the hard disk drive if the Operating System is broken and the HDD with the old OS and Plesk is mounted in the new system

Connectivity issues

Sometimes, migrating to another server is not possible due to connectivity problems between servers. Please refer to the following articles to check whether this is the case:

  • 115002029405 Migration does not start: “Error: No migration agents found. Data migration is not available”

Error revealed

Periodically, an error may occur within the log files or Plesk user interface messages. In these cases, the following articles may be useful:

  • 213909985 Cannot create domain in Plesk: There are no available resources of this type (domains) left. Requested: 1; available: 0.

    Failed deployment of domain domain.tld

    Execution of /opt/psa/admin/plib/api-cli/domain.php --create domain.tld -owner admin -do-not-apply-skeleton -notify false -guid b55020df-b7a3-4ecc-824e-2bdfb9dab685 -creation-date 2011-09-17 -ignore-nonexistent-options failed with return code 1.
    Stderr is
    An error occurred during domain creation: There are no available resources of this type (domains) left. Requested: 1; available: 0.
  • 213395649 Plesk Backup Manager loads a long time and then fails with error Nginx 504 Gateway Time Out

    2014/01/07 16:49:33 [error] 3235#0: *1483 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 123.123.123.12, server: , request: "GET /plesk/server/backup/local-repository/ HTTP/1.1", upstream: "fastcgi://unix:/var/run/sw-engine.sock", host: "11.12.13.14:8443", referrer: "https://11.12.13.14:8443/admin/server/tools?context=tools"
  • 213906685 Insufficient disk space on the source server to store temporary files for transfer.

    Insufficient disk space on the source server to store temporary files for transfer. Available: 16868 MB. Required: 109833 MB. Please free disk space on the source server.
  • 213958125 Migrating to Plesk 12 on Centos 7 shows warning: python is not supported

    python is not supported
  • 213954625 Migration fails with error "Specified key was too long; max key length is 1000 bytes"

    Runtime error during db: (1, '', 'ERROR 1071 (42000) at line 323: Specified key was too long; max key length is 1000 bytes\
  • 213391589 When using the PMM to migrate Plesk data from FreeBSD, I receive this error after selecting the accounts to transfer:

    readResponse|handle 1|(14) data[Error: unable to connect to database: Can't connect to local MySQL server through socket$
  • 213408649 Subscription migration fails with error "Assertion failed: files.size() == 1"

    Assertion failed: files.size() == 1
  • 115002004529 Migration fails: "Illegal mix of collations"

    Illegal mix of collations
  • 214030889 Default value of MySQL global variable "wait_timeout" on Source or/and Destination server can interrupt migration with error "MySQL server gone away"
    MySQL server gone away
  • 213410469 Domain is not created because of existing DNS records in psa database

    Unable to set domain name: Unable to create the domain domain.tld because a DNS record pointing to the host domain.tld already exists.

Have more questions? Submit a request
Please sign in to leave a comment.