Backup MongoDB (VBR 12.2)

[BostjanUNIJA]

Hi.
During the upgrade VBR from 12.1 to 12.2 I noticed in the wizard about new features regarding MongoDB:
"Protect MongoDB deployments effortlessly, without the need to leverege pre-freeze and post-thaw scripts, using our new policy for MongoDB. Additionaly , our new Veeam Explorer for MongoDB allows for easily recovering replica sets, databases, and individial collections".

So I took a look on one of the jobs backing up a Windows 2019 VM where I know that DEV team have MongoDB installed on that VM.
Application awareness is enabled for that VM (using credentials of local admin). But on APP awareness configuration page I was expecting there would be a tab with settings for MongoDB, but there was none (only MSSQL, ORACLE, etc...)
And if I open Veeam explorer for MongoDB I don't see any MongoDB collections.
So what am I missing?

B

[karsten123]

it is only supported on linux

[BostjanUNIJA]

Hi Karsten123.
Thank you for your reply.
Yep, after posting the question I went searching for this MongoDB backup with Veeam and found OS requirements page:
https://helpcenter.veeam.com/docs/backu ... ml?ver=120

So if not on Linux distro no joy :/
Will need to move MongoDB from Win environment into Linux. Already added to short-term plan.
Thanks.

[Gostev]

@PetrM FYI

[PetrM]

Hello,

@BostjanUNIJA I have a couple of questions:
1. You have just one VM or do you have several MongoDB servers? If it's not just one VM, do you have replica sets/sharded clusters or standalone only?
2. Do you have Enterprise or Community edition of MongoDB?

Also, please keep in mind that only replica set deployments are currently supported. You can find more information about this feature in our user guide.

Thanks!

[BostjanUNIJA]

Hi PeterM.
Thank you for your reply. I need to check that with team and will report.
But basically as far as I know 1 Windows VM holds MongoDB and already the idea is to transfer this to Linux VM.

[PetrM]

Hi Bostjan,

Many thanks for your reply! In fact, if you store data files and journals on the same volume, you won't even need to lock a database to obtain a consistent backup. You can find more information about the supported backup methods on this page. However, I suggest performing test restores to an isolated environment or running SureBackup to ensure that the workload is usable after the restore.

If there are separate volumes for data files and journals, you will need to lock a database prior to backup. I recommend using the pre-freeze/post-thaw scripts that call fsync lock/unlock functions to prepare a database for snapshot creation.

Thanks!

[BostjanUNIJA]

Hi PetrM.
Are pre-freeze/post-thaw scripts still necessary with version 12.2 VBR?

[PetrM]

Yes, if you have a standalone server and if data files and journals reside on the separate volumes.

Thanks!