Hmm I have never heard of this issue before. Does it happen on a fresh install of WP with this plugin?
I have not done a fresh install in a awhile but yes as I remember it has happened before on a fresh install. It is almost like an echo of the backup command happens.
That is weird, I can’t reproduce this on my end on a fresh install on my local though. I will leave this open to see if anybody have the same issue.
If it is a scheduled backup, WP cron scheduler might trigger twice?
I would recommend using this http://support.hostgator.com/articles/specialized-help/technical/wordpress/how-to-replace-wordpress-cron-with-a-real-cron-job
I just did a manual backup on a db that had no problems. I got two backups at the same date and time stamp of 12:59.
This may be useful to you.
Yeap looks like it is a WP scheduler problem which makes it difficult to reproduce because WP scheduler is not a true cron. So they might be two guys hitting your site at the same time right down to the same second, triggering the cron job at the same time. This is really out of my control though.
Try the link I pasted above instead.
I am not sure what you mean by two guys hitting my site at the same time. I am the only admin and the only one that does backups manually. Otherwise the software does the backups. Is there some kind of injection or similar problem with what you say is happening. Could someone inject data into the db in the form of transients for example.
Hmm nope you got it wrong. I think it might be too technical for me to explain.
I would suggest reading up on how WordPress cron works. WordPress cron is triggered based on visitors from your site.
Interesting about WP cron and visitors. Would a hack attempt of constantly hitting the login or enough probing attacks to trigger a WP cron be used to do a db injection? This site and one other were attacked by brute force recently and I have been having problems with the db jumping or doubling in size soon after. How I find out is when wp-dbmanager emails the db to me. Do you think it would be possible to use the wp cron to stuff transients with hacked info or create transients in the db?
After my experiences with nextgen transients from the earlier versions have junk stuffed into them, I don’t trust transients much. I will look at the WP cron per your link above. Thanks for that.
Hmm I am not sure of the transients part. But technically speaking it should not unless there is a security hole in one of the plugins.
May I interest you in another of my plugin called WP-Sweep https://ww.wp.xz.cn/plugins/wp-sweep/. It will clear away your transients
This db increase thing has happened on two different sites running somewhat different plugins except for the security ones. Both have been the focus of recent brute force attacks and as far as I can tell were unsuccessful. I have long suspected transients as being a problem with core WP but am not enough of a tech to prove it.
I am currently using wp-optimize which allows for cleaning of the transients. But they come back soon after removal. How is your plugin different?
transients always comes back because they are meant to be temporary, so if they are going, the plugin will recreate them again.
If you are using WP-Optimize then you are good already =) The main difference between WP-Sweep and WP-Optimize is:
This plugin uses proper WordPress delete functions as much as possible instead of running direct delete MySQL queries.
