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.
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. The key file is backed up from the source master node during discovery or during a full backup operation.
Note
All nodes of the cluster must have the same key file contents.
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 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
-
MongoDB 7.0 is supported only from CPR2023E (11.32) Maintenance Release 55 or higher. The most recent certified version of MongoDB 7.x is 7.0.14
-
The most recent certified version of MongoDB 8.x is 8.0.4.
Percona Server for MongoDB Versions
Percona Server 7.x, 6.x, 5.x, 4.4.x, 4.2.x.
Note
-
Percona 7.x is supported only from CPR2023E (11.32) Maintenance Release 55 or higher.
-
The most recent certified version of Percona Server for MongoDB 7.x is 7.0.14-8.
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 |
-
Assumes latest generation CPU architecture.
-
Front-End Terabytes (FET): Size of the data on the client computer that has to be backed up.