E2E’s DBaaS provides a selection of node types optimized to fit different relational database use cases consisting of different database engines. Node Cluster configuration comprises varying combinations of CPU, memory, storage and gives you the flexibility to choose the appropriate mix of resources for your database.
E2E’s Relational DBaaS Service makes it easier for us to set up and operate Relational Databases in the cloud, providing us with Cost-efficient service and automating time-consuming administrator tasks such as Provisioning, Patching, and Setups.
Database makes it easier to deploy the nodes, Using the Myaccount portal with just a click away from providing necessary details you will be able to provision the node. There will not be any administrative task of installing or maintaining the database software.
Scalability and Failover¶
Database with only a few clicks helps you setup a slave which allows you to launch one or more Read Replicas to offload read traffic from your primary database nodes.
Database Supports the most demanding application. You can choose between different cluster configurations based on your usage which are optimized for high performance.
Database is highly secure restricting access to the external environment with Firewall. It Provides the necessary option for you to optimize the setting so that only a known and existing host will be able to connect with your database.
Getting Started with Database¶
E2E’s DBaaS is a service that makes it easier to set up, operate, and scale a relational database in the cloud. MyAccount Portal provides you a web-based interface for accessing and managing all your Database resources.
How to Create a Database Cluster in Myaccount Portal¶
This section will show you how to create a database cluster from the Myaccount portal. The tutorial that is mentioned below are the basic steps of getting started with the Relational Database cluster in Myaccount Portal
Login into MyAccount Portal¶
Please Login to Myaccount Portal using your credentials set up at the time of creating and activating the E2E Networks ‘My Account’.
On the top right section of the manage database dashboard, You need to click on the “Create Database” Button which will prompt you to the cluster page where you will be selecting the configuration and entering the details of your database
Database Configuration and Setting¶
After creating the database, You need to select the required configuration and setting for your database which are mentioned below.
Database Engine - Database has various database engines available. You need to select the required database engine which you prefer, Below are the list of database engine which we currently support
Mariadb - 10.4
Mariadb - 10.6
Mariadb - 10.11
Cluster Configuration - Node Cluster configuration comprises varying combinations of CPU, memory, storage and gives you the flexibility to choose the appropriate mix of resources for your database.
Cluster Name - You need to Provide the Cluster name which you want for your cluster. This name will be visible on the Database page
Database Setting - We need to update the database name, user and provide a secure password for our database. You will be using these credentials to log in to the database server.
With strong password authentication, your database controls and authenticates user accounts. If a DB engine has strong password management features, they can enhance security.
Once you have entered the required details, click on create a database. Your database might take a few minutes to Launch. The database node will be in a setting up state until its ready to use and when the status will change to running.
Connecting to your database Cluster¶
After E2E’s database (DBS) provision your nodes, you can use any standard SQL client application to connect to a database on the DB instance. In this example, you connect to a database on a Maria DB instance using the MySQL command-line tool.
To connect to your database node using MySQL command line¶
Once your database has been provisioned and its running status, You can get the database connectivity information on the dashboard.
Enter the following command at a command prompt on your local or client desktop to connect to a Mariadb or mysql database.
mysql -h <host> -P 3306 -u <’username’> -p <’password’>
After you enter the password for the user, you should see output similar to the following.
Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 272 Server version: 5.5.5-10.0.17-MariaDB-log MariaDB Server Copyright (c) 2000, 2015, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Type 'help;' or '\h' for help. Type '\c' to clear the current input statement. mysql >
Managing Your Database Node¶
In this section, you can find instructions and details to Manage and Maintain your database.
To manage your Database Instance, Click on … (Action Button) and Select Manage option for your database Node
Stopping your Database¶
If you are using your DB Node for temporary testing or for any other daily development activity and want to test out your database by stopping it which will close all the connections in your database. You can perform this action by clicking on Action and selecting the Stop button.
You can resume your database which was stopped earlier by clicking on the Start button in the Action menu. Resuming your database will retain the same IP and credentials for your database and there will not be any changes at configuration level.
Backup your Database¶
You can take your database backup on our Object Storage. You can perform this action by clicking on Action and selecting the Enable Backup button.
After click on Enable Backup button, it will ask for Bucket details along with Access key & Secret Key to configure the DB Backup. The DBaaS Binlogs will be copied over to the E2E storage bucket that you specify. You can enable/disable binlogs backup at any time.
There is no additional charge for enabling binlogs backup but you will be charged for the EOS bucket storage it consumes.
Restart your Database¶
If you are testing out your DB nodes, restarting your database to reset connections or for any troubleshooting purpose, You can restart your database by clicking on the Restart button on the action menu.
Upgrade your database¶
The DBaaS upgrade feature enables customers to easily upgrade their DBaaS plan based on their specific usage requirements. For upgrading you database you have to click on Upgrade button under Action button.
After clicking on Upgrade the Upgrade plan will be show and you have to click on Upgrade button with the selected plan after that the confirmation popup will be open and you have to click on Upgrade button.
After this the Upgrading process will be start and the database status will be in upgrading status.
Please ensure that your database is stopped when performing the upgrade action.
Delete your Database¶
To delete your database, click on Delete option. Please note that once you have deleted your database you will not be able to recover your database.
Database and Connectivity Details¶
In the Manage Database page, You can find the details of your database configurations deatils in Connection Details section for created Database Instance.
To check the Connectivity Details of your database, Click on Connectivity details tab.
Here you can have two options for your database connectivity.
Use Different Read/Write IP¶
This option will have different read and write port (3306 and 3307) binded for your database connection.
Use Same Read/Write Port & IP¶
This option will have same port binded for both read and write operation for your database connection.
To check the Database information, Click on DBaaS Details tab below to get the host details like Database Engine, DBaaS Configuration, Plan information and other DBaaS related details.
Allow Trusted Host IP’s:- This setting control the access of Allowed Host IP that can be able to connect your Database node from your trusted ISP IP. If No trusted host selected. Anyone can connect using credentials.
The snapshot feature is valuable for data protection, disaster recovery, and testing scenarios, providing users with the ability to easily revert to a previous database state or create duplicates for various purposes.and we use “restore snapshot” to quickly recover lost or corrupted data, recover from system failures, and revert to a stable state in case of issues during testing or updates. It’s like a fast-forward button to a previously known good state of a system.
Take Manual Snapshot of Database¶
When the user wants to take a snapshot immediately and manually, they can click on the take snapshot button.
After clicking on the take snapshot button. A popup menu will appear, prompting you to enter the snapshot name. Provide the snapshot name and click on ‘create snapshot’ to initiate the snapshot creation.
To restore the snapshot from the saved file, click the action button, select the ‘restore’ option, and proceed with the snapshot restoration.
When a user wants to deletes the snapshot, they can remove from the snapshot list.
To delete a snapshot, click the action button, select the delete option, and confirm the deletion of the snapshot.
scheduled snapshot is a proactive approach to data management and system backup, providing regular and automated snapshots to enhance data protection, disaster recovery, and overall system reliability. When a user wants to schedules a time duration, a snapshot will be created every day within the specified timeframe.
To schedule a snapshot of your database, click on the ‘Scheduled snapshot’ link or the provided ‘click here’ option. Choose the snapshot creation interval and select the desired time duration for taking snapshots.
Edit Scheduled Snapshot¶
When a user wants to edit the scheduled snapshot interval, they can modify the time duration for the scheduled snapshot changes.
To edit the scheduled snapshot of your database, click on the ‘Edit Scheduled Snapshot’ button. Select the desired options, and save the changes to the scheduled snapshot.
After editing the scheduled snapshot for your database, you can disable the scheduled snapshot.
Configure Snapshot Lifecycle¶
To configure the snapshot lifecycle of your database, click on ‘Configure Snapshot Lifecycle’ and select the option to configure the snapshot lifecycle. When a user selects the snapshot lifecycle, the snapshot is automatically deleted after the specified time duration.
Snapshot will be deleted automatically after the selected interval.
Edit configure Snapshot lifecycle¶
To edit the Configure scheduled snapshot of your database, click on the ‘Edit Configure Scheduled Snapshot’ button. Select the desired options, and save the changes to the scheduled snapshot. When a user edits the snapshot lifecycle, the time duration for the snapshot Lifecycle changes.
After editing the configure snapshot lifecycle for your database, you can disable the configure snapshot lifecycle.
Read Replica of the Database¶
The read replica operates as a DB instance that allows only read-only connections; applications can connect to a read replica just as they would to any DB instance.
The size of read-only nodes can not be set individually and are tied to the size of the DBaaS primary node. Due to this read-only nodes must be at least as big as your DBaaS’s primary node and will be automatically scaled to match.
After you launch your database node, you can view the monitoring graphs for your node on the Monitoring tab. Each graph is based on one of the different metrics. This information is collected from your node and processes raw data into readable graphs. Monitoring is an important part of maintaining the reliability, availability, and performance of your database.
Slow Log queries¶
The slow query log feature in MySQL allows you to log all queries that take longer than a given threshold of execution time. The queries in the slow query log are good candidates to start optimizing and eliminating the bottlenecks.
To configure slow log queries, Click on configure view and select the appropriate time duration to log the queries that will be displayed on the dashboard.
You can set up new alerts by defining trigger parameters as per your use case for your database. The alerting system works by sending automatic response notifications to your defined email list.