MongoDB Oplog restore error

Hey @Mauro,

I’m no MongoDB expert but I found a case that maches your symtoms almost exactly. The issue was some parameters in the mongodb configuration file that caused the issue. The settings they had may not exactly match your issue but perhaps this is somewhere to start looking.

Customer had below option set in their MongoDB configuration file and this was not present in the commvault created config file, which caused the compressor issue. On setting the below registry key to pass the additional parameters while starting the server, restore completed successfully.
 

Option set in the MongoDB config file:

wiredTiger:

    engineConfig:

      journalCompressor: zlib

 

Registry key added:

sMongoDbRecoveryArgs

Path:iDataAgent

Type:String

- For a single argument: arg1 (converted to --arg1)
- For two or more arguments: arg1#arg2#..#argn (converted to --arg1 --arg2 --argn)
- For arguments with a value: arg1#arg2+arg2value#arg3 (converted to --arg1 --arg2 arg2value --arg3)

Value:wiredTigerJournalCompressor+zlib

https://documentation.commvault.com/additionalsetting/?q=sMongoDbRecoveryArgs

Hi

Just an update. I found additional information on the required permissions and have applied them with the same error. 

 

I just want to give a short update. We’ve created a custom role in Mongo and it seems to have resolved the restore error. I want to just complete a few more tests, before I post what we did.