From the DCD, you can create and manage MongoDB Clusters. In the DCD > Databases, 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 Set up a MongoDB Cluster.
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 Assigning Privileges to Groups.
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.
1. In the Data Center Designer, click the Databases menu.
2. In the Databases page, click + Add in the MongoDB Clusters section.
3. Provide an appropriate Display Name.
4. 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.
5. Choose the Edition type as Playground. In this edition, you can create one playground instance for free and test MongoDB.
Note: For every additional instance that you create apart from the first instance, the charges are applicable accordingly.
6. Select the Template to use the resources for creating your MongoDB cluster. In the Playground edition, the following standard resources are available:
RAM Size (GB): 2.
vCPU: 1.
Storage Size: 50 GB.
7. Select the Database Type as the Replica Set. 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.
8. Select the Instances to host a logical database manager environment to catalog your databases. By default, one instance is offered for free in this 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.
9. In the Cluster to Datacenter Connection section, set up the following:
Select a Data Center: Select a data center from the available list. Use the search option to enter a data center that you want to select.
LAN in the selected Datacenter: Select a LAN for the chosen data center.
10. In the Private IP/Subnet, perform the following actions:
Private IP/Subnet: Enter the private IP or subnet address in the correct format by using the available Private IPs.
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 IP blocks 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.
Click Add to save the private IP/Subnet address details.
Click Add Connection to connect the cluster to the data center.
11. Select the appropriate MongoDB Version. The IONOS Database Manager supports 5.0 and 6.0 MongoDB versions.
12. In the Maintenance Window, set the following:
Maintenance time: 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, adjust the time accordingly.
Maintenance day: From the dropdown menu, choose the preferred day on which the maintenance of the cluster must take place.
13. Click Save to provision the creation of the MongoDB cluster.
Result: The MongoDB cluster for the defined values is created in the Playground edition.
1. In the Data Center Designer, click the Databases menu.
2. In the Databases page, click + Add in the MongoDB Clusters section.
3. Provide an appropriate Display Name.
4. 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.
5. Choose the Edition type as Business.
6. Select the Template to use the resources needed for creating your MongoDB cluster. In the Business edition, the resources varying from MongoDB Business XS to MongoDB Business 4XL_S are made available. Each template differs based on the RAM Size (GB), vCPU, and Storage Size.
Note: Depending on the resource limit allocation as per your contract, some of the templates may not be available for selection.
7. Select the Database Type as the Replica Set. This database type maintains replicas of data sets and offers redundancy and high availability of data.
Note: The Sharded Cluster database type is not available for selection in the Business edition.
8. Choose the Instances to host a logical database manager environment to catalog your databases. By default, one instance and three instances are possible in the Business 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.
9. In the Cluster to Datacenter Connection section, set up the following:
Select a Data Center: Select a data center from the available list. Use the search option to enter a data center that you want to select.
LAN in the selected Datacenter: Select a LAN for your data center.
10. In the Private IP/Subnet, perform the following actions:
Private IP/Subnet: Enter the private IP or subnet address in the correct format by using the available Private IPs. Depending on the number of instances selected in step 8, you need to enter one private IP/Subnet address detail for every instance.
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 IP blocks 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.
Click Add to save the private IP/Subnet address details.
Click Add Connection to connect the cluster to the data center.
11. Select the appropriate MongoDB Version. The IONOS Database Manager supports 5.0 and 6.0 MongoDB versions.
12. In the Maintenance Window, set the following:
Maintenance time: 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, adjust the time accordingly.
Maintenance day: From the dropdown menu, choose the preferred day on which the maintenance of the cluster must take place.
13. Click Save to provision the creation of the MongoDB cluster.
Result: The MongoDB cluster for the defined values is created in the Business edition.
1. In the DCD, click the Databases menu.
2. In the Databases page, click + Add in the MongoDB Clusters section.
3. Provide an appropriate Display Name.
4. 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.
5. Choose the Edition type as Enterprise.
6. 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).
CPU Cores: You can choose between 1 and 31 CPU cores using the slider or choose from the available shortcut values.
RAM Size (GB): 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 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.
7. 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. Define the Amount of Shards between two to a maximum of thirty-two shards.
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.
8. Choose the Instances to host a logical database manager environment to catalog your databases. By default, three instances are possible in the 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.
9. In the Cluster to Datacenter Connection section, set up the following:
Select a Data Center: Select a data center from the available list. Use the search option to enter a data center that you want to select.
LAN in the selected Datacenter: Select a LAN for your data center.
10. In the Private IP/Subnet, perform the following actions:
Private IP/Subnet: Enter the private IP or subnet address in the correct format by using the available Private IPs. Depending on the number of instances selected in step 8, you need to enter one private IP/Subnet address detail for every instance.
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 IP blocks 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.
Click Add to save the private IP/Subnet address details.
Click Add Connection to connect the cluster to the data center.
11. Select the appropriate MongoDB Version. The IONOS Database Manager supports 5.0 and 6.0 MongoDB versions.
12. Choose 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.
13. Toggle on the Enable BI Connector 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.
14. In the Maintenance Window, set the following:
Maintenance time: 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, adjust the time accordingly.
Maintenance day: From the dropdown menu, choose the preferred day on which the maintenance of the cluster must take place.
15. Click Save to provision the creation of the MongoDB cluster.
Result: The MongoDB cluster for the defined values is created in the Enterprise edition.
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.
MongoDB database cluster backups are available only in the following editions: MongoDB Business and MongoDB Enterprise.
Note: Backups are disabled for the Playground edition.
Note: All the available MongoDB clusters that are part of your contract are listed under the MongoDB Clusters section on the Databases page.
1. In the Data Center Designer, click the Databases menu.
2. In the Databases page under the MongoDB Clusters section, click the database cluster that is added for the Business edition.
3. In the Snapshots section, choose the snapshot you want to use for restoring the database cluster from the list of available snapshots.
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).
4. Click Restore on the snapshot selected for restoring the data in the cluster.
5. Confirm the database restore from the snapshot by entering your password and clicking Yes, I'm sure.
Result: The database restore from the selected snapshot is successfully initiated.
Note:
The operation of database restore from the snapshot cannot be undone 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 Data Center Designer, click the Databases menu.
2. In the Databases page under the MongoDB Clusters section, click the database cluster that is added for the Enterprise edition.
3. In the Snapshots section, choose from the following two options to restore a database cluster:
1. Restore by time: Restores 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.
Confirm the database restore from the snapshot by entering your password and clicking Yes, I'm sure.
2. 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 entering your password and clicking Yes, I'm sure.
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.
Note:
The operation of database restore from the snapshot cannot be undone 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.
You can update an existing MongoDB cluster on any of the following editions: Playground, Business, or Enterprise.
Prerequisites: Make sure the MongoDB database cluster is added by following the steps in Set up a MongoDB 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. In the Data Center Designer, click the Databases menu.
2. In the Databases page under the MongoDB Clusters section, click the database cluster that is added for the Playground edition.
Note: From this page, you can perform the following actions: Copy connection URI and User Management .
4. In the Edit Form, you can update the following cluster details:
Display Name: Edit the name of the MongoDB cluster.
Edition: You can upgrade the existing cluster edition from Playground to either Business or Enterprise.
Template: Based on the edition selected, choose from the list of templates you want to update the cluster with.
Instances: Depending on the edition and template selected, you would see the allowed number of instances you could 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.
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.
Delete an existing IP address.
Add new Private IP/Subnet List.
6. In the Maintenance Window, you can edit the following details:
Maintenance time: Choose the appropriate time from the clock displayed.
Maintenance day: From the dropdown list, modify the preferred day on which the maintenance of the cluster must take place.
7. Click Save to provision your changes.
Result: The existing MongoDB cluster is updated with the newly defined values. You can review the updated cluster details under the Properties section.
Next steps: In editing a cluster, you can also perform the following actions:
In the User Management section, click Add to create and manage user roles for the MongoDB cluster. For more information, see Roles.
Note: Database snapshots are not available for clusters in the Playground edition. For more information, see Features.
1. In the Data Center Designer, click the Databases menu.
2. In the Databases page under the MongoDB Clusters section, click the database cluster that is added for the Business edition.
4. In the Edit Form, you can update the following cluster details:
Display Name: Edit the name of the MongoDB cluster.
Edition: You can upgrade the existing cluster edition from Business to Enterprise.
Template: Based on the edition selected, choose from the list of templates you want to update the cluster with.
Instances: Depending on the edition and template selected, you would see the allowed number of instances you could 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.
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.
Delete an existing IP address.
Add new Private IP/Subnet List.
6. In the Maintenance Window, you can edit the following details:
Maintenance time: Choose the appropriate time from the clock displayed.
Maintenance day: From the dropdown list, modify the preferred day on which the maintenance of the cluster must take place.
7. Click Save to provision your changes.
Result: The existing MongoDB cluster is updated with the newly defined values. You can review the updated cluster details under the Properties section.
Next steps: In editing a cluster, you can also perform the following actions:
In the User Management section, click Add to create and manage user roles for the MongoDB cluster. For more information, see Roles.
In the Snapshots section, restore the data in the cluster from the selected snapshot. For more information, see Restore a MongoDB Cluster via the DCD.
Note: When you delete a cluster, all of its backup data is also immediately deleted.
1. In the Data Center Designer, click the Databases menu.
2. In the Databases page, click the database cluster that is added for the Enterprise edition.
4. In the Edit Form, you can update the following cluster details:
Display Name: 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 from the Enterprise edition to any other edition.
CPU Cores: Update the number of CPU cores between 1 and 31 cores using the slider or choose from the available shortcut values.
RAM Size (GB): Update RAM size for up to 230 GB is possible. Select the RAM size using the slider or choose from the available shortcut values.
Instances: Choose from three, five, or seven instances to host a logical database manager environment to catalog your databases.
Note: At this time, downscaling of instances is not supported.
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.
Delete an existing IP address.
Add new Private IP/Subnet List.
6. 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.
7. Update the offsite Backup Location to allow backup data to be stored in a location other than the deployed database cluster. Available backup locations: de, eu-south-2, eu-central-2.
8. In the Maintenance Window, you can edit the following details:
Maintenance time: Choose the appropriate time from the clock displayed.
Maintenance day: From the dropdown list, modify the preferred day on which the maintenance of the cluster must take place.
9. Click Save to provision your changes.
Result: The existing MongoDB cluster is updated with the newly defined values. You can review the updated cluster details under the Properties section.
Next steps: In editing a cluster, you can also perform the following actions:
In the User Management section, click Add to create and manage user roles for the MongoDB cluster. For more information, see Roles.
In the Snapshots section, restore the data in the cluster from the selected snapshot. For more information, see Restore a MongoDB Cluster via the DCD.
Note: When you delete a cluster, all of its backup data is also immediately deleted.
3. Click edit to modify the cluster details for the selected database cluster.
5. In the Cluster to Datacenter Connection section, click edit to perform the following actions:
Delete an existing cluster by using the delete option .
Note: From this page, you can perform the following actions: Copy connection URI and User Management .
3. Click edit for the selected database cluster to modify the cluster details.
5. In the Cluster to Datacenter Connection section, click edit to perform the following actions:
Delete an existing cluster by using the delete option .
Note: From this page, you can perform the following actions: Copy connection URI and User Management .
3. Click edit for the selected database cluster to modify the cluster details.
5. In the Cluster to Datacenter Connection section, click edit to perform the following actions:
Delete an existing cluster by using the delete option .
