ngc6751

Hi Katmoody.

To answer your questions, here were the steps:
1) I upgraded WordPress to 4.7 as well as all existing plugins.
2) I didn’t delete BackupWordpress first. I just upgraded it like all the others, all within roughly one hour.
3) I also added a few new plugins and spent time configuring them.
4) There were formatting issues, so I spent a day to get everything to work properly.
5) I was happy with how everything was working and let my website rest for 24 hours, then began to add new content.
6) I did 3 specific manual backups using BackupWordpress at critical stages of my upgrading process and downloaded them, Jan 10, Jan 14AM, Jan 14PM.
7) When I tried to do a clean reinstall of those 3 backups I ran into the same problem with each: current files (i.e. new pix in the wp-content folder… Good Job!) but accessing an old database, with old menus, no header picture, old posts, and a media tab that did not show all the new pix I had uploaded, etc. Weird! Because BackupWordPress uses the same database name for all 3 backups, I have no idea what database each backup was accessing at the time of download. Beyond that, I don’t quite know what to say.

A few days ago, I downloaded a database using phpMyAdmin, the related files with Filezilla, then did a clean reinstall. Needless to say, that worked fine, as the timing of both was synchronous. Whether a plugin can imitate that behavior or not ALL THE TIME, I don’t know. This is highly technical stuff that is beyond me.

Thanks for the kind inquiry and sorry for the rather shocking title. My whole point here is to help others avoid the stupid mistake I made. I’ve looked at a bunch of other plugins. It seems they all have their issues and yours is one of the best. Let’s face it: life’s a mystery and to quote Forrest Gump “Shit happens!”

Hi Katmoody,

Thanks for the feedback. To be honest, I still can’t figure it out completely. All I know for sure is the following:

1) A recent backup from Jan14, 2017, shows all the new photos I uploaded on Jan 14. So it looks like the file backup was from the correct folder and current.
2) But when I look at the sql file in the zip folder, it’s from Jan 10, 2017. Hmmm!

When I try to do a clean installation into a new folder and a new database, with wp-config pointing to the new database, the backup doesn’t work. I don’t get it. In fact, the database looks like a database from a long time ago with older posts, older media and older menus. Weird!

So that’s why I say that the files seem to be current, but somehow the plugin selected the wrong database. Beyond that, I don’t know what else to say.

I will continue to monitor this plugin. It seemed to work fine for years and I can only conclude that because I’m doing a major overhaul of my site, the plugin is not tracking with all the changes I’m making on an hourly basis, even if I do a manual backup.

Thanks.

P.S. Here’s a minor suggestion for an upgrade: When I look at the backup zip folder that I download from your plugin, every single sql file is named the same as follows: database-domain.ext-default-1.sql. This is not very useful as it does not tell me which database you accessed, especially if I have 5 databases all linked to my .com domain. Perhaps nomenclature like database-domain.ext-dbname-1.sql would help a lot. It doesn’t have to be all 16 characters… maybe just the first 6 characters of the db name.

Just a suggestion.

• This reply was modified 9 years, 2 months ago by ngc6751.
• This reply was modified 9 years, 2 months ago by ngc6751.
• This reply was modified 9 years, 2 months ago by ngc6751.