The big data guided setup guides you through creating a server backup plan and adding the MongoDB cluster.
If you already have a server backup plan that you can use, you can skip this step.
Settings
|
Steps
|
Plan name
|
-
Fill in the following plan information:
-
Choose whether to create a new plan or use a base plan.
-
If you selected Create a new plan, in the Plan name, enter a name for the server plan.
-
If you selected Use existing base plan, specify the plan name and select a base 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.
You can use the Metallic Recovery Reserve cool storage class 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, full backup database frequency, or to add exceptions, move the Advanced toggle key to the right, and do the following:
-
From the time zone list, select the time zone according to which the backups must run.
-
If you select incremental or differential backup type for all agents or databases, to modify the full backup frequency of the database, specify a value for Run full backup on databases every option.
-
To add exceptions when the backups must not run, click Exceptions, and then add exceptions for any day of a month or week or schedule an exception for any week of the month.
Exceptions repeat every week or month according to the selected exception.
-
To modify the transaction log frequency, or enable disk cache for log backups, in the Run transaction log for databases field, click Edit .
-
For Transaction log, specify how often to run log backups.
-
To automatically back up the database logs to the MediaAgent cache, move the Advance toggle button to the right and do the following:
-
Move the Use disk cache for log backups toggle key to the right.
-
For Commit every, enter how often to commit the logs to the CommServe computer.
Disk caching of database logs applies to the following databases: Informix, Microsoft SQL Server on Windows, Oracle, Oracle RAC, and SAP HANA
Note
The database schedules are available only if the server plan is applicable to database solution and only one transaction log schedule can be added to that specific plan.
-
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
|
- Leave the Allow plan to be overridden check box cleared.
|
-
On the Add a Big Data application 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.
Note
If the master node for an instance is not available due to a network failure or any other reason and a backup is in progress, then the Commvault software picks another node as master node from the replica set for backup operation. This is applicable only for the replica set environments.
-
In the Binary path box, enter the path to the folder that contains the mongod or mongos executable file.
The Commvault software uses mongo/mongosh, mongod, mongodump, and mongorestore for backup and restore operations. Keep the binaries in bin path and verify that the bin path is same across all the nodes in the cluster.
-
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.
-
From Plan list, select the server backup plan to use for the cluster.
-
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.
The account must have one of the following on the admin database:
-
The root role. This is a superuser role.
-
The backup, restore, and clusterAdmin roles. If you do not want to assign a superuser role to the database user, use these roles.
-
Click Save.