I still use UpdraftPlus, but not on a db that large.
I’d be looking at something command line if possible.
The WP CLI command `wp db export` is one of the best ways for larger db’s, then just zip or gzip etc your site files with the db export file.
Should be no problem.
Mysqldump with tar and gz
Try WPvivid.
You have a size of a page that should not rely on plugins for such critical operations. I highly recommend a Hoster that has this highly automated or give you access to the command line interface. And it’s worth for your personal skill set to learn a bit about secure connection, MySQL dumping, zipping and archiving on command line level.
UpdraftPlus documentation states that there is no size limit, but I’ve never had a db that large to test with for real world scenarios.
Your best bet might just be a sqldump in a CRON job.
I had this problem. Turns out that 48 of the 51gb was the postmeta table, and the offending data was meta_name LIKE ‘_oembed%’
once I fucked those records off and optimised the table, I had a 3gb database to deal with.
Updraft maybe but just get an export using wp-cli
1. try to clean db
2. try to optimize db
if you have ssh access, use sql commands
if you have phpmyadmin access, use gui interface
some cache plugins is known to fill wp_postmeta table
I like all in one WP migration.
I still use UpdraftPlus, but not on a db that large.
I’d be looking at something command line if possible.
The WP CLI command `wp db export` is one of the best ways for larger db’s, then just zip or gzip etc your site files with the db export file.
Should be no problem.
Mysqldump with tar and gz
Try WPvivid.
You have a size of a page that should not rely on plugins for such critical operations. I highly recommend a Hoster that has this highly automated or give you access to the command line interface. And it’s worth for your personal skill set to learn a bit about secure connection, MySQL dumping, zipping and archiving on command line level.
UpdraftPlus documentation states that there is no size limit, but I’ve never had a db that large to test with for real world scenarios.
Your best bet might just be a sqldump in a CRON job.
I had this problem. Turns out that 48 of the 51gb was the postmeta table, and the offending data was meta_name LIKE ‘_oembed%’
once I fucked those records off and optimised the table, I had a 3gb database to deal with.
Updraft maybe but just get an export using wp-cli
1. try to clean db
2. try to optimize db
if you have ssh access, use sql commands
if you have phpmyadmin access, use gui interface
some cache plugins is known to fill wp_postmeta table
[removed]