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.

  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.

Protect Encrypted Database

The Commvault software protects MongoDB replica set and sharded clusters with 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 key file is backed up from the source master node.

• 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.

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 nodes. No client is associated with the arbiter during node discovery, and this does not impact backup or restore operations.

Supported MongoDB and Percona Server Versions

MongoDB Versions

Percona Server for MongoDB Versions

Percona Server 7.x, 6.x, 5.x, 4.4.x, 4.2.x.

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.