Error When Backing Up: Table postmeta has very many rows

[ChrisParticipant]

Hi there,

While trying to back up a site, we receive this error:

Warning: Table wp82_postmeta has very many rows (459247) – we hop your web hosting company gives you enough resources to dump out that table in the backup

While searching the help forum, we found someone else who ran into this, but they said their backup was still completed even though they received the same error. We let ours run for days before we checked, came back to look at the backups and only see this on the latest backup:

Not Complete

We run into the same issue if we try to migrate the site. The migrations on the destination is not complete.

Can someone help us troubleshoot this and get it fixed?

Thanks!

-chris.

[Dee NutbourneModerator]

Hi Chris,

Could you please send us a copy of the backup log? This can be found in the Existing Backups tab of the UpdraftPlus settings page.
The contents will be too long to post here directly, but you can use an online service such as Dropbox or Pastebin, and post the link here. You can also set your reply to ‘private’.

Do you use any plugins that track post revisions? If so, could you see if there is a method of clearing this log?

Best Wishes,
David N

[ChrisParticipant]

This reply has been marked as private.

[ChrisParticipant]

This reply has been marked as private.

[udadminKeymaster]

Hi Chris,

The log shows that on your server, PHP is allowed to run for approximately 50 seconds, before being killed off. The problem is that the postmeta table on your site is larger than PHP can process in that time. Consequently, there are 3 possible resolutions:

1) You can reduce the size of your postmeta table. To do this, you’d need to inspect what’s in it that may be consuming so many rows (you have nearly half a million entries, which is huge). This could be unprocessed comments, or spam comments – but that’s just one possibility; there are many.

2) Or, you could ask the server admin to allow PHP to run for longer.

3) Or, you could ask the server admin where the “mysqldump” binary is found on your webserver, and add a line in your wp-config.php identifying the location:

define(‘UPDRAFTPLUS_MYSQLDUMP_EXECUTABLE’, ‘/path/to/mysqldump’);

mysqldump can dump out MySQL data significantly faster than PHP – but is not found on your server in any of the standard locations.

David

[ChrisParticipant]

This reply has been marked as private.

[Author]

Posts