I am looking for advice on getting several of my blogs to successfully backup to Dropbox using BackupBuddy.
I have been working with BackupBuddy support, but they feel very strongly that the solution is for DreamHost to allow my backup process to run with more memory. I tried manually increasing the memory to 256MB in phprc, but as expected this process seems to have gotten killed by the DreamHost monitoring process. It seemed like 128MB was a safer manual increase (over my default of 90MB) but this did not seem to be enough memory for BackupBuddy to run (or maybe the monitor also killed it?).
My blogs are not huge (in my opinion). The blogs that are failing to backup range in size (database and files) from about 35MB to about 250MB.
I know that one of the limitations that is causing a problem is that the Dropbox API which BackupBuddy uses requires that the entire backup file be transferred in a single step, and that the entire file be held in memory during that transfer step. It seems like process overhead causes this to be too much for my shared hosting plan even with the smaller 35MB backup.
While I know that it would be better if BackupBuddy provided an incremental backup option, or wrote a more robust transfer routine which would break the full backup set into safer-sized chunks (instead of a single zip file), that’s not how the software works and I don’t know if there is any plan to change it. It would also be better if the Dropbox API provided a chunking transfer like Amazon S3 does, but again - don’t know when/if that will change.
Unfortunately, my refund request ($100) has so far been ignored or denied (not sure which) by BackupBuddy. Their techs seem to feel very strongly that the problem should be resolved by DreamHost allowing more memory.
Any advice would be greatly appreciated!