1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Migration from a broken machine

Discussion in 'Plesk for Linux - 8.x and Older' started by Hak Foo, Jan 16, 2008.

  1. Hak Foo

    Hak Foo Guest

    Our current host runs Plesk 8.1.1, but Pleskbackup or Pleskrestore is broken in some way. (see below for more details)

    We're planning to migrate to another host with Plesk 8.2, using its PMM.

    My concern: How dependent is PMM on the old system? Everything else works right, more or less, but if it requires pleskbackup to work, and it doesn't, then we might well have a crisis here.

    Alternatively, can someone help me fix pleskbackup?

    The backups appear to go fine, but they don't restore, with an error of

    0: /usr/local/psa/admin/plib/common_func.php3:151
    psaerror(string 'Unable "RestoreClient"::getDumpDescription(): Empty error message from utility.')
    1: /usr/local/psa/admin/plib/backup/BackupInfo.php:119
    2: /usr/local/psa/admin/plib/backup/BackupClientInfo.php:91
    3: /usr/local/psa/admin/plib/backup/BackupClientInfo.php:80
    4: /usr/local/psa/admin/plib/backup/BackupClientInfo.php:21
    5: /usr/local/psa/admin/plib/PMM/MigrationCObject.php:102
    6: /usr/local/psa/admin/htdocs/backup/backup_info.php:28

    When I look at the XML data, it's got a lot of superfluous ^@ characters:

    Manual attempts to create a map from the command line fail with invalid-token errors.

    < limit name="blablabla" >-1^@^@^@^@^@^@^@^@^@^@^@^@< /limit >