Title: Empty database dump after update Last modified: August 31, 2016 --- # Empty database dump after update * Resolved [Mihail D](https://wordpress.org/support/users/memberremember/) * (@memberremember) * [10 years, 4 months ago](https://wordpress.org/support/topic/empty-database-dump-after-update/) * was updated only plugin files (not changed any db user permissions or something on server) yesterday logs is ok, today Database size: 526 B * No errors in apache logs. Site working as usual. In archive dump ‘Database and Files’ also db file is empty(526 B as below) * Where can be a reason ? Thank you * ``` -- MySQL dump 10.13 Distrib 5.5.43, for debian-linux-gnu (x86_64) -- -- Host: localhost Database: preved_blog -- ------------------------------------------------------ -- Server version 5.5.43-0+deb8u1-log /*!40101 SET @OLD_CHARACTER_SET_CLIENT=@@CHARACTER_SET_CLIENT */; /*!40101 SET @OLD_CHARACTER_SET_RESULTS=@@CHARACTER_SET_RESULTS */; /*!40101 SET @OLD_COLLATION_CONNECTION=@@COLLATION_CONNECTION */; /*!40101 SET NAMES utf8 */; /*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */; /*!40103 SET TIME_ZONE='+00:00' */; /*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */; /*!40014 SET @OLD_FOREIGN_KEY_CHECKS=@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */; /*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE='NO_AUTO_VALUE_ON_ZERO' */; /*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */; ``` * [https://wordpress.org/plugins/backupwordpress/](https://wordpress.org/plugins/backupwordpress/) Viewing 9 replies - 1 through 9 (of 9 total) * Plugin Contributor [Katrina “Kat” Moody](https://wordpress.org/support/users/katmoody/) * (@katmoody) * [10 years, 4 months ago](https://wordpress.org/support/topic/empty-database-dump-after-update/#post-6977858) * I’m not positive why the SQL would be truncated. Are you able to reach out to us via the support module on the site (on the BackUpWordPress page)? It would be nice to troubleshoot this a little more deeply. * Thanks Kat * Thread Starter [Mihail D](https://wordpress.org/support/users/memberremember/) * (@memberremember) * [10 years, 4 months ago](https://wordpress.org/support/topic/empty-database-dump-after-update/#post-6977863) * Sorry, found error myself * > PHP > ZipArchive Yes > Server > zip command No <– This was a solution mysqldump command mysqldump * Plugin Contributor [Katrina “Kat” Moody](https://wordpress.org/support/users/katmoody/) * (@katmoody) * [10 years, 4 months ago](https://wordpress.org/support/topic/empty-database-dump-after-update/#post-6977873) * Mihail – can you elaborate on that – you enabled the Unix Zip Command and that fixed the issue? That doesn’t have anything to do with the database backup so I’m a little confused. * Thanks, Kat * Thread Starter [Mihail D](https://wordpress.org/support/users/memberremember/) * (@memberremember) * [10 years, 4 months ago](https://wordpress.org/support/topic/empty-database-dump-after-update/#post-6977874) * sorry for your confusion problem still not resolved, still empty dump 🙁 * Plugin Contributor [Katrina “Kat” Moody](https://wordpress.org/support/users/katmoody/) * (@katmoody) * [10 years, 4 months ago](https://wordpress.org/support/topic/empty-database-dump-after-update/#post-6977876) * That’s okay – it sounds like you are having a problem with something we’ve identified as a bug. As soon as the developers have been able to figure out the issue I’ll check back in here and update you, okay? kat * Thread Starter [Mihail D](https://wordpress.org/support/users/memberremember/) * (@memberremember) * [10 years, 4 months ago](https://wordpress.org/support/topic/empty-database-dump-after-update/#post-6977877) * thank you Kat also will investigate(debug) this issue myself little later * Thread Starter [Mihail D](https://wordpress.org/support/users/memberremember/) * (@memberremember) * [10 years, 4 months ago](https://wordpress.org/support/topic/empty-database-dump-after-update/#post-6977879) * is plugin tested on PHP version 5.4 ? * Have 2 servers with the same copied sources+db on 5.6.14 – plugin working correctly but on 5.4.39 – empty tables * can be php version is a reason uncompability ? * Plugin Contributor [Katrina “Kat” Moody](https://wordpress.org/support/users/katmoody/) * (@katmoody) * [10 years, 3 months ago](https://wordpress.org/support/topic/empty-database-dump-after-update/#post-6977904) * That’s an interesting idea and one I’ll definitely alert the developers to, but they unit test the heck out of these to ensure they are running in all the PHP versions indicated (above 5.3 I think?). I’ll check with them in any case. * Thanks Kat * Plugin Contributor [Katrina “Kat” Moody](https://wordpress.org/support/users/katmoody/) * (@katmoody) * [10 years, 3 months ago](https://wordpress.org/support/topic/empty-database-dump-after-update/#post-6977905) * Hey there Mihail – * The developers would like to try and reproduce this error and are having trouble doing so. Would you be willing to work with them and possibly allow access to the server for them to do further troubleshooting? You can enable the support module and reach out to me via that to let me know and I can put them in touch with you that way as well. * Thanks so much, again. Kat Viewing 9 replies - 1 through 9 (of 9 total) The topic ‘Empty database dump after update’ 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/) * 9 replies * 2 participants * Last reply from: [Katrina “Kat” Moody](https://wordpress.org/support/users/katmoody/) * Last activity: [10 years, 3 months ago](https://wordpress.org/support/topic/empty-database-dump-after-update/#post-6977905) * Status: resolved