• Inviting everyone who uses WordPress management tools in Plesk
    The Plesk team is conducting a 60-minute research session that includes an interview and a moderated usability test.
    To participate, please use this link .
    Your experience will help shape product decisions and ensure the tools better support real-world use cases.

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