Unreliable database backup

Submitted by peacebellservers on Thu, 12/15/2016 - 12:04

Hi, I faced serious problem losing a database backup, because my backups marked as successful had error so now I can't recover from this backups as thay hasn't performed with success and it is not logged and no alert

LOCK TABLES #__acymailing_userstats WRITE; /!40000 ALTER TABLE #__acymailing_userstats DISABLE KEYS */; Error: Couldn't read status information for table jopsg3_assets () mysqldump: Couldn't execute 'show create table jopsg3_assets': Table 'reciklaza.jopsg3_assets' doesn't exist (1146) /!40000 ALTER TABLE #__acymailing_userstats ENABLE KEYS */; UNLOCK TABLES;

---------------end of database dump --------- no log about error -------I assumed it as backup but it is not Lost database.

Status: 
Active

Comments

Submitted by andreychek on Thu, 12/15/2016 - 12:39

Howdy -- hmm, that's a pretty unusual error!

You're correct, Virtualmin should be notifying you if there's a problem with the backup, and Jamie will be able to respond more to that.

Just to clarify though, are you saying the above error occurred, but the backup status was listed as "OK"?

However, when reviewing the backup logs, the above error shows up?

Submitted by peacebellservers on Thu, 12/15/2016 - 15:24

Yes its status is ok,

42 servers backed up successfully, 0 had errors.

Submitted by JamieCameron on Thu, 12/15/2016 - 19:22

Also, was a table perhaps deleted from your database at the same time the backup was being taken?

Submitted by peacebellservers on Fri, 12/16/2016 - 03:51

All backups for this database (maybe some other, need to check all that) one full and other incremental, one month and half ago are screwed the same way ... ending just after begining with 'Error: Couldn't read status information for table' - hasn't been any complaints

Submitted by JamieCameron on Fri, 12/16/2016 - 18:44

If you connect to MySQL manually and run a command like show create table jopsg3_assets , does it work?

Submitted by peacebellservers on Sat, 12/17/2016 - 00:40

I can't reproduce it, I don't have that database anymore.. isn't it point of trapping mysql errors as error in this case it was Error: Couldn't read status information for table' , no matter what produce it .

Submitted by JamieCameron on Sat, 12/17/2016 - 01:31

The problem is that the mysqldump command which Virtualmin calls completely fails when it hits an unreadable table, so we have to mark the entire domain's backup as failed.