• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

pleskrestore MySQL tables missing

eugenevdm

Regular Pleskian
I was forced to restore a whole server using pleskrestore, clients, domains, and settings.

The old server ran Fedora Core 6 64-bit and the new server runs Ubuntu 8.04 LTS 64-bit.

I am missing some critical MySQL tables and data for a few databases.

Where I am missing data most of the tables and data is there alphabetically from the top but then towards the end of database some tables and the data is missing.

For example before I might have database 'db_name' with tables:

'categories', 'client', 'logfile', and 'products'

but now I only have:

'categories', 'clients', 'logfile' and 'products' is missing.

This process seems to repeat itself, yet in one instance the whole database is missing.

I thought a good idea to examine the source file and see if I could see if the backup file is intact, but the it's 18 GB in size and doing anything with it takes almost an hour. If I could easily examine the source file I could GUNZIP it and search for the source data to see if it's still intact, but I can't, the file is so difficult to use.

I speculate the problem could be one of three reasons:

1. The data was not backed up properly in the first place. My gut feel is this is not the case and I dearly hope so because I have no other backup to rely on.

2. The restore is failing because of a minor version change or some other peculiarity with restoring from one OS / MySQL to another OS / MySQL. I read with great interest the case of database charset issues in this post http://forum.parallels.com/showthread.php?t=81088 but since I have received no errors I am not sure if this is the case.

3. I also have a theory of timeouts - the one particular table that needs to be inserted is fairly large and I was wondering if MySQL might be timing out.

Nothing I can see in the log file relates to the problem, for example, I don't see any "max key length" errors anywhere that would point at the charset issue.

Please assist urgently.
 
eugenevdm, u were right. in my case it was the consequence of inappropriate backing up of data. i just didn't feel it is necessary..
 
Last edited by a moderator:
Back
Top