Databases
We currently support cluster mode for MySQL & KeyDB (Redis compatible). We are working hard on adding cluster mode support for more databases.
- DB Migration service
- MySQL Database Migration to Elestio
- PostgreSQL Database Migration to Elestio
- MariaDB Database Migration to Elestio
- ColumnStore Database Migration to Elestio
- Redis Database Migration to Elestio
- KeyDB Database Migration to Elestio
- Valkey Database Migration to Elestio
- MongoDB Database Migration to Elestio
- TimescaleDB Database Migration to Elestio
- Hydra Database Migration to Elestio
- DB Clusters
DB Migration service
MySQL Database Migration to Elestio
Elestio provides a robust and user-friendly platform for managing your database migrations seamlessly. Whether you are migrating from an on-premises MySQL database or from another cloud provider, Elestio's migration tool simplifies the process. By following a few straightforward steps, you can securely and efficiently move your MySQL databases to Elestio, ensuring minimal downtime and disruption to your operations.
This guide will walk you through the process of migrating your MySQL database from an external source to Elestio. We will cover everything from configuring your migration settings, validating the connection to your source database, and finally starting the migration process while monitoring its progress.
Step 1 - Configure
- Go to the overview of your MySQL service on Elestio.
- Click on the Migrate Database button.
- A modal window will open, ensure that your target service has enough disk space to accommodate your database
- Click on Get started button.
Step 2 - Validation
- You need to provide the connection details to establish a connection to your source database, enter the required details:
- Hostname
- Port
- Username
- Password
- Click on Run Check to validate the connection.
Step 3 - Migration
- If all checks pass with no errors, you can trigger the migration by selecting Start migration.
- Once the migration starts, you can monitor the progress through the migration logs displayed in real-time.
PostgreSQL Database Migration to Elestio
Elestio provides a robust and user-friendly platform for managing your database migrations seamlessly. Whether you are migrating from an on-premises PostgreSQL database or from another cloud provider, Elestio's migration tool simplifies the process. By following a few straightforward steps, you can securely and efficiently move your PostgreSQL databases to Elestio, ensuring minimal downtime and disruption to your operations.
This guide will walk you through the process of migrating your PostgreSQL database from an external source to Elestio. We will cover everything from configuring your migration settings, validating the connection to your source database, and finally starting the migration process while monitoring its progress.
Step 1 - Configure
- Go to the overview of your PostgreSQL service on Elestio.
- Click on the Migrate Database button.
- A modal window will open, ensure that your target service has enough disk space to accommodate your database
- Click on Get started button.
Step 2 - Validation
- You need to provide the connection details to establish a connection to your source database, enter the required details:
- Hostname
- Port
- Database Name
- Username
- Password
- Click on Run Check to validate the connection.
Step 3 - Migration
- If all checks pass with no errors, you can trigger the migration by selecting Start migration.
- Once the migration starts, you can monitor the progress through the migration logs displayed in real-time.
MariaDB Database Migration to Elestio
Elestio provides a robust and user-friendly platform for managing your database migrations seamlessly. Whether you are migrating from an on-premises MariaDB database or from another cloud provider, Elestio's migration tool simplifies the process. By following a few straightforward steps, you can securely and efficiently move your MariaDB databases to Elestio, ensuring minimal downtime and disruption to your operations.
This guide will walk you through the process of migrating your MariaDB database from an external source to Elestio. We will cover everything from configuring your migration settings, validating the connection to your source database, and finally starting the migration process while monitoring its progress.
Step 1 - Configure
- Go to the overview of your MariaDB service on Elestio.
- Click on the Migrate Database button.
- A modal window will open, ensure that your target service has enough disk space to accommodate your database
- Click on Get started button.
Step 2 - Validation
- You need to provide the connection details to establish a connection to your source database, enter the required details:
- Hostname
- Port
- Username
- Password
- Click on Run Check to validate the connection.
Step 3 - Migration
- If all checks pass with no errors, you can trigger the migration by selecting Start migration.
- Once the migration starts, you can monitor the progress through the migration logs displayed in real-time.
ColumnStore Database Migration to Elestio
Elestio provides a robust and user-friendly platform for managing your database migrations seamlessly. Whether you are migrating from an on-premises ColumnStore database or from another cloud provider, Elestio's migration tool simplifies the process. By following a few straightforward steps, you can securely and efficiently move your ColumnStore databases to Elestio, ensuring minimal downtime and disruption to your operations.
This guide will walk you through the process of migrating your ColumnStore database from an external source to Elestio. We will cover everything from configuring your migration settings, validating the connection to your source database, and finally starting the migration process while monitoring its progress.
Step 1 - Configure
- Go to the overview of your ColumnStore service on Elestio.
- Click on the Migrate Database button.
- A modal window will open, ensure that your target service has enough disk space to accommodate your database
- Click on Get started button.
Step 2 - Validation
- You need to provide the connection details to establish a connection to your source database, enter the required details:
- Hostname
- Port
- Database name
- Username
- Password
- Click on Run Check to validate the connection.
Step 3 - Migration
- If all checks pass with no errors, you can trigger the migration by selecting Start migration.
- Once the migration starts, you can monitor the progress through the migration logs displayed in real-time.
Redis Database Migration to Elestio
Elestio provides a robust and user-friendly platform for managing your database migrations seamlessly. Whether you are migrating from an on-premises Redis database or from another cloud provider, Elestio's migration tool simplifies the process. By following a few straightforward steps, you can securely and efficiently move your Redis databases to Elestio, ensuring minimal downtime and disruption to your operations.
This guide will walk you through the process of migrating your Redis database from an external source to Elestio. We will cover everything from configuring your migration settings, validating the connection to your source database, and finally starting the migration process while monitoring its progress.
Step 1 - Configure
- Go to the overview of your Redis service on Elestio.
- Click on the Migrate Database button.
- A modal window will open, ensure that your target service has enough disk space to accommodate your database
- Click on Get started button.
Step 2 - Validation
- You need to provide the connection details to establish a connection to your source database, enter the required details:
- Hostname
- Port
- Username
- Password
- Click on Run Check to validate the connection.
Step 3 - Migration
- If all checks pass with no errors, you can trigger the migration by selecting Start migration.
- Once the migration starts, you can monitor the progress through the migration logs displayed in real-time.
KeyDB Database Migration to Elestio
Elestio provides a robust and user-friendly platform for managing your database migrations seamlessly. Whether you are migrating from an on-premises KeyDB database or from another cloud provider, Elestio's migration tool simplifies the process. By following a few straightforward steps, you can securely and efficiently move your KeyDB databases to Elestio, ensuring minimal downtime and disruption to your operations.
This guide will walk you through the process of migrating your KeyDB database from an external source to Elestio. We will cover everything from configuring your migration settings, validating the connection to your source database, and finally starting the migration process while monitoring its progress.
Step 1 - Configure
- Go to the overview of your KeyDB service on Elestio.
- Click on the Migrate Database button.
- A modal window will open, ensure that your target service has enough disk space to accommodate your database
- Click on Get started button.
Step 2 - Validation
- You need to provide the connection details to establish a connection to your source database, enter the required details:
- Hostname
- Port
- Username
- Password
- Click on Run Check to validate the connection.
Step 3 - Migration
- If all checks pass with no errors, you can trigger the migration by selecting Start migration.
- Once the migration starts, you can monitor the progress through the migration logs displayed in real-time.
Valkey Database Migration to Elestio
Elestio provides a robust and user-friendly platform for managing your database migrations seamlessly. Whether you are migrating from an on-premises Valkey database or from another cloud provider, Elestio's migration tool simplifies the process. By following a few straightforward steps, you can securely and efficiently move your Valkey databases to Elestio, ensuring minimal downtime and disruption to your operations.
This guide will walk you through the process of migrating your Valkey database from an external source to Elestio. We will cover everything from configuring your migration settings, validating the connection to your source database, and finally starting the migration process while monitoring its progress.
Step 1 - Configure
- Go to the overview of your Valkey service on Elestio.
- Click on the Migrate Database button.
- A modal window will open, ensure that your target service has enough disk space to accommodate your database
- Click on Get started button.
Step 2 - Validation
- You need to provide the connection details to establish a connection to your source database, enter the required details:
- Hostname
- Port
- Username
- Password
- Click on Run Check to validate the connection.
Step 3 - Migration
- If all checks pass with no errors, you can trigger the migration by selecting Start migration.
- Once the migration starts, you can monitor the progress through the migration logs displayed in real-time.
MongoDB Database Migration to Elestio
Elestio provides a robust and user-friendly platform for managing your database migrations seamlessly. Whether you are migrating from an on-premises MongoDB database or from another cloud provider, Elestio's migration tool simplifies the process. By following a few straightforward steps, you can securely and efficiently move your MongoDB databases to Elestio, ensuring minimal downtime and disruption to your operations.
This guide will walk you through the process of migrating your MongoDB database from an external source to Elestio. We will cover everything from configuring your migration settings, validating the connection to your source database, and finally starting the migration process while monitoring its progress.
Step 1 - Configure
- Go to the overview of your MongoDB service on Elestio.
- Click on the Migrate Database button.
- A modal window will open, ensure that your target service has enough disk space to accommodate your database
- Click on Get started button.
Step 2 - Validation
- You need to provide the connection details to establish a connection to your source database, enter the required details:
- Hostname
- Port
- Username
- Password
- Click on Run Check to validate the connection.
Step 3 - Migration
- If all checks pass with no errors, you can trigger the migration by selecting Start migration.
- Once the migration starts, you can monitor the progress through the migration logs displayed in real-time.
TimescaleDB Database Migration to Elestio
Elestio provides a robust and user-friendly platform for managing your database migrations seamlessly. Whether you are migrating from an on-premises TimescaleDB database or from another cloud provider, Elestio's migration tool simplifies the process. By following a few straightforward steps, you can securely and efficiently move your TimescaleDB databases to Elestio, ensuring minimal downtime and disruption to your operations.
This guide will walk you through the process of migrating your TimescaleDB database from an external source to Elestio. We will cover everything from configuring your migration settings, validating the connection to your source database, and finally starting the migration process while monitoring its progress.
Step 1 - Configure
- Go to the overview of your TimescaleDB service on Elestio.
- Click on the Migrate Database button.
- A modal window will open, ensure that your target service has enough disk space to accommodate your database
- Click on Get started button.
Step 2 - Validation
- You need to provide the connection details to establish a connection to your source database, enter the required details:
- Hostname
- Port
- Database Name
- Username
- Password
- Click on Run Check to validate the connection.
Step 3 - Migration
- If all checks pass with no errors, you can trigger the migration by selecting Start migration.
- Once the migration starts, you can monitor the progress through the migration logs displayed in real-time.
Hydra Database Migration to Elestio
Elestio provides a robust and user-friendly platform for managing your database migrations seamlessly. Whether you are migrating from an on-premises Hydra database or from another cloud provider, Elestio's migration tool simplifies the process. By following a few straightforward steps, you can securely and efficiently move your Hydra databases to Elestio, ensuring minimal downtime and disruption to your operations.
This guide will walk you through the process of migrating your Hydra database from an external source to Elestio. We will cover everything from configuring your migration settings, validating the connection to your source database, and finally starting the migration process while monitoring its progress.
Step 1 - Configure
- Go to the overview of your Hydra service on Elestio.
- Click on the Migrate Database button.
- A modal window will open, ensure that your target service has enough disk space to accommodate your database
- Click on Get started button.
Step 2 - Validation
- You need to provide the connection details to establish a connection to your source database, enter the required details:
- Hostname
- Port
- Database Name
- Username
- Password
- Click on Run Check to validate the connection.
Step 3 - Migration
- If all checks pass with no errors, you can trigger the migration by selecting Start migration.
- Once the migration starts, you can monitor the progress through the migration logs displayed in real-time.
DB Clusters
MySQL cluster with Multi-master or Replica mode
If you can’t afford for your database to be down for even a few minutes, a Multi-Master cluster is a great option to ensure high availability.
A multi-master scenario means that one node can be taken offline (e.g. for maintenance or upgrade purposes) without impacting availability, as the other node will continue to serve production traffic. Further, it doubles your capacity to read or write to the database and provides an additional layer of protection against data loss.
MySQL includes a Multi-Master replication, and Elestio enables you to set up your MySQL Multi-Master cluster in just a few clicks.
To begin, you will need to have deployed two MySQL instances
1) Go to elestio Dashboard > Deploy new service> Databases > select MySQL, scroll down and name it for example mysql-1 then click on the "Create service button"
2) Again, go to elestio Dashboard > Deploy new service> Databases > select MySQL, scroll down and name it for example mysql-2 then click on the "Create service button"
3) Wait for the 2 instances to be ready
4) In the elestio dashboard open the service details of mysql-1 and click on the "Configure cluster" button
5) Select in the partner instance dropdown "mysql-2" as the partner, then select "Multi Master" in Cluster mode, then click on "Apply changes" button
6) In the elestio dashboard open the service details of mysql-2 and click on the "Configure cluster" button
7) Select in the partner instance dropdown "mysql-1" as the partner, then select "Multi-Master" in Cluster mode, then click on "Apply changes" button
All done. You now have a multi-master MySQL cluster.
You can now read and write on both instances. If instance A is down you will still be able to use instance B and vice versa. Also, if you restore a backup on one instance it will be automatically replicated to the other instance.
How to use Multi-Master cluster from Node.js
If you can configure your two master clusters in Round Robin in your MySQL driver, a load balancer is not needed. The client-side will split the traffic between your instances and avoid a dead node. This helps to greatly simplify the high-availability system.
The regular MySQL driver for node.js supports this: https://www.npmjs.com/package/mysql#poolcluster
How to test your High Availability Cluster
- Shut down one of the VMs (instance A). You should still be able to connect, read and write on your cluster.
- Restart instance A, wait 30 seconds, then shut down instance B.
- Test your connectivity and read/write access to the cluster again.
- Finally, restart instance B.
How to use PHPMyAdmin to test your cluster
- Open the service details and click on Admin UI to get url and credentials of PHPMyAdmin.
- Open a browser tab with the Admin UI for instance B.
- Open another browser tab for instance A.
- Create a new database in instance A, add a table, and insert a line with sample data.
- Check if the database created from A is correctly replicated to instance B.
- Open the database in instance B.
- Add or edit some rows in the database on instance B and check if correctly replicated to instance A.
KeyDB (Redis compatible) with Multi-master or Replica mode
If you can’t afford for your database to be down for even a few minutes, you need a Multi-Master cluster to ensure high availability. This means that one node can be taken offline (e.g. for maintenance or upgrade purposes) without impacting availability, as the other node will continue to serve production traffic. Further, it doubles your capacity to read or write to the database and provides an additional layer of protection against data loss.
KeyDB is a fork of Redis that brings multithreading and Multi-Master replication, so you can have a highly available cluster of Redis in-memory DB. Usually setting up a cluster is a non-trivial task but in OpenVM you can do this in a few clicks.
To begin, you will need to have deployed two KeyDB instances
1) Go to elestio Dashboard > Deploy new service> Databases > select KeyDB, scroll down and name it for example keydb-1 then click on the "Create service button"
2) Again, go to elestio Dashboard > Deploy new service> Databases > select KeyDB, scroll down and name it for example keydb-2 then click on the "Create service button"
3) Wait for the 2 instances to be ready
4) In the elestio dashboard open the service details of keydb-1 and click on the "Configure cluster" button
5) Select in the partner instance dropdown "keydb-2" as the partner, then select "Multi-Master" in Cluster mode, then click on "Apply changes" button
6) In the elestio dashboard open the service details of keydb-2 and click on the "Configure cluster" button
7) Select in the partner instance dropdown "keydb-1" as the partner, then select "Multi-Master" in Cluster mode, then click on "Apply changes" button
All done. You now have a multi-master KeyDB cluster.
You can now read and write on both instances. If instance A is down you will still be able to use instance B and vice versa. Also, if you restore a backup on one instance it will be automatically replicated to the other instance.
How to use Multi-Master cluster from Node.js
////////////// NodeJS sample //////////////
const Redis = require("ioredis");
const cluster = new Redis.Cluster([
{ port: 23647, password:'FIRST_INSTANCE_PASSWORD_HERE', host: "Type_your_first_node_ip_here" },
{ port: 23647, password:'FIRST_INSTANCE_PASSWORD_HERE', host: "Type_your_second_node_ip_here" }
]);
cluster.set("foo", "bar");
cluster.get("foo", (err, res) => {
// res === 'bar'
});
////////////// ////////////// ////////////// //////////////
How to test your High Availability Cluster
- Shut down one of the VMs (instance A). You should still be able to connect, read and write on your cluster.
- Restart instance A, wait 30 seconds, then shut down instance B.
- Test your connectivity and read/write access to the cluster again.
- Finally, restart instance B.
Use Redis Insight to test your cluster
- Open the service details and click on Admin UI to get url and credentials of Redis Insight.
- Open a browser tab with the Admin UI for instance B.
- Open another browser tab for instance A.
- Go to Local Redis > Browser > Add Key.
- Create a key, of type String, named ‘A’, with value 100, then click on Add.
- Go to the other browser tab for instance A and select Local Redis > Browser > and check if you see key A with the correct value.
- You can also test it by modifying the A key - e.g. set another value, or by creating a new key and checking in your first tab if the change has been correctly replicated.