Title: Database engine error
Last modified: June 27, 2021

---

# Database engine error

 *  [wwwolf](https://wordpress.org/support/users/wwwolf/)
 * (@wwwolf)
 * [4 years, 10 months ago](https://wordpress.org/support/topic/database-engine-error/)
 * I’ve been getting errors like this for some time:
    php: ZipArchive::close(): 
   Renaming temporary file failed: No such file or directory, /home/xxxxxxxx/public_html/
   wp/wp-content/plugins/backupwordpress/classes/backup/class-backup-engine-file-
   zip-archive.php, 46 along with numerous iterations of: zip warning: No such file
   or directory
 * But the backups seemed to work OK (tho occasionally fail to complete) so I haven’t
   paid it much attention. However… now I’m also getting:
    Mysqldump: mysqldump:
   Got error: 1286: “Unknown storage engine ‘InnoDB'” when using LOCK TABLES IMysqldump:
   SQLSTATE[42000]: Syntax error or access violation: 1286 Unknown storage engine‘
   InnoDB’
 * When I went looking in the database, I found that, while most tables use MylSAM,
   two WordFence tables use InnoDB. Both engines are supported by the database server,
   the site works fine, and WordFence seems to be happy, so I assume this is OK 
   and it’s just that WordFence needs some of the myriad additional config features
   in InnoDB. But why is BackUpWordPress having a problem with it?
 * I also found that the error messages above are embedded in the database dump.
   Is that a problem — am I going to find that these backups are not actually fully
   functional if I try to restore them? I just tried restoring one to a blank database
   and it looks OK. Weirdly though, viewing a list of tables/engines, whether for
   the restore OR the current ‘live’ database (!), I sometimes (but not always) 
   get a big list of errors…? (I can’t actually replicate that ATM, so can’t post
   an example.)
 * If anyone can throw any light on this (or reassurance if appropriate!) I’d be
   grateful. I’m not that database savvy, so all this took a while to pull together,
   and I’m not sure where to go with it next (other than going back to taking backups
   manually!) Maybe I’m old-fashioned, but I don’t like complicated backup/restore
   plugins, my ideal is a .tgz of the site files and another of the database… but
   this nice simple plugin is the nearest ‘automated’ equivalent, or was ’til it
   started throwing errors…

The topic ‘Database engine error’ is closed to new replies.

 * ![](https://ps.w.org/backupwordpress/assets/icon-256x256.jpg?rev=1105225)
 * [BackUpWordPress](https://wordpress.org/plugins/backupwordpress/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/backupwordpress/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/backupwordpress/)
 * [Active Topics](https://wordpress.org/support/plugin/backupwordpress/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/backupwordpress/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/backupwordpress/reviews/)

 * 0 replies
 * 1 participant
 * Last reply from: [wwwolf](https://wordpress.org/support/users/wwwolf/)
 * Last activity: [4 years, 10 months ago](https://wordpress.org/support/topic/database-engine-error/)
 * Status: not resolved