Update a MongoDB Cluster

You can update an existing MongoDB cluster on any of the following editions: Playground, Business, or Enterprise.

Edit a Cluster

Note: All the available MongoDB clusters that are part of your contract are listed under the MongoDB Clusters section on the Databases page.

1. Log in to the DCD with your username and password.

2. Go to Menu > Databases > MongoDB.

Select MongoDB from the drop-down menu

1. In the MongoDB cluster overview window, select the cluster that needs modification using one of these options:

   • Click Edit in the OPTIONS column.

   

   Edit a cluster

   a. Alternatively, you can select a cluster from the list by clicking on its name or by selecting Details in the OPTIONS column.

   

   Alternative edit option

   b. Select Edit in the Cluster details tab.

Alternative edit option

1. The Edit window displays the details of the cluster. You can edit the following:

Playground

• Properties: Enter a new name in Cluster Name to edit the name of the MongoDB cluster.

• Edition: You can upgrade the existing cluster edition from Playground to either Business or Enterprise.

• Cluster configuration: The Database type is set to Replica set. Depending on the edition, you would see the allowed number of Instances to choose from. For example, if the existing cluster is updated to Business edition and a MongoDB Business S template is selected, then, you could choose to edit the number of instances to either one or three instances.

• Network configuration: You can add additional private IP addresses from the IP/Subnet drop-down list when you increase the number of Instances to upgrade the existing Playground edition to an another MongoDB edition.

• Maintenance period (optional): * Day: From the drop-down list, modify the preferred day on which the maintenance of the cluster must take place. * Start Time (UTC): Choose the appropriate time from the clock displayed.

Note: — Database snapshots are not available for clusters in the Playground edition. For more information, see Features. — Delete an existing cluster by using the delete option.

Edit Playground edition

Business

• Properties: Enter a new name in Cluster Name to edit the name of the MongoDB cluster.

• Edition: You can upgrade the existing cluster edition from Business to another version of Business or Enterprise.

• Cluster configuration: The Database type is set to Replica set. Depending on the edition, you would see the allowed number of Instances to choose from. For example, if the existing cluster is updated to Business edition and a MongoDB Business L template is selected, then, you could choose to edit the instances to either one or three instances.

• Network configuration: You can add additional private IP addresses from the IP/Subnet drop-down list when you increase the number of Instances to upgrade the existing Business edition to an another MongoDB edition.

• Maintenance period (optional):

  • Day: From the drop-down list, modify the preferred day on which the maintenance of the cluster must take place.

  • Start Time (UTC): Choose the appropriate time from the clock displayed.

Note: — Database snapshots are available for clusters in the Business edition. In the Backups tab, restore the data in the cluster from the selected snapshot. For more information, see Restore a MongoDB Cluster via the DCD. — Delete an existing cluster by using the delete option. When you delete a cluster, all of its backup data is also immediately deleted.

Edit Business edition

Enterprise

• Properties: Enter a new name in Cluster Name to edit the name of the MongoDB cluster.

• Edition: You can only view the existing cluster edition set as Enterprise.

Note: At this time, it is not possible to downgrade the Enterprise edition to any other edition.

• Cluster configuration:

  • The Database type can be Sharded cluster or Replica set based on the value selected during the cluster creation.

  • Update the Amount of shards as required.

  • Select from three, five, or seven Instances from the drop-down list to host a logical database manager environment to catalog your databases.

Note: At this time, downscaling of instances is not supported.

• Select a value from the drop-down list to update the offsite Backup Location to allow backup data to be stored in a location other than the deployed database cluster. Available backup locations: Germany/Frankfurt am Main (de), Spaine/Logroño (eu-south-2), Germany/Berlin (eu-central-2), and Germany/Berlin (eu-central-3).

• Toggle on or off the Enable BI Connector. It is advised to enable the MongoDB Connector for Business Intelligence (BI) to query a MongoDB database by using SQL commands to aid in the data analysis.

• Resources:

  • Number of CPUs (per instance): Update the number of CPU cores between 1 and 31 cores using the slider or choose from the available shortcut values.

  • RAM Size (per instance): Updating RAM size for up to 576 GB is possible. Select the RAM size using the slider or choose from the available shortcut values.

  • Storage Size: The existing storage values can be reset to a maximum of 4 TB. For optimal performance, a storage size of at least 100 GB is recommended.

• Network configuration: You can add additional private IP addresses from the IP/Subnet drop-down list when you increase the number of Instances.

• Maintenance period (optional):

  • Day: From the drop-down list, modify the preferred day on which the maintenance of the cluster must take place.

  • Start Time (UTC): Choose the appropriate time from the clock displayed.

Note: — Database snapshots are available for clusters in the Enterprise edition. In the Backups tab, restore the data in the cluster from the selected snapshot. For more information, see Restore a MongoDB Cluster via the DCD. — Delete an existing cluster by using the delete option. When you delete a cluster, all of its backup data is also immediately deleted.

Edit Enterprise edition

Note: The Estimated price will be displayed based on the input. The estimated cost is exclusive, where certain variables like traffic and backup are not considered.

5. Click Save to provision your changes.

Result: The existing MongoDB cluster is updated with the newly defined values.