- This topic has 19 replies, 2 voices, and was last updated 5 years, 12 months ago by admin561.
-
Posts
-
Hello, and thank you in advance for any help.
We run a very large WordPress Multisite network* and have been successfully using Updraft to perform remote backups for at least 6± months. Suddenly the last two manual backup attempts take forever, or fail with the “Not Finished” message. The last attempt has been running for nearly three days. Past successful backups would take an hour or so.
What would I be looking for in the log file to indicate any problem? Our log file alone is 180+ MB, so I’d rather not upload it again. All the most recent 200+ log entries include “adding to final database dump” without any indication of a cause for the failure. Granted, I have not reviewed all the 1.6 million lines…
Last log message: backup_2018-04-09-1416_Tripawds_Blogs_2fbadcb2eee5-db-table-wp_3891_links.table.gz (10907/15423): adding to final database dump (Apr 11 09:17:20)
This is not an issue with max_timeout or memory limits as many backups have successfully completed before and nothing has changed on the server end.
I’m curious about the recommendation to “define(‘UPDRAFTPLUS_NO_BINZIP’, true);” since I found various old support topics suggesting that, with contradictory feedback here.
The issue started occurring after the most recent Updraft update to (Version 2.14.5.24).
Please advise how I can troubleshoot further.
*FYI: This is a legacy WPMU install later converted to a WPMS network, which has caused issues with certain plugins in the past. Though those problems should be irrelevant, since Updaraft is just dumping all data, not interacting with specific tables.
Hi,
Would it be possible to split off the last few runs worth of the log (Each run is shown by the number in brackets on each line), and send us a copy?
You would need to use an online service such as Pastebin, and post the link here.Could you also check the PHP error logs for any errors occurring around the time of the backup?
Best Wishes,
David NHi,
Thank you.
From the log, it appears that the backup is being timed out when attempting to finish creating the database backup archive, due to the large number of database tables.
If possible, please could you try increasing the max_execution_time to 600 seconds?
If you find that a backup is taking too long, you can abort it in the Current Status tab.
Best Wishes,
David NHi,
Apologies for the delay.
From the log, it appears that the backup was still making progress at the time.
Did the backup complete successfully?
Best Wishes,
David NHi,
From the log, it appears that the backup process is struggling with some files in the blogs.dir directory.
Are there any sub-sites with any particularly large files (such as videos)?
The log file should display if the backup is manually aborted.
Best Wishes,
David NHi,
Yes, you can delete the backups on the server.
However, these should not have effected the backups, as the updraft directory is automatically skipped.I will consult with my colleagues to try and find a solution.
Best Wishes,
David NHi,
Apologies for the delay.
It appears that your new PHP installation does not have the php-zip module installed.
As such, the (much) slower PclZip is being used.Please could you ask your hosts/server admins to enable the php-zip module?
Best Wishes,
David N
- The topic ‘Large Backups Now Failing after Update’ is closed to new replies.