The big data guided setup guides you through creating a server backup plan and adding the MongoDB cluster.
Go to the Big Data Guided Setup
From the navigation pane, go to Guided setup.
The Welcome page appears.
On the Protect tab, at the bottom of the page, click More.
Click the Big data apps tile.
The Big data app setup page appears.
If you already completed the guided setup, the Apps page appears.
Create a Server Backup Plan That You Can Use for MongoDB
If you already have a server backup plan that you can use, you can skip this step.
On the Create server backup plan page, click Create a new plan, and then specify the settings for a server backup plan that you can use for the MongoDB cluster.
Settings | Steps |
|---|
Plan name | Choose whether to create a new plan or use a base plan. In Plan name, enter a name for the server plan.
|
Backup destinations | Click Add copy. The Add copy dialog box appears. In Name, enter a name for the backup destination. From the Storage list, select the storage to use for the backups. If you selected storage that uses Distributed Storage, the Optimize for instant clone toggle key appears. By default, this setting is turned on to allow the associated Distributed Storage to optimize backups for clones, using Copy Data Management. To turn off the setting, move the Optimize for instant clone toggle key to the left. The setting does not apply to HyperScale solutions that use Distributed Storage. You can use the MRR cool storage class (Metallic Recover Reserve) for creating secondary copies, but not for creating primary copies. To specify the start time for backups on a specific date and later, move the Backups On and After toggle key to the right. For Retention rules, enter the amount of time to retain the backups. To specify additional backups, such as weekly full backups, move the Extended retention rules toggle key to the right, and then add rules. Click Save. To add additional regions to the backup destination, move the Multi-region toggle key to the right, and then select the regions. You can also add more regions and associate the storage copy to the region.
|
RPO | For Backup frequency, click Add. The Add backup frequency dialog box appears. From the Backup type list, select the backup type, and from the for list, select All agents or Databases. Specify the frequency of the backup. To specify the client time zone or to add exceptions, move the Advanced toggle key to the right. From the time zone list, select the time zone according to which the backups must run. To add exceptions when backups must not run, click Exceptions and add exceptions for any day or week of a month. These exceptions will repeat every month.
For Backup window (if incremental and differential backups are supported for the workload), specify when you want incremental and differential backups to run. For Full backup window, specify when you want full backups to run.
|
Snapshot options | Under Snapshot options, do the following: Specify how to retain snapshots: To specify a number of jobs to retain on a snapshot copy, select Number of snap recovery points, and then enter the number of jobs to retain. To specify a retention period, select Retention period, and then enter the amount of time to retain the jobs.
If you don't want to create backup copies, move the Enable backup copy toggle key to the left to turn it off. For Backup copy frequency, enter how often to run backup copy jobs.
|
Database options | Under Database options, do the following: For Log backup RPO, enter how often to run log backups. To automatically back up the database logs to the MediaAgent cache, do the following: Move the Use disk cache for log backups toggle key to the right. For Commit, enter how often to commit the logs to the CommServe computer. Disk caching of database logs applies to the following: Informix, Microsoft SQL Server on Windows, Oracle, Oracle RAC, and SAP HANA.
|
Override restrictions | |
Add the MongoDB Cluster
On the Add a big data app page, from the Application type list, select MongoDB.
If no MongoDB master node is found, a message appears, with a link that you can use to download and install the Commvault software on the master node so that you can select it from the Master node list.
In the Cluster name box, enter a name for the cluster.
From the Master node list, select the master node.
In the Binary path box, enter the path to the folder that contains the mongod or mongos executable file.
In the OS user name box, enter the OS user name that you want to use to run the MongoDB servers.
Commvault software uses the OS user name to start the MongoDB servers after the restore operation.
Note: The OS user must have the permission to start the server and have ownership of the files in dbPath.
In Port number box, enter the mongod or mongos port number.
To back up MongoDB clusters in both Windows and Linux environments, under Database authentication, you can enter the credentials of an account to authenticate with.
Note: Log backups with authentication are not supported on Windows.
The account must have one of the following on the admin database:
The root role. This is a superuser role.
The backup, restore, clusterMonitor, and hostManager roles. If you do not want to assign a superuser role to the database user, use these roles.
From Plan, select the server backup plan to use for the cluster.
Click Save.