Start with the database, then filesystem, please

I agree, and that’s what it does. ??

It will dump the database first and then iterate over the wp-content directory.

Cheers,
Mikey

Right, I found the backup folder on the server where you dump the DB, just after posting this.

Let me change my request to this: can we have the pluging beam the dump over to dropbox before doing anything else? Preferrably as a compressed file too.

My backup has been running for ~80 hours now and is nowhere near completion (though the progress bar reports 99%. There seems to be a slight issue with the estimation on the UI side there. :)).

I really like the promise of your plugin and will stick with it – you’ve got a great trajectory in the development of it, and a high standard of work, so I am confident this will become one of the de-facto standards for “fire & forget” WordPress backups.

But as of right now – until I can see it reliably getting the database off the server – I can’t let go of WordPress Database Backup.

Keep up the good work, and don’t kill yourself in these support forums. They get incredibly frustrating at times.

It is “fire & forget” for most which is nice! There are some that run into issues but that is the nature of computing. ??

I will be looking at ways to increase the performance of the plugin and I’ll consider prioritising the DB dump.

I am also aware of the poor estimation on larger then normal sites. It’s on my TODO to fix.

Thanks for sticking with me.

Cheers,
Mikey