# System Requirements for MongoDB

Verify that your environment meets the system requirements.

## All Environments

- All mongod and mongos 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.

- If the client name and the MongoDB host name differ, the MongoDB host name must resolve to an IP address that is accessible by Commvault and included in the MongoDB `bind_ip` setting.

- The security.keyFile parameter value must be identical across cluster nodes.

## Linux Environments

- Database authentication is supported on Windows and Linux for full backups. For incremental backups, authentication is supported only on Linux.

- For MongoDB deployments with authentication enabled, use a database user with one of the following role configurations:

  - `root` role on the admin database (superuser)

  - `backup`, `restore`, and `clusterAdmin` roles on the `admin` database as an alternative to the `root` role.

- Logical Volume Manager (LVM) volume groups must have enough free space to create IntelliSnap snapshots. By default, the copy-on-write (COW) cache size is 4096 MB or 10% of the volume size, whichever is greater. You can increase the COW cache size if needed.

  Note

  - As a best practice, keep at least 10% free space in the volume group. This free space is typically sufficient for environments with low to moderate write activity. If your workload changes data frequently, you may need more free space to prevent the snapshot from becoming invalid.

  - For native LVM snapshots, the lvm.conf setting event_activation in the /etc/lvm/lvm.conf file can be set to either 0 or 1. Both settings are supported.

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

### Protect Encrypted Database

Commvault protects MongoDB replica set and sharded clusters that use encrypted databases. MongoDB clusters must use a local master encryption key file on all nodes to encrypt databases. During discovery or a full backup, the software backs up the key file from the source master node.

Note

All nodes of the cluster must have the same key file contents.

- For encrypted database restores, the Commvault software performs the following actions:

  - In-place restore

    - Restores the key file to its original location.

    - Automatically renames the existing key file.

  - Out-of-place restore

    - Restores the key file to all destination clients.

    - Creates the key file path if it does not exist.

  - Granular restore

    - Creates the key file on the 3DFS share that is used to start the staging server.

- Enable encryption on the destination clients only when restoring from an encrypted backup.

## Sharded Cluster Environments

- Create the same database user on all shard servers and 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 nodes. No client is associated with the arbiter during node discovery, and this does not impact backup or restore operations.

## Job Results Directory Space Requirements

For incremental backups, the software creates oplog dump files every 15 minutes in the job results directory.

Ensure that the job results directory has sufficient free space to accommodate the cumulative size of the oplog dump files that are generated until the next incremental backup.

Note

If the available free space in the job results directory is insufficient, incremental backup operations might fail.

## Supported MongoDB and Percona Server Versions

### MongoDB Versions

Operating system | Processor architectures | MongoDB 8.x | MongoDB 7.x
--- | --- | --- | ---
Amazon Linux 2023 AMI | x86_64 | Yes | Yes
Amazon Linux 2 | x86_64 | NA | Yes
Debian 12 | x86_64 | Yes | Yes
RHEL/Rocky/Alma/Oracle Linux 9.x | x86_64 | Yes | Yes
RHEL/Rocky/Alma/Oracle Linux 8.x | x86_64 | Yes | Yes
RHEL/Oracle Linux 7.x | x86_64 | NA | Yes
SuSE Linux 15 | x86_64 | Yes | Yes
SuSE Linux 12 | x86_64 | NA | Yes
Ubuntu 24.04 | x86_64 | Yes | NA
Ubuntu 22.04 | x86_64 | Yes | Yes
Ubuntu 20.04 | x86_64 | Yes | Yes
Windows Server 2022 | x86_64 | Yes | Yes
Windows Server 2019 | x86_64 | NA | Yes

Note

- The latest certified version of MongoDB 7.x is 7.0.14

- The latest certified version of MongoDB 8.x is 8.2.3.

- The `mongodump` and `mongorestore` database tools must be version 100.3.0 or later. The `--config` option used for YAML file–based input of credentials is available only in these versions.

### Percona Server for MongoDB Versions

Percona Server 7.x

Note

- The latest certified version of Percona Server for MongoDB 7.x is 7.0.14-8.

- The `mongodump` and `mongorestore` database tools must support the `--config` option for YAML–based credential input.

## Access Node Requirements for Backup Copy Operations

The following hardware specifications apply to the access node that performs file system backup copy operations for MongoDB backups.

Components | Extra Large | Large | Medium | Small | Extra Small
--- | --- | --- | --- | --- | ---
CPU/RAM 1 | 16 CPU cores, 128 GB RAM (or 16 vCPUs/128 GB) | 12 CPU cores, 64 GB RAM (or 12 vCPUs/64 GB) | 8 CPU cores, 32 GB RAM (or 8 vCPUs/32 GB) | 4 CPU cores, 24 GB RAM (or 4 vCPUs/24 GB) | 2 CPU cores, 16 GB RAM (or 2 vCPUs/16 GB)
Front End Terabytes (FET) 2 | 90 TB to 120 TB | 50 TB to 100 TB | 25 TB to 50 TB | 10 TB to 25 TB | 5 TB to 10 TB

1. Assumes latest generation CPU architecture.

2. Front-End Terabytes (FET): The amount of client data that must be backed up.

×

Loading...