• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Restoring backup

D

Dataphone

Guest
Hi,

anyone had this problem?

I have 2 servers. Both use the same IP net and I want to take the backup taken on the old server that completed successfully and restore it on the new server.

The problem is that when ever I try to restore the file to the new server I get an error stating that " archive don't contain file 'xxxxxxx' " How is it possible that the backup states all is fine but the restore cannot find the files??

On the old server I am running Plesk for windows 7.0.2_build040921.10 and on the new one I am running Plesk for windows 7.0.3_build041216.02
Both servers run windows 2003 standard server.

Seems the real problem actually is that the backup stores information about some mysql databases and there are no databases. Therefore when running restore the restore soft tries to restore the databases. (But there are noone??)

How come it tries to backup empty mysql database directories?

Now we have managed to find out that if you create a domain/customer and activates mysql for them the backup system tries to back that database up. Problem is there are no database there. Therefore the restore system cannot it.

We've solved it by adding a database/table for the customers that have thsi activated. Then the restore seem to work flawless. Strange behavior I think.
 
Back
Top