System Requirements for MongoDB

Updated

Verify that your environment meets the system requirements.

All Environments

  • All instances must run with configuration files in the YAML format.

  • If the ports between the master node and the other cluster nodes are blocked, the nodes must connect through a firewall.

Linux Environments

  • Database authentication is supported on both Windows and Linux for full backups. Authentication is supported only on Linux for incremental backups.

  • The user account that you authenticate with must have one of the following role or roles on the admin database:

    • The root role. This is a superuser role. If you choose to overwrite the database or collection, you must grant the root role to the MongoDB user.

    • A set of roles (backup, restore, clusterMonitor, hostManager). If you do not want to assign the superuser role to the database user, then use these roles.

  • Logical Volume Manager (LVM) volume groups must have adequate free space for creating the IntelliSnap snapshots. The default COW cache size is set to 4096 MB or 5% of the volume size, whichever is greater. You can increase the COW cache size.

Replica Set Environments

  • Replica sets must have at least one secondary node.

Note: If you have a single node replica set that has only a primary node, add the bMongoDBEnableBkpForSingleNodeRepSet additional setting to the client node that you want to back up.

  • The Encryption at rest support feature is supported for replica set clusters using local key mechanisms with the same key on all nodes. Additional settings must be configured on the source nodes for the encryption key file to be backed up. The file also needs to be present on the destination clients for the restore operation.

    During in-place restores, the encryption key file is restored to its original location. Existing key files are renamed. During out-of-place restores, the encryption key file is restored to the same path as the path discovered in the destination cluster. If the destination cluster does not have encryption enabled, it is restored to the path where it was in the source cluster.

Sharded Cluster Environments

  • The same database user must be created on all the sharded servers and on the config server.

  • Each sharded server must be a replica set, and the replica set must have at least one secondary node.

  • The Commvault software is not required on the arbiter node.

Supported MongoDB Versions

MongoDB version 3.2.x, 3.4.x, 3.6.x, 4.0.x, 4.2.x, 4.4.x, 5.x, 6.x, MongoDB Enterprise edition, MongoDB Community edition, and Percona Server for MongoDB versions 4.2.x, 4.4.x, 5.x

Note: Starting from MongoDB 4.4, the mongodump and mongorestore utilities must be downloaded separately and copied to the bin path.

Operating Systems and Processor Architectures

Linux

Operating system

Processor architectures

Amazon Linux 2

  • x86

  • x64

  • ARM64

  • Compatible processors

Debian 10 and more recent versions of 10

  • x86

  • x64

Red Hat Enterprise Linux/CentOS 8.x with glibc 2.17.x

  • x86

  • x64

  • PowerPC (little endian)

Red Hat Enterprise Linux/CentOS 7.x with glibc 2.17.x

  • x86

  • x64

  • PowerPC (little endian)

Red Hat Enterprise Linux/CentOS 6.x with glibc 2.12.x

  • x64

SuSE Linux 12 (Initial Release/SP1 and later SPs) with glibc 2.19.x and higher

  • x86

  • x64

SuSE Linux 15 (Initial Release/SP1 and later SPs) with glibc 2.26.x and higher

  • x86

  • x64

Ubuntu 20.04 LTS

  • x86

  • x64

Ubuntu 18.04

  • x86

  • x64

Ubuntu 16.04

  • x86

  • x64

Windows

Operating system

Processor architectures

Windows Server 2019

All Windows-compatible processors

Windows 2016

All Windows-compatible processors

Windows 2012

All Windows-compatible processors