> CommCell Console > Backup and Restore Agents > Big Data Apps > MongoDB

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, then the MongoDB host name must resolve to an IP address accessible by Commvault and is 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 both Windows and Linux for full backups. Authentication is supported only on Linux for incremental backups.

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

    • root role on the admin database (superuser)

    • backup, restore, and clusterAdmin roles on the admin database as an alternative to superuser access.

  • Logical Volume Manager (LVM) volume groups must have sufficient 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.

Protect Encrypted Database

The Commvault software protects MongoDB Replica Set clusters with encrypted databases. MongoDB clusters must 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 backup and restore operations. During discovery or a full backup, the key file is backed up 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 does following:

    • 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 used to start the staging server.

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

Note

The Encryption at rest support feature that is enabled by bMongoDbEnableBkpEncryptionKey is only supported for replica set clusters.

Sharded Cluster Environments

  • The same database user must be created 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 node.

Supported MongoDB Versions

MongoDB version 8.x, 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 7.x, 6.x, 5.x, 4.4.x, 4.2.x.

Note

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

  • MongoDB 7.0 and Percona 7.x is supported only from CPR2023E (11.32) Maintenance Release 55 or higher.

  • The most recent certified version on MongoDB 7.x is 7.0.14.

  • The most recent certified version of Percona Server for MongoDB 7.x is 7.0.14-8.

Operating Systems and Processor Architectures

Linux

Operating system

Processor architectures

Amazon Linux 2

  • x64

  • Compatible processors

Debian 10 and more recent versions of 10

x64

Oracle Linux 9.x

x64

Oracle Linux 8.x

x64

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

  • x64

  • PowerPC (little endian)

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

  • x64

  • PowerPC (little endian)

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

x64

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

x64

Ubuntu 20.04 LTS

x64

Ubuntu 18.04

x64

Ubuntu 16.04

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

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.

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): Size of the data on the client computer that has to be backed up.

×

Loading...