• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Backup Failure

D

David Allan

Guest
Hi,

We are running PPP 9.2.3 on CentOS 5 64bit and all of a sudden the plesk backup has stopped working.

-------------- Start print backup log hire --------------
<?xml version="1.0" encoding="UTF-8"?>
<execution-result status="error">
<object name="backup" type="backupowner">
<message severity="error" code="msgtext">The dump have been invalidated by check-dump operation</message>
</object>
<object name="backup" type="backupowner">
<message severity="error" code="msgtext">Runtime error: The check dump failed with code '1'. The dump can contain invalid data! at /usr/local/psa/admin/bin/plesk_agent_manager line 638.
</message>
</object>
</execution-result>
-------------- End print backup log hire --------------

You can view additional information in the log file located in /usr/local/psa/PMM/sessions/2010-03-23-083153.115 directory. This directory will be removed automatically after 30 days

Runtime error: The backup failed with errors!






[08:39:44|INFO:18795:p.log] pmm-ras started : /usr/local/psa/admin/bin/pmm-ras --get-dump-info --dump-file-specification=backup_info_1003230831.xml --session-path=/usr/local/psa/PMM/sessions/2010-03-23-083153.115 --verbose
[08:39:44|INFO:18795:p.log] Repository '/var/lib/psa/dumps' initialising...
[08:39:44|INFO:18795:p.log] Repository '/var/lib/psa/dumps': Initialized
[08:39:44|INFO:18795:p.log] Repository '/var/lib/psa/dumps': Get backup info from backup_info_1003230831.xml
[08:39:44|INFO:18795:p.log] Repository '/var/lib/psa/dumps': Get initial backup info from dir .discovered/backup_info_1003230831
[08:39:44|INFO:18795:p.log] Get backup params from listing of .discovered/backup_info_1003230831
[08:39:44|INFO:18795:p.log] Read properties from xml backup_info_1003230831.xml
[08:39:45|INFO:18795:p.log] Repository '/var/lib/psa/dumps': Validate backup backup_info_1003230831.xml
[08:39:45|INFO:18795:p.log] Repository '/var/lib/psa/dumps': Validate backup (common phase) backup_info_1003230831.xml
[08:39:45|INFO:18795:p.log] Repository '/var/lib/psa/dumps': Get items 'status' for discovered 'backup_info_1003230831' at path
[08:39:45|INFO:18795:p.log] Executing utility: /usr/local/psa/admin/sbin/backup_sign verify /var/lib/psa/dumps/backup_info_1003230831.xml
[08:39:46|INFO:18795:p.log] The utility executed with the return code 0
[08:39:47|INFO:18795:p.log] Repository '/var/lib/psa/dumps': Create item 'status_WRONG-FORMAT' for discovered 'backup_info_1003230831' at path
[08:39:47|INFO:18795:p.log] Repository '/var/lib/psa/dumps': Put info to .discovered/backup_info_1003230831/status_WRONG-FORMAT
[08:39:47|INFO:18795:p.log] pmm-ras finished. Exit code: 0


Can anyone advise?

Many Thanks

David
 
Looks like Guids (unique identity codes) for Parallels Plesk Panel accounts were not generated. Also tables psa.domains and psa.clients have incorrect structure. This is the reason. Deep complex investigation and database correction is required there. Therefore I suggest you contact support team with reference to similar support ticket ID #758991.
 
I have gone through the /var/lib/psa/dumps/backup_info_1003222241.xml file and everything has a GUID that should have one, I have checked the structure of all the psa tables agains a server that works and both match.

One think I have noticed is that even though the server backup fails all but one of the resellers backups succeed, and in that reseller account all but one client backups succeed, I'm going through all the domains now 500+ of them trying to see if one is showing a failed backup, is there a quick way for me to do this?????? I believe that we have one domain that is screwey and fixing that will fix the backup.

Thans
 
I was right all of the domains in the client with the failed backup worked apart from one, I excluded that domain and the backup is all working again. I just need to find out what wrong with that one.
 
Back
Top