Almost perfect.

I Haven’t been using it for very long, but so far every feature I’ve tested works well. My one critique would be that, restoring a previously saved database only overwrites (or puts back if missing) the tables you saved. It does not also remove tables added after the time of the save point. When I restore a database, unless otherwise noted, I want that database to look exactly the way it did when I saved it. This means if you make a save point, then add some new plugin that spams your DB with tables, then go to restore your database, you’ll still have to manually hunt through your database and remove the tables left by the offending plugin. This is a pain and the reason why I installed WP-DBManager to begin with (my current backup plugin behaves similarly when dealing with db backups which sucks). Overall, works well and you shouldn’t need to restore that often, so the extra work to ensure no extra garbage tables are lurking around in your db, shouldn’t be to much of a problem. I wish there was an option for a full replacement of the saved database with the restore instead of its current behavior of writing over tables. This topic was modified 6 years, 1 month ago by Sicut Unum .