[SERVER-22465] restoring from dump created via mongodump inflates the db Created: 04/Feb/16  Updated: 04/Feb/16  Resolved: 04/Feb/16

Status: Closed
Project: Core Server
Component/s: Admin
Affects Version/s: 3.0.3
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: nadav reichler Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: ALL
Steps To Reproduce:

I used
mongodump
tar -czf ./dump.tar.gz ./dump
(moved the archive to a new server with another instance)

on the second server:
tar -xzf ./dump.tar.gz
mongorestore ./dump

Participants:

 Description   

I attempted to restore a mongo backup from an archived dump. the restoration was successful but the db size grew from 4.5GB to 40GB.

I used
mongodump
tar -czf ./dump.tar.gz ./dump
(moved the archive to a new server with another instance)

on the second server:
tar -xzf ./dump.tar.gz
mongorestore ./dump



 Comments   
Comment by Ramon Fernandez Marina [ 04/Feb/16 ]

nadavreichler, it seems you are compressing your dump with gzip, hence the reduction in size from the original, uncompressed dump.

If you're interested in using compression for your data files you can switch to the WiredTiger storage engine, which supports data compression.

Please note that the SERVER project is for reporting bugs or feature suggestions for the MongoDB server. For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag, where your question will reach a larger audience. A question like this involving more discussion would be best posted on the mongodb-user group. See also our Technical Support page for additional support resources.

Regards,
Ramón.

Generated at Thu Feb 08 04:00:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.