To delete a MongoDB cluster, follow these steps:
Log in to the DCD with your username and password.
Go to Menu > Databases > MongoDB. A list of all MongoDB clusters is displayed.
Click in the OPTIONS column and select Delete.
Alternatively, you can also delete a cluster using the following options:
Select a MongoDB cluster by clicking on its name and in the Cluster details tab, select Delete.
Select a MongoDB cluster by clicking on its name and in the Cluster details tab, select Edit. In the Edit window, select Delete.
Select Delete in the dialog box to confirm deletion.
Result: The STATE of the respective MongoDB cluster is set to DESTROYING before it is completely deleted.
You can add a MongoDB cluster on any of the following editions: Playground, Business, or Enterprise.
Prerequisites: Before setting up a database, make sure you are working within a provisioned VDC that contains at least one virtual machine (VM) from which to access the database. The VM you create is counted against the quota allocated in your contract. For more information on databases quota, see Resource Allocation.
Note: Database Manager is available for contract administrators, owners, and users with Access and manage DBaaS privileges only. You can set the privilege via the DCD group privileges.
To create a MongoDB cluster, follow these steps:
1. In the DCD, click Menu > Databases > MongoDB.
Info: The Resource allocation section displays the resources allotted to your contract and the number of used and unused resources if you have already created MongoDB clusters.
2. In the MongoDB cluster overview window, click Create cluster to create a new MongoDB cluster.
3. Specify the following in the Properties section:
Provide an appropriate Cluster Name.
From the drop-down list, choose a Location where your data for the database cluster can be stored. You can select an available data center within the cluster's data directory to create your cluster.
Select the appropriate MongoDB Version. The IONOS Database Manager supports MongoDB versions 5.0 and 6.0.
4. Choose an Edition.
In the Playground edition, the following standard resources are available:
RAM Size (GB): 2.
vCPU: 1.
Storage Size: 50 GB.
Note: You can create one playground instance for free and test MongoDB. For every additional instance that you create apart from the first instance, the charges are applicable accordingly.
In the Business edition, select a relevant Template to based on the resources required for creating your MongoDB cluster. The resources vary for each of the predefined templates based on the RAM Size (GB), vCPU, and Storage Size. Select a template from the drop-down list that suits your needs.
Note: Depending on the resource limit allocation as per your contract, some of the templates may not be available for selection.
In the Enterprise edition, choose the following resources for creating each node of your MongoDB cluster. The total billed resources will be these values multiplied by the number of instances and the number of shards (if applicable).
Upon selecting Enterprise edition, you can choose from the following in the Resources section:
Number of CPUs (per instance): You can choose between 1 and 31 CPU cores using the slider or choose from the available shortcut values.
RAM Size (per instance): Values of up to 230 GB RAM sizes are possible. Select the RAM size using the slider or choose from the available shortcut values.
Storage Type: The SSD Premium, SSD Standard, or HDD storage options are available.
Storage Size: Set the storage size value to at least 100 GB in case of SSD Standard and Premium storage types for optimal performance of the database cluster. You can configure the storage size to a maximum of 4 TB.
5. Configure your cluster in the Cluster configuration section.
Database type: It is set to Replica Set, by default. This database type maintains replicas of data sets and offers redundancy and high data availability.
Note: The Sharded Cluster database type is not available for selection in the Playground edition.
Instances: By default, one instance is offered for free in this edition to host a logical database manager environment to catalog your databases.
Database type: It is set to Replica Set, by default. This database type maintains replicas of data sets and offers redundancy and high data availability.
Note: The Sharded Cluster database type is not available for selection in the Business edition.
Instances: Select a value from the drop-down list to host a logical database manager environment to catalog your databases. By default, one instance and three instances are possible in the Business edition.
Database type: Select the Database type from the following:
Replica Set: Maintains replicas of datasets; offers redundancy and high availability of data.
Sharded Cluster: Maintains collection of datasets that are distributed across many shards (servers) and hence offers horizontal scalability.
Note: For sharded clusters, an additional three config server instances are created with sizing of two cores, 4 GB of memory, and 40 GB of storage each. These instances are excluded from the billed resources.
Amount of shards: Define the Amount of shards between two to a maximum of thirty-two shards. This is applicable to Sharded Cluster only.
Instances: Select the number of instances to host a logical database manager environment to catalog your databases. By default, three instances are possible in the Enterprise edition.
Backup Location: Select a backup location that is explicitly the location of your backup (region). You can have off-site backups by using a region that is not included in your database region.
BI Connector enabled: Toggle to enable the MongoDB Connector for Business Intelligence (BI) to query a MongoDB database by using SQL commands to aid in the data analysis. If you do not want to use BI Connector, you can toggle off this setting.
6. In the Network configuration section, set up the following:
Datacenter: Select a data center from the available drop-down list.
Datacenter LAN: Select a LAN for the chosen data center.
IP/Subnet: Enter the private IP or subnet address in the correct format by using the available Private IPs. For Business and Enterprise editions, specify one private IP/Subnet address detail for every instance based on the chosen number of Instances.
Note: To know your private IP address/Subnet, you need to:
Create a single server connected to an empty private LAN and check the IP assigned to that NIC in that LAN. The DHCP in that LAN is always using a /24 subnet, so you have to reuse the first 3 octets to reach your database.
To prevent a collision with the DHCP IP range, it is recommended to use IP addresses ending between x.x.x.3/24 and x.x.x.10/24 (which are never assigned by DHCP).
If you have disabled DHCP on your private LAN, then you need to discover the IP address on your own.
7. In the Maintenance period (optional) section, set the following:
Day: From the drop-down list, choose the preferred day on which the maintenance of the cluster must take place.
Start Time (UTC): Set the time (in UTC) for the maintenance of the MongoDB cluster. Use the pre-defined format (hh:mm:ss) or you can use the clock. The maintenance occurs in a 4-hour-long window.
8. Click Save to provision the creation of the MongoDB cluster.
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.
Result: The MongoDB cluster with the chosen edition is created.
After successfully configuring your MongoDB clusters, you can modify specific details, restore backups, or delete a specific cluster if it is no longer required.
To modify the values, follow these steps:
Log in to DCD with your username and password.
Go to Menu > Databases > MongoDB. A list of all MongoDB clusters is displayed.
Result: You can view the total number of resources allocated and the list of all clusters in addition to the following details: — NAME: Displays the name of the cluster. Select the name of the cluster to view its details. — STATE: Displays the state of the respective cluster: — BUSY: When the cluster is being created or updated. For example, after creation, modifying its details or after restoration. — AVAILABLE: When the cluster is available and healthy. — DESTROYING: When the cluster is being deleted. — FAILED: An error occurred. — LOCATION: Displays the location where the cluster is located. — INSTANCES: Displays the number of instances. — VERSION: The version selected during cluster creation. — EDITION: The edition selected during cluster creation. — OPTIONS: Select to perform the following: — Details: Select to view the details of the respective cluster. — Edit: Select to edit the respective cluster. — Delete: Select to delete the corresponding cluster. In the dialog box that appears, select Delete to confirm deletion. For more information, see Delete a MongoDB Cluster.
You can view the details of a specific cluster. To do so, follow these steps:
Log in to DCD with your username and password.
Go to Menu > Databases > MongoDB. A list of all MongoDB clusters is displayed.
Select a cluster from the list by clicking on its name. Alternatively, click Details in the OPTIONS column.
Result: You can copy the cluster's Cluster UUID and Connection URI from the Cluster details tab. Additionally, you can also do the following: — Edit a MongoDB Cluster — Delete a MongoDB cluster — Restore a MongoDB Cluster via the DCD — Define roles
To assign users and define roles, follow these steps:
In the User Management tab, click Add user to create and manage user roles for the MongoDB cluster.
Enter the username, password, and define roles for the database.
Click Add.
Result: The user is successfully created.
You an also edit the user's password and roles or delete it. For more information, see User Management via the API.
You can restore a MongoDB cluster by using a snapshot reference. A cluster can have multiple snapshots for backup and are retained for seven days; hence, cluster recovery is possible for up to a week from the current date. For more information, see Backup and Recovery.
Note: MongoDB database cluster backups are available only in the following editions: Business and Enterprise. Backups are disabled for the Playground edition.
Note:
All the available MongoDB clusters that are part of your contract are listed on the MongoDB cluster overview page.
You cannot revert the database restore operation once confirmed. For more information, see Backup and Recovery.
You cannot initiate a new database restore of a cluster from a snapshot when a restore is already in progress.
1. In the DCD, click Menu > Databases > MongoDB.
2. In the MongoDB cluster overview window, select the database cluster that is added for the Business edition by selecting a cluster from the list by clicking on its name or by selecting Details in the OPTIONS column.
Select Backups.
In the Backups tab, choose the snapshot you want to use for restoring the database cluster from the list of available snapshots. Each snapshot displays the following details:
Version: The MongoDB version number of the database cluster.
Created: A date and time when the database snapshot was created. For more information on instances when the snapshots are added, see Backups.
Size: Snapshot database cluster size (in MB).
5. Click Restore on the snapshot selected for restoring the data in the cluster.
Result: The database restore from the selected snapshot is successfully initiated.
1. In the DCD, click Menu > Databases > MongoDB.
2. In the MongoDB cluster overview window, select the database cluster that is added for the Enterprise edition by selecting a cluster from the list by clicking on its name or by selecting Details in the OPTIONS column.
3. In the Backups tab, choose from the following two options to restore a database cluster:
a. Point-in-time recovery: Select Point-in-time recovery to restore the database cluster from a specific point-in-time of the database backup.
Choose the backup time from the calendar displayed and click Save. The number of hours in the past from which the backup is possible is between 1 and 24 hours. The default value is 24 hours.
You will receive a confirmation message that the backup is being restored.
b. Restore: Choose the snapshot you want to use for restoring the database cluster from the list of available snapshots.
Click Restore.
Confirm the database restore from the snapshot by clicking Restore.
Note: Each snapshot displays the following details:
Version: The MongoDB version number of the database cluster.
Created: A date and time when the database snapshot was created. For more information on instances when the snapshots are added, see Backups.
Size: Snapshot database cluster size (in MB).
Result: The database restore from the selected snapshot is successfully initiated.
You can update an existing MongoDB cluster on any of the following editions: Playground, Business, or Enterprise.
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.
In the MongoDB cluster overview window, select the cluster that needs modification using one of these options:
Click Edit in the OPTIONS column.
a. Alternatively, you can select a cluster from the list by clicking on its name or by selecting Details in the OPTIONS column.
b. Select Edit in the Cluster details tab.
The Edit window displays the details of the cluster. You can edit the following:
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.
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.
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.
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.
From the DCD, you can create and manage MongoDB Clusters. In the DCD, go to Menu > Databases > MongoDB. You can view the resource allocation details for your user account that shows details of CPU Cores, RAM (in GB), and Storage data. In the MongoDB, you can create database clusters in the following editions: Playground, Business, and Enterprise. Each of these editions offer varied resource allocation templates and advanced features that you could choose from that suits your enterprise needs. For information on creating a MongoDB cluster via the DCD, see .
Note: The Database Manager is available for contract administrators, owners, and users with Access and manage DBaaS privileges only. You can set the privilege via the DCD group privileges. For more information, see .