Pleskrestore crisis

[Hak Foo]

I always used to use pleskbackup all, but I can't stage a 20Gb backup on the amount of free space.

Fine, I'll build a script which backs up one domain, then FTPs it.

The problem is recovery.

I decided to check if the backup was valid:

/usr/local/psa/bin/pleskrestore --create-map ./DOMAINNAME.backup -map DOMAIN.map

It dies with
Traceback (most recent call last):
File "/usr/local/psa/admin/share/supervisor/processor.py", line 83, in getStatus
return (None, self.realGetStatus())
File "/usr/local/psa/admin/share/supervisor/processor.py", line 413, in realGetStatus
info = dump_format.readInfo(fh)
File "/usr/local/psa/admin/lib/python/dump_format.py", line 399, in readInfo
xml.sax.parse(fp, i)
File "/usr/lib/python2.4/xml/sax/__init__.py", line 33, in parse
parser.parse(source)
File "/usr/lib/python2.4/xml/sax/expatreader.py", line 107, in parse
xmlreader.IncrementalParser.parse(self, source)
File "/usr/lib/python2.4/xml/sax/xmlreader.py", line 123, in parse
self.feed(buffer)
File "/usr/lib/python2.4/xml/sax/expatreader.py", line 211, in feed
self._err_handler.fatalError(exc)
File "/usr/lib/python2.4/xml/sax/handler.py", line 38, in fatalError
raise exception
SAXParseException: /var/backups/restore/dump-plesk.xml:11:33: not well-formed (invalid token)

It creates a "restore" directory with two files: plesk-map and supervisor.log


The Supervisor.log file is XML and contains a block which says

2007-11-20 10:42:45,846 INFO Outgoing packet:
<?xml version="1.0" encoding="UTF-8"?><action-response action-internal-name="AwaitingRestoreObjectsState">
<finished status="error">
<message code="Error in AwaitingRestoreObjectsState.getStatus()">
<context></context>
<file></file>
<line></line>
<text>Traceback (most recent call last):
File &quot;/usr/local/psa/admin/share/supervisor/processor.py&quot;, line 83, in getStatus
return (None, self.realGetStatus())
File &quot;/usr/local/psa/admin/share/supervisor/processor.py&quot;, line 413, in realGetStatus
info = dump_format.readInfo(fh)
File &quot;/usr/local/psa/admin/lib/python/dump_format.py&quot;, line 399, in readInfo
xml.sax.parse(fp, i)
File &quot;/usr/lib/python2.4/xml/sax/__init__.py&quot;, line 33, in parse
parser.parse(source)
File &quot;/usr/lib/python2.4/xml/sax/expatreader.py&quot;, line 107, in parse
xmlreader.IncrementalParser.parse(self, source)
File &quot;/usr/lib/python2.4/xml/sax/xmlreader.py&quot;, line 123, in parse
self.feed(buffer)
File &quot;/usr/lib/python2.4/xml/sax/expatreader.py&quot;, line 211, in feed
self._err_handler.fatalError(exc)
File &quot;/usr/lib/python2.4/xml/sax/handler.py&quot;, line 38, in fatalError
raise exception
SAXParseException: /var/backups/restore/dump-plesk.xml:11:33: not well-formed (invalid token)
</text>
</message>
</finished>
</action-response>

after several reports of successfully reading packets

When you look at line 11 of dump-plesk.xml, it's
<limit name="disk_space">-1(about 30 control-@s)</limit>
This is weird.

[Update]
Further analysis:

Removing all those superfluous Control-@ characters lets the restore proceed further, but then it barfs up on one of ose "multi-part seperator" lines.

I suspect pleskbackup may be making a busted backup.

 

[Ch0p]

Hi,

I'm stuck with exactly the same problem here. The plesk restore function dies with the same error report and stores it in a restore directory. This directory contains 2 files: dump-plesk.xml and supervisor.log. The dump-plesk.xml is a not well formed xml document which looks like the expected map file but with a lot of NULL values. Does anybody know how to continue the restore and recover the backup files and database??

regards,
Maarten

 

[Hal9000]

i have the same problem. how to solve?