jgjh151,
Thanks for the feedback and sorry so frustrating. The reason I separate the files and folder isnt to make it hard but to deal with really large sites.
If I dont break the backup into small pieces then we often see timeouts during the backup or when downloading.
However, I do agree that I could make it easier for smaller sites like yours. In the past we did have a single sql file and then just one folder for each under wp-content but we were forced to break the backups into smaller and smaller pieces as the plugin was deployed to larger and larger sites.
So with all that said, what could I do to make it easier? Could you also share how large your site is? If you still have WPBackItUp installed you can just share the size of the single backup file.
Thanks again for the feedback. Its tough to hear but constructive criticism just helps us get better.
Chris
Give the option to have a single SQL file that can be imported and be done with. Simple.
Give option for single ZIP of site backup that I can upload and extract.
If you do this you’ll be golden. Went through 5 backup plugins so far and not offer this. They all save things in there own file extension and bundle in @ssbakwards formats that only work if you’re restoring using the plugin.
There is already an option for a single zip file. Take a look in settings. This option is fairly memory intensive so it may not work for you. Really just depends on your host and site size. If the setting is on the backup will attempt to stick all the zip files in a single zip. If it cant then the backup wont fail but WPBackItUp will just turn off the setting so it doesn’t keep trying on ever backup.
You can also change the Batch Size option for databases to a much larger number like 100000. This would tell WPBackItUp to export 100,000 rows to each SQL file so at least then you would only have 1 SQL file for every table. Not ideal but hopefully better. Give that a try and let me know if it helps. If the backup fails on Db export then your database is just too large and an export would likely fail even on a export using a MySQL tool.
Lastly, the single SQL file is possible for a small site and sounds like a good idea. As I said before, we separated it into multiple files because large sites would just timeout on the DB export. But adding the single SQL file as an option like single zip file backup is a good idea. May not work if your site is too big but you could at least try.
Lemme see what I can do. Will post something here after I review.
Chris
jgjh151,
I was able to get this working for you last night. Please create a support ticket using the link below and I will send you instructions on how to install a pre-release version of WPBackItUp that will contain a single SQL file with your entire database.
http://www.wpbackitup.com/support/
Thanks
Chris
