I just tried this module for the first time, and I'd say that it's a very welcome addition to my grown collection of Drupal admin modules. Well done.
I do have one nitpick, however. The backup settings offers "BZip" as a compression option and the resulting file is suffixed ".sql.bz".
The file that I got out of it was, however, compressed with bzip2. The original bzip had software patent issues, has been discontinued for 8 years or so, and is quite hard to come across.
So I'd suggest that this option be renamed "bzip2" (no caps) and the file extension changed to ".sql.bz2" to avoid problems with unarchivers that might get confused about which algorithm to use :)
Comments
Comment #1
ronan CreditAttribution: ronan commentedThanks for the info. I was unaware of the history of bzip. I never actually use it myself and only stuck it in there because it was supported in php and didn't seem like too much more effort. I haven't caught the issue, because I use Mac OS X and the built in archiver seems to handle the .bz files just fine.
Changing the ui is trivial, but I'll have to be careful changing the file extension since that's how the module detects what you're passing to it on restore. I don't want to break compatibility with people's existing backups.
I'll see what I can do about getting this change into the 1.x branch, but may just make the change going forward in the 2.x branch for the sake of consistency.
Thanks
Ronan
Comment #2
Senpai CreditAttribution: Senpai commentedAs of 6.x-2.2 on a RedHatEL server, selecting the 'bzip' setting in a B&M profile will result in a filename of [site-name]-Y-m-d\TH-i-s-mysql.bz.bz2
Unfortunately, this file is not importable by B&M. I think you mean to have a filename ending in H-i-s-sql.bzip2, right?
Comment #3
ronan CreditAttribution: ronan commentedFixed now. Thanks for the info
Comment #4
ronan CreditAttribution: ronan commented