MongoDB restore fails with "stored size exceeds source size" error

Article ID: 78149

Article Type: Troubleshooting

Last Modified:

If the journalCompressor option is not available in the Commvault config file, the MongoDB restore fails. 

Symptoms

MongoDB server does not start, and the following error appears in the MongoDB log file:

2022-08-29T16:07:27.784+0200 E  STORAGE  [initandlisten] WiredTiger error (0) [1661782047:784401][1732977:0x7f886f9cdc00], txn-recover: WT_COMPRESSOR.decompress: stored size exceeds source size Raw: [1661782047:784401][1732977:0x7f886f9cdc00], txn-recover: WT_COMPRESSOR.decompress: stored size exceeds source size

Causes

The MongoDB restore fails because the journalCompressor option is not available in the Commvault configuration file, which causes a compressor problem.

Resolution

To the client computer, set the sMongoDbRecoveryArgs additional setting to wiredTigerJournalCompressor+zlib, and then run the restore job.

1 Commvault Way, Tinton Falls, NJ 07724 Sitemap | Legal Notices | Trademarks | Privacy Policy
Copyright © Commvault | All Rights Reserved.