After upgrading to 11.5 restore by CLI is not working

[IsmetP]

Yesterday we upgraded V.11 to V.11.5.30. And now we are not able to restore our backups anymore from our main server on our failover server by CLI (we have automated this with cronjobs and need the CLI backup/restore). We have a failover sulotion with two servers and restore the backups of our main server on our failover server!

If we try to create the map file on our failover server, we get the error:
The dump specification '/home/backups/plesk_partnerserver/dumps/backup_info_1308030132.xml' should be inside of dump directory '/home/backups/plesk/dumps'.
/home/backups/plesk_partnerserver/dumps is the path on our failoverserver where we store the backups of our main server and /home/backups/plesk/dumps ist the regular dump path of the failover server.

And if we try to restore the file without creating a map file on our failover server with /usr/local/psa/bin/pleskrestore --restore backup_info_1308030132.xml -level server:
Unable to resolve all conflicts

What happend? Now after upgrading to 11.5 our backup- and failover-solutions are in big trouble!

Our OS is Debian Squeeze
PP is 11.5.30

Greetings from Germany

 

[IsmetP]

pleskrestore (CLI) shows me the following error in debug-Mode:

<?xml version="1.0"?>
<conflicts-description>
<conflict id="1" guid="3769da1a3dddbdf0d...">
<type>
<configuration>
<reason-description>
<required-resource-description>
<db-server host="localhost" type="postgresql" port="5432"/>
</required-resource-description>
</reason-description>
<resolve-options>
<option name="do-not-restore"/>
</resolve-options>
</configuration>
</type>
<conflicting-objects/>
</conflict>
</conflicts-description>

What does it mean? A missing postgresql database server? But we do not have postgresql installed (never). On both servers are the same components and the same plesk version (11.5.30 #11)

 

[IgorG]

Do you have the same output on both servers?

mysql> select * from DatabaseServers;
+----+-----------+------+------------+-------------+----------------+---------------------+----------------+---------------+
| id | host | port | type | admin_login | admin_password | last_error | server_version | parameters_id |
+----+-----------+------+------------+-------------+----------------+---------------------+----------------+---------------+
| 1 | localhost | 3306 | mysql | admin | ******** | no_error | 5.0.95 | 0 |
| 2 | localhost | 5432 | postgresql | | | credentials_not_set | | 0 |
+----+-----------+------+------------+-------------+----------------+---------------------+----------------+---------------+
2 rows in set (0.00 sec)

 

[IsmetP]

Hello Igor,

yes, same output:

Main server:
+----+-----------+------+------------+-------------+----------------+---------------------+----------------+---------------+
| id | host | port | type | admin_login | admin_password | last_error | server_version | parameters_id |
+----+-----------+------+------------+-------------+----------------+---------------------+----------------+---------------+
| 1 | localhost | 3306 | mysql | admin | ******** | no_error | 5.1.66 | 0 |
| 2 | localhost | 5432 | postgresql | | | credentials_not_set | | 0 |
+----+-----------+------+------------+-------------+----------------+---------------------+----------------+---------------+

Failover server:
+----+-----------+------+------------+-------------+----------------+---------------------+----------------+---------------+
| id | host | port | type | admin_login | admin_password | last_error | server_version | parameters_id |
+----+-----------+------+------------+-------------+----------------+---------------------+----------------+---------------+
| 1 | localhost | 3306 | mysql | admin | ******** | no_error | 5.1.66 | 0 |
| 2 | localhost | 5432 | postgresql | | | credentials_not_set | | 0 |
+----+-----------+------+------------+-------------+----------------+---------------------+----------------+---------------+

For your information: If we move the dump files to the regular dump dir of the failover server or change its dump path in psa.conf (as a workaround) and start the restore with debug and verbose mode on, we allways get an error we reported here 289950

 

[IgorG]

I have replied in the mentioned thread.

 

[Fede Marsell]

Same problem here. Exactly. IsmetP has any information about his resolution, please?


/usr/local/psa/bin/pleskrestore --restore BACKUP-FILE -level server -ignore-sign -verbose

<?xml version="1.0"?>
<conflicts-description>
<conflict id="1" guid="3769da1a3dddbdf0d6a213be2eded92c">
<type>
<configuration>
<reason-description>
<required-resource-description>
<db-server host="localhost" type="postgresql" port="5432"/>
</required-resource-description>
</reason-description>
<resolve-options>
<option name="do-not-restore"/>
</resolve-options>
</configuration>
</type>
<conflicting-objects/>
</conflict>
</conflicts-description>
Unable to resolve all conflicts

 

[IsmetP]

Hello Miguel,

sorry, still getting the error! No change and no solution from Parallels yet :-(