• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Migration from a broken machine

H

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
BackupInfo->getDumpDesc()
2: /usr/local/psa/admin/plib/backup/BackupClientInfo.php:91
BackupClientInfo->parseBackupDesc()
3: /usr/local/psa/admin/plib/backup/BackupClientInfo.php:80
BackupClientInfo->domainListIni()
4: /usr/local/psa/admin/plib/backup/BackupClientInfo.php:21
BackupClientInfo->stepBegin()
5: /usr/local/psa/admin/plib/PMM/MigrationCObject.php:102
MigrationCObject->make()
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 >
 
Back
Top