The Commvault Content Store uses the MongoDB database engine to provide a subset of its functionality. This article provides a basic description of how Commvault uses the MongoDB database engine.

General

What version of the MongoDB database engine is installed?

Commvault installs the following versions of MongoDB Community Edition on Windows and Linux computers:

How can I verify that MongoDB is installed?

MongoDB Community Edition is installed as a Commvault service, and is visible in the Commvault Process Manager on Windows and Linux computers.

Where can I find the MongoDB configurations?

MongoDB configurations can be found in the config file located in the Commvault installation directory as follows:

• Windows: <commvault_installation_directory>\MongoDB\Server\cvmongod.cfg
• Linux: <commvault_installation_directory>\MongoDB\Server\cvmongod.conf

Where can I find the MongoDB server binaries?

For both Windows and Linux, you can find the MongoDB server binaries in the following directory:

• <commvault_installation_directory>\MongoDB\Server\Latest\bin

Is the MongoDb installation secure?

To make sure that the MongoDB utility is secure, the following authentication is configured:

• Authentication: The MongoDB instance is configured with user authentication. The master user credentials are created and stored in the CommServe database in an encrypted format, and all Commvault modules use the stored credentials to connect to the MongoDB instance.

Are MongoDB operations logged? If yes, where can I view them?

Yes. MongoDB operations are logged in the following log file in the Commvault installation directory: <commvault_installation_directory>\Log Files\cvmongod.log

Note: Beginning with Feature Release 11.19 up to Platform Release 2023E (11.32), MongoDB logging is disabled by default. This is required to keep the MongoDB.log from becoming too large because rollover with MongoDB is not automatic. However, for Platform Release 2024 (11.34) and later releases, MongoDB logging is enabled by default, since Commvault supports automatic rollover of MongoDB log files. To disable or enable logging, see the KB article Disabling and Enabling Logging for MongoDB Instances.

Maintenance, Issues, and Resolutions

When is MongoDB upgraded to a newer version?

When you upgrade a Commvault release, MongoDB is upgraded to the latest supported version. To determine which version of MongoDB is deployed with a given release, see "What version of the MongoDB database engine is installed?" above.

Can I manually upgrade MongoDB to a newer version?

While you cannot manually upgrade MongoDB to a newer major release (for example, MongoDB 4.0 to MongoDB 4.2), Commvault does provide instructions for upgrading to a newer minor version of MongoDB (for example, MongoDB 4.2.2 to MongoDB 4.2.3).

The instructions that Commvault provides are designed to ensure that Commvault continues to work seamlessly with MongoDB after the upgrade. For more information about upgrading to a newer minor release, see KB article "Manually Upgrading the MongoDB Minor Version".

What should I do if MongoDB is not working ?

For information about troubleshooting MongoDB, see Resolving Errors Detected by a MongoDB Health Check.

What should I do if MongoDB log files occupy an unusually large amount of disk space?

Beginning with Feature Release 11.19 up to Platform Release 2023E (11.32), MongoDB logging is disabled by default, because MongoDB logs are not automatically rotated or cleaned up in those releases. If logging is enabled in these releases, this can lead to MongoDB log files consuming much of the available disk space. You can disable logging if this occurs. For information about disabling or enabling logging, see Disabling and Enabling Logging for MongoDB Instances.

What should I do if I have two instances of MongoDB in the Windows Service Manager?

Note: This applies only to Windows computers that were first installed with Commvault Feature Release 11.20 or previous versions.

Commvault uses only one MongoDB service per instance. The service can be found in the Windows Services Manager as Commvault MongoDB(InstanceXYZ), where XYZ refers to the instance number. If there are additional MongoDB instances installed on the computer that currently runs Commvault, uninstall the additional MongoDB instances using the following steps:

1. Go to Control Panel > Add/Remove Programs, and then uninstall any MongoDB instance listed.
2. Go to the Windows Service Manager, and then remove or delete any instance named MongoDB Server. To delete the instance, open the command prompt in administrator mode, and then run the following command: sc delete [service-name]

How do I un-install or remove the MongoDB package?

Do not remove the MongoDB utility package (not to be confused with the MongoDB database agent), since it is required for the Commvault Commserve and Webserver packages. For any other questions or issues with the MongoDB utility, contact Commvault Customer Support.