Vultr's managed databases automate many challenging aspects of database administration so that you can stay focused on your app. They are secure, redundant, and do not require manual installation or configuration. In addition, they offer automated failover to replica nodes, scheduled automatic updates, end-to-end security, and full logs.
Here are some of our most frequently asked questions.
You can reach your database over the public internet with the connection string shown on the Overview tab of the Database Details page in the Vultr customer portal.
Your connection string connects to the primary node and will automatically switch to the newly-elected primary node in case of a database failover.
Yes, you will find your connection information in the Vultr customer portal.
Managed databases do not allow customers to create superuser accounts. All user management is done through the Vultr customer portal.
When first deployed, a database cluster is open to all. Use the Trusted Sources section of your managed database configuration screen to restrict access to your database cluster before creating your databases or users. You should also use a strong password for all user accounts.
Your data is encrypted at rest and in transit.
Yes, managed databases are fully backed up. To restore a backup, please open a support ticket.
Users cannot change MySQL database properties or use the
root user for cluster stability. However, you can view the database properties with the
SHOW VARIABLES; SQL query.
ANSI (Combination Mode)SQL mode includes the following SQL modes:
ANSI (Combination Mode)is enabled, that setting will take precedence.
ONLY_FULL_GROUP_BY, you will also need to disable
ANSI (Combination Mode), because it is a part of that mode bundle.
TRADITIONAL (Combination Mode)includes the following SQL modes:
PAD_CHAR_TO_FULL_LENGTHSQL modes at this time.
Yes, you must use primary keys for all database tables, which is enforced through the database configuration.
Vultr's managed databases automate many challenging aspects of database administration so that you can stay focused on your app. They are secure, redundant, and do not require installation or configuration.
A database cluster consists of a primary node and, optionally, one or more replica nodes.
Vultr uses the most popular database engines:
Vultr offers several server types:
We have plans ranging from 1 to 96 vCPUs, and between 1 and 256 GB of RAM. Not all plan sizes are available for every server type.
MySQL databases use the InnoDB storage engine. We do not support other storage engines.
We use the latest version of MySQL and keep your server updated.
You can deploy a managed database cluster at any of Vultr's locations. All nodes in the cluster are deployed in the same location.
Your upgrades are managed automatically. You can schedule the automatic upgrades in the Settings tab of the customer portal or trigger an upgrade manually.
Managed database clusters are self-service, and you can provision a new database cluster in just a few minutes through the customer portal.
No, all nodes in your cluster are the same type.
This is not available during the beta. This feature will be available in the public release.
Migrating a cluster to a new location is not supported during the beta, but it's a planned feature for the final release. If you have questions about migration, please contact our support team.
Scaling, either horizontally by adding or removing nodes or vertically by selecting a different server type, is not supported. Instead, you must migrate to a new cluster. Migrating a cluster is not supported during the beta, but it's a planned feature for the final release. If you have questions about migration, please contact our support team.
You may need to migrate a cluster to:
Migrating a cluster is not supported during the beta, but it's a planned feature for the final release. If you have questions about migration, please contact our support team.
During updates and node failover, your application may experience brief outages of up to 15 seconds, which will cause your applications to disconnect from your database nodes. You should configure your client applications for a reasonable number of reconnection attempts before timing out to maintain availability.
The number of database connections allowed depends on the amount of memory allocated to your database. This information is not available during the beta. We will publish a table with details after the public release.
You can select the update window, but you cannot defer an update from happening.
Data transfer through the public internet counts against a monthly bandwidth quota.
Vultr backs managed databases with a 100% uptime guarantee. In addition, Vultr continuously monitors your database clusters. If you deploy replica nodes, they will automatically failover by electing a new primary if the primary node becomes unavailable.
Vultr managed databases are popular open-source databases. You can find more answers to frequently asked questions on these websites: