Title: UpdraftPlus database backups fail Last modified: October 15, 2024 --- # UpdraftPlus database backups fail * Resolved [minterrors](https://wordpress.org/support/users/minterrors/) * (@minterrors) * [1 year, 7 months ago](https://wordpress.org/support/topic/updraftplus-database-backups-fail/) * I am having an issue with backing up the database on a windows based IIS server, windows 2022. * The Plugins, Themes, Uploads and Others complete successfully. * The Database fails no matter if it is backed up individually or with the other files listed above. * The last successful database backup was on Sep 28th. * I AM able to backup the MYSQL Tables via MySQL workbench under the admin tab * Watching the backup, it apparently gets hung up on * Table wp_wffilemods: Total expected rows (approximate): 132553 * Here is a snip of the log: * 7226.796 (9) Scheduling a resumption (10) after 300 seconds (1728781664); but the job will then be aborted unless something happens this time 7226.853 (9) Creation of backups of directories: already finished 7226.880 (9) Saving backup status to database (elements: 13) 7226.920 (9) Resuming creation of database dump (WordPress DB) 7226.945 (9) SQL compatibility mode is: NO_ZERO_IN_DATE,ERROR_FOR_DIVISION_BY_ZERO, NO_ENGINE_SUBSTITUTION 7226.983 (9) Testing potential mysqldump binary: C:\Program Files\MySQL\MySQL Workbench 8.0\mysqldump.exe 7227.152 (9) Output: /*!40103 SET @OLD_TIME_ZONE=@@TIME_ZONE */;\n/*!40103 SET TIME_ZONE=’+00:00′ */;\n/*!40014 SET @OLD_UNIQUE_CHECKS=@@UNIQUE_CHECKS, UNIQUE_CHECKS=0 */;\n/*!40014 SET @OLD_FOREIGN_KEY_CHECKS =@@FOREIGN_KEY_CHECKS, FOREIGN_KEY_CHECKS=0 */;\n/*!40101 SET @OLD_SQL_MODE=@@SQL_MODE, SQL_MODE=’NO_AUTO_VALUE_ON_ZERO’ */;\n/*!40111 SET @OLD_SQL_NOTES=@@SQL_NOTES, SQL_NOTES=0 */;\nDROP TABLE IF EXISTS `wp_options`;\n/*!40101 SET @saved_cs_client = @@character_set_client */;\n/*!50503 SET character_set_client = utf8mb4 */;\ n (truncated – 1539 bytes total) 7227.173 (9) Working binary mysqldump found:“ C:\Program Files\MySQL\MySQL Workbench 8.0\mysqldump.exe” 7227.206 (9) Table wp_options: corresponding file already exists; moving on 7227.232 (9) Table wp_users: corresponding file already exists; moving on 7227.262 (9) Table wp_usermeta: corresponding file already exists; moving on 7227.295 (9) Table wp_actionscheduler_actions: corresponding file already exists; moving on 7227.332 (9) Table wp_actionscheduler_claims: corresponding file already exists; moving on 7227.332 (9) Table wp_actionscheduler_groups: corresponding file already exists; moving on 7227.332 (9) Table wp_actionscheduler_logs: corresponding file already exists; moving on 7227.332 (9) Table wp_commentmeta: corresponding file already exists; moving on 7227.332 (9) Table wp_comments: corresponding file already exists; moving on 7227.332 (9) Table wp_links: corresponding file already exists; moving on 7227.333 (9) Table wp_postmeta: corresponding file already exists; moving on 7227.333 (9) Table wp_posts: corresponding file already exists; moving on 7227.333 (9) Table wp_term_relationships: corresponding file already exists; moving on 7227.333 (9) Table wp_term_taxonomy: corresponding file already exists; moving on 7227.362 (9) Table wp_termmeta: corresponding file already exists; moving on 7227.362 (9) Table wp_terms: corresponding file already exists; moving on 7227.362 (9) Table wp_wc_category_lookup: corresponding file already exists; moving on 7227.362 (9) Table wp_wc_product_meta_lookup: corresponding file already exists; moving on 7227.362 (9) Table wp_wc_reserved_stock: corresponding file already exists; moving on 7227.362 (9) Table wp_wc_tax_rate_classes: corresponding file already exists; moving on 7227.362 (9) Table wp_woocommerce_order_itemmeta: corresponding file already exists; moving on 7227.362 (9) Table wp_woocommerce_payment_tokenmeta: corresponding file already exists; moving on 7227.362 (9) Table wp_aioseo_cache: corresponding file already exists; moving on 7227.362 (9) Table wp_aioseo_notifications: corresponding file already exists; moving on 7227.362 (9) Table wp_aioseo_posts: corresponding file already exists; moving on 7227.362 (9) Table wp_rank_math_404_logs: corresponding file already exists; moving on 7227.362 (9) Table wp_rank_math_internal_links: corresponding file already exists; moving on 7227.362 (9) Table wp_rank_math_internal_meta: corresponding file already exists; moving on 7227.362 (9) Table wp_wc_admin_note_actions: corresponding file already exists; moving on 7227.362 (9) Table wp_wc_admin_notes: corresponding file already exists; moving on 7227.362 (9) Table wp_wc_customer_lookup: corresponding file already exists; moving on 7227.362 (9) Table wp_wc_download_log: corresponding file already exists; moving on 7227.363 (9) Table wp_wc_order_addresses: corresponding file already exists; moving on 7227.363 (9) Table wp_wc_order_coupon_lookup: corresponding file already exists; moving on 7227.388 (9) Table wp_wc_order_operational_data: corresponding file already exists; moving on 7227.388 (9) Table wp_wc_order_product_lookup: corresponding file already exists; moving on 7227.388 (9) Table wp_wc_order_stats: corresponding file already exists; moving on 7227.388 (9) Table wp_wc_order_tax_lookup: corresponding file already exists; moving on 7227.388 (9) Table wp_wc_orders: corresponding file already exists; moving on 7227.388 (9) Table wp_wc_orders_meta: corresponding file already exists; moving on 7227.388 (9) Table wp_wc_product_attributes_lookup: corresponding file already exists; moving on 7227.388 (9) Table wp_wc_product_download_directories: corresponding file already exists; moving on 7227.388 (9) Table wp_wc_rate_limits: corresponding file already exists; moving on 7227.388 (9) Table wp_wc_webhooks: corresponding file already exists; moving on 7227.388 (9) Table wp_wfblockediplog: corresponding file already exists; moving on 7227.388 (9) Table wp_wfblocks7: corresponding file already exists; moving on 7227.388 (9) Table wp_wfconfig: corresponding file already exists; moving on 7227.388 (9) Table wp_wfcrawlers: corresponding file already exists; moving on 7227.388 (9) Table wp_wffilechanges: corresponding file already exists; moving on 7227.393 (9) Table wp_wffilemods: Total expected rows (approximate): 128303 7768.211 (10) Opened log file at time: Sun, 13 Oct 2024 01:11:45 +0000 on [https://minterrors.org](https://minterrors.org) 7768.228 (10) UpdraftPlus WordPress backup plugin ([https://updraftplus.com](https://updraftplus.com)): 1.24.6 WP: 6.6.2 PHP: 8.2.11 (cgi-fcgi, Windows NT WIN-4D75KOSJ9D7 10.0 build 20348 (Windows Server 2022) AMD64) MySQL: 8.0.34 (max packet size=67108864) WPLANG: en_US Server: Microsoft-IIS/10.0 safe_mode: 0 max_execution_time: 900 memory_limit: 256M (used: 93.4M | 98M) multisite: N openssl: OpenSSL 3.0.8 7 Feb 2023 mcrypt: N LANG: ZipArchive::addFile: Y 7768.250 (10) Free space on disk containing Updraft’s temporary directory: 3796111.6 MB 7768.285 (10) Requesting backup semaphore lock( cb950e1fc446) 7768.327 (10) [Info] Lock (updraft_lock_cb950e1fc446, wp_options) acquired 7768.376 (10) Backup run: resumption=10, nonce=cb950e1fc446, file_nonce =cb950e1fc446 begun at=1728774137 (7768s ago), job type=backup 7768.426 (10) [ Updraftplus] The backup is being aborted for a repeated failure to progress. 7768.452 (10) An error condition has occurred for the first time during this job 7768.477 (10) [Info] Lock option (updraft_lock_cb950e1fc446, wp_options) released 7768.512 (10) Fetching RSS news feed 7769.306 (10) Fetched RSS news feed; result is a: SimplePie 7769.393 (10) Sending email (‘Files (database backup has not completed) (Full backup)’) report (attachments: 1, size: 174.7 KB) to: info@… 7771.063 (10) The backup attempt has finished, apparently unsuccessfully - This topic was modified 1 year, 7 months ago by [minterrors](https://wordpress.org/support/users/minterrors/). Viewing 1 replies (of 1 total) * Plugin Support [vupdraft](https://wordpress.org/support/users/vupdraft/) * (@vupdraft) * [1 year, 7 months ago](https://wordpress.org/support/topic/updraftplus-database-backups-fail/#post-18077614) * It looks like your WordFence table is timing out the backup. Upping your max memory might help, can you try adding this to your wp-config.php * define( ‘WP_MEMORY_LIMIT’, ‘512M’ ); * I would also optimise your DB using the free plugin WordPress Optimize: getwpo. com * Finally it might be worth reaching out to the WordFence team to see if there is an easy way to empty this table/clear data. Viewing 1 replies (of 1 total) The topic ‘UpdraftPlus database backups fail’ is closed to new replies. * ![](https://ps.w.org/updraftplus/assets/icon-256x256.jpg?rev=1686200) * [UpdraftPlus: WP Backup & Migration Plugin](https://wordpress.org/plugins/updraftplus/) * [Frequently Asked Questions](https://wordpress.org/plugins/updraftplus/#faq) * [Support Threads](https://wordpress.org/support/plugin/updraftplus/) * [Active Topics](https://wordpress.org/support/plugin/updraftplus/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/updraftplus/unresolved/) * [Reviews](https://wordpress.org/support/plugin/updraftplus/reviews/) * 1 reply * 2 participants * Last reply from: [vupdraft](https://wordpress.org/support/users/vupdraft/) * Last activity: [1 year, 7 months ago](https://wordpress.org/support/topic/updraftplus-database-backups-fail/#post-18077614) * Status: resolved