• 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

pleskrestore dont work on Plesk 11.5.30#13

evilduff79

New Pleskian
Hi, I set up a new empty machine with Plesk 11.5.30#13 on CentOS6.

Now I create a new backup with:
Code:
/usr/local/psa/bin/pleskbackup --server --output-file=./dump_test1

I create a map file:
Code:
/usr/local/psa/bin/pleskrestore --create-map ./dump_test1 -map ./my_map1.map

An then I try to restore the backup on the same machine, I get the following error message:
Code:
 /usr/local/psa/bin/pleskrestore --restore ./dump_test1 -verbose -map ./my_map1.map -level server

PHP Warning: fread(): 263 is not a valid stream resource; File: /usr/local/psa/admin/plib/StreamXMLReader.php, Line: 107

2013-09-04T21:59:43+02:00 ERR (3)  [panel]: Failed to read data from stream:
0: StreamXMLReader.php:109
        StreamXMLReader->parse()
1: StreamXMLReader.php:176
        StreamXMLReader->read(string 'conflicts-description', integer '2', integer '1', integer '0')
2: StreamXMLReader.php:245
        StreamXMLReader->sub(string 'conflicts-description', integer '2')
3: PMMResponseRestoreTaskResult.php:27
        PMMResponseRestoreTaskResult->getConflictsDescription()
4: cuPleskRestore.php:563
        cuPleskRestore->doRestore(array, string '/srv/datensicherung/temp/backup_info_1309042143.xml', object of type RestoreMapping, NULL null, string '/srv/my_map1.map')
5: cuPleskRestore.php:708
        cuPleskRestore->cmdRestore(string './dump_test1')
6: cuPleskRestore.php:208
        cuPleskRestore->__construct()
7: pleskrestore.php:9
ERROR: Exception: Failed to read data from stream (StreamXMLReader.php:109)

Is this a current problem in the version #13? Is there a solution?
The problem is the same on all my other servers with Plesk 11.5.30#13.

Greets Philipp
 
I've the same problem...

But I wanted to restore a backup from another vserver with the same plesk version (11.5.30 Update #14)

Is there any solution for this problem?



EDIT:

I tried the following:

Code:
/usr/local/psa/bin/pleskrestore --restore /var/lib/psa/dumps/bak__info_1309020207.xml -level server -filter list:CLIENT.LOGIN -map /var/lib/psa/dumps/mapfile.map    

Unable to resolve all conflicts

I tried to restore the backup in the plesk panel gui (browser), All I got is

Code:
Warning:	
Deployer has been terminated by exception:
Nothing more.... :-(

So, I checked the Backup with
Code:
/usr/local/psa/bin/pleskrestore --check-backup /var/lib/psa/dumps/bak__info_1309020207.xml
the result: backup is valid.

I should say that this backup includes a few child backups as you could see in the following log --> dump_object27.xml

Here are the last few lines of my /usr/local/psa/PMM/logs/restore[Date]/deployer.log

Code:
[2013-09-16 22:32:59.865|26489] INFO: Add map item: domain#[MYDOMAIN_TO_BE_RESTORED] --> /opt/psa/PMM/rsessions/20130916223257120/dump/dump_object27.xml
[2013-09-16 22:32:59.865|26489] INFO: Add content base map item: domain#[MYDOMAIN_TO_BE_RESTORED] --> /var/lib/psa/dumps/domains/[MYDOMAIN_TO_BE_RESTORED]
[2013-09-16 22:32:59.865|26489] INFO: Starting restore of: /opt/psa/PMM/rsessions/20130916223257120/dump/info.xml
[2013-09-16 22:32:59.865|26489] DEBG: Validate dump using restore specification: /opt/psa/PMM/restore-specification.xsd
[2013-09-16 22:32:59.890|26489] INFO: StdException[55851764-8249-46cd-849a-f2f888897bc3^@]: Deployer has been terminated by exception:  [./main.cpp:294]
int act(config&)
[2013-09-16 22:32:59.891|26489] INFO: deployer finished. Exit code: 1
 
Last edited:
Have nobody a solution? The same problems on 11.5.30 Update #14 on command line. A restore over Plesk-Panel at "Backup Manager" works at the most time. But not at command line. I tested the backup before I start the restore with:
/usr/local/psa/bin/pleskrestore --check-backup
and I get "backup is valid".
 
I think that there are some database inconsistency. This issue required detailed investigation directly on your server. Therefore I suggest you contact Support Team.
 
Back
Top