System Requirements for MongoDB

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, clusterAdmin). 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.

  For LVM snapshots, the snapshot retention for LVM snapshot copy must be set to 0 days in the backup plan associated with the MongoDB cluster.

Replica Set Environments

Replica sets must have at least one secondary node.

Protect Encrypted Database

Commvault protects MongoDB Replica Set clusters with encrypted databases. MongoDB clusters should use a local master encryption key file on all the nodes to encrypt the databases. You must configure the bMongoDbEnableBkpEncryptionKey additional setting on all MongoDB clients for both backup and restore operations. The key file is backed up from the source master node during discovery or during a full backup operation.

Restore operations:

• During an In-place full restore operation the key file is restored to the original location (where it was backed up) and the existing key file is renamed automatically.

• During an Out-of-place full restore operation:

  • The key file is restored to all the destination clients.
  • The key file path is created if one is not present.

• During a Granular restore operation the key file is created on the 3DFS share which is used to start the staging server.

• For restore operation, the setting must be enabled on the destination clients only when restoring from encrypted backup.

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 7.x, 6.x, 5.x, 4.4.x, 4.2.x, 4.0.x, 3.6.x, 3.4.x, 3.2.x MongoDB Enterprise edition, MongoDB Community edition, and Percona Server for MongoDB versions 5.x, 4.4.x, 4.2.x

Operating Systems and Processor Architectures

Linux

Windows

Access Node Requirements for Backup Copy Operations

The following are hardware specifications for access node to perform file system backup copy operations for MongoDB backups.

1. Assumes latest generation CPU architecture.

2. Front-End Terabytes (FET): Size of the data on the client computer that has to be backed up.