Skip to content

Cannot extract database .gz file created by scheduled backup #2915

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
brendanmckeown opened this issue Jan 7, 2016 · 5 comments
Closed

Cannot extract database .gz file created by scheduled backup #2915

brendanmckeown opened this issue Jan 7, 2016 · 5 comments
Labels
bug report Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development

Comments

@brendanmckeown
Copy link

I have scheduled backups enabled, with the "database and media" type selected. On schedule, the system creates a backup file in the /var/backups directory, e.g. 1452176641_media.tgz. When I extract this file on the command line, using: tar -xzf 1452176641_media.tgz, I see a pub and var directory. pub contains the media files as expected. var contains what looks like an archive of the database, e.g. 1452176641_db.gz. However, when I try to extract this file using gzip -d var/1452176641_db.gz, gzip throws an error: gzip: var/1452176641_db.gz: not in gzip format. How can I extract this database file?

@marvincaspar
Copy link

Just rename the file to 1452176641_db.sql and open it in a text editor

@brendanmckeown
Copy link
Author

@mc388,
Thanks, that works! Why is it given a .gz extension in the first place?

@marvincaspar
Copy link

I don't know but I had the same issue a few month ago. Maybe the fix this in the future

@mazhalai
Copy link
Contributor

mazhalai commented Jan 7, 2016

Reopening, since we have to fix this internally, in ticket MAGETWO-47687 to fix this.

@mazhalai mazhalai reopened this Jan 7, 2016
@mazhalai mazhalai added Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development PS bug report labels Jan 7, 2016
@mazhalai
Copy link
Contributor

mazhalai commented Mar 8, 2016

@brendanmckeown thank you for reporting. We have merged a fix in the develop branch, hence closing this ticket. Please create a new ticket if issues still arise.

@mazhalai mazhalai closed this as completed Mar 8, 2016
magento-engcom-team pushed a commit that referenced this issue Jul 30, 2018
[MPI] MAGETWO-84929: Default merchant account ID is used on subsequent partial invoices
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report Issue: Ready for Work Gate 4. Acknowledged. Issue is added to backlog and ready for development
Projects
None yet
Development

No branches or pull requests

3 participants