Hi
Just a question, but when I do a local backup, I get a 1.3mb file, oppose to a download backup, that gets 10.3 mb.
With the large one, I can't make a restore using this module. I have use phpmyadmin, and the site gets messy, but after clear all caches, and re-login, it survives.
Dont' see no config for the download backup, so I guess his using the same profile as local backup.

Not sure why this happen or when it started to happen. I can still use the local backup, but as the send to email id now broken, I would like to fix this.
Anyone notice this behavior, or just me ?

Thanks

Comments

mesnitu created an issue. See original summary.

Dr Trichome’s picture

Dr Trichome commented

Yes, I have seen this issue. The backup that is stored locally is compressed (.gz). When I download the backup, my browser automatically uncompresses it. When I try to restore using the uncompressed backup, I get some odd behavior because I believe that backup_migrate is expecting a compressed backup file. The cure: (1) disable the automatic de-compression from your browser, (2) save the backup locally and move it to your computer using rsync or some other command line tool, (3) save the backup locally and move it to your computer using cPanel or another web-based file manager. I hope this helps.
My setup:
drupal 7.39
backup_migrate 7.x-3.1
Safari 8.08

xaqrox’s picture

xaqrox
he/him
Primary language English
Location Washington, D.C.
commented
Status: Active » Closed (duplicate)

Duplicate of #2494009: compression not happening on database backup. Don't think disabling the browser's decompression is the real fix, since in #2494009-7: compression not happening on database backup it's mentioned that downloading other (non-B&M) .gz files works fine. Downloading not using a browser is a legit workaround (it's what I ended up doing), but not a real fix either.

xaqrox’s picture

xaqrox
he/him
Primary language English
Location Washington, D.C.
commented
Related issues: +#2494009: compression not happening on database backup