This article is to support customers of Relational DB Service, Lumen's database-as-a-service product. The responses in this FAQ document are specific MySQL-compatible Relational DB.
P: How will I connect to my MySQL instance?
R: You will instantly receive your connection string information when you create your database subscription. Use the provided connection string, port, and your selected database credentials to connect to and manage your database using your favorite MySQL Client or through Command Line Interface (CLI).
P: How is my data isolated from other Relational DB tenants?
R: Each MySQL instance lives on its own Virtual Machine.
P: Are there published APIs that I can use in my own automation?
R: Sim. We have published APIs for all actions that can be performed in the UI. API endpoint is https://api.rdbs.ctl.io/. For more information and to get started using our APIs, you can view our API documentation.
P: Can I choose to replicate my data for higher availability?
R: Customers are given the option to replicate their database instance during the ordering/provisioning process. If replication is chosen, a replica instance will be created within the same datacenter. We use logic to ensure that the primary and replica instances do not share the same host or storage volume. The service will then monitor both primary and replica and will auto-failover to the replica instance if the primary becomes unavailable. Customers can also choose to perform a manual failover, if needed. For more information on replication and failover, see our KB on Replication and Failover.
P: Is the replication synchronous or asynchronous?
R: Replication is asynchronous across a local 10G network, resulting in real time replication assuming normal networking conditions.
P: Can I access my replica instance separately in order to load balance my read requests?
R: No. The replica instance is used for high availability purposes only. A separate read replica with unique connection string is a future feature.
P: I understand that SSL Encryption options are available. Will my data be encrypted in transit and/or at rest?
R: Upon database subscription, you will be given the option to download a self-signed cert that can be consumed by your target application. When implemented, your database connection is encrypted as well as your data in transit. Please see the KB article on Connecting to MySQL Relational DB Over SSL for additional details. At this time data-at-rest encryption is not supported.
P: How will I know when my database instance is reaching maximum capacity?
R: Customers have the option to sign up to receive email notification when their CPU and/or storage has reached 80% capacity. Customers who sign up for these notifications will be notified again when capacity reaches 90%. Upon notification, customers can easily scale their database instance size through API or UI.
P: How can I grow or shrink my database instance?
R: Customers can easily scale their database instance size through the UI or API. CPU and RAM can be scaled up or down and storage can be scaled up only. Adding or removing memory or reducing CPU will require a database restart. Growing CPU or storage will not require a restart of the database. Please see the KB article on Resizing a Relational DB Instance
P: I understand that Lumen is backing my data up daily. How can I access my backups in order to restore?
R: If you need to restore from an available backup, you can leverage the Restore Backup API or perform the restore in the Control Portal. For more information on performing database restores in Control, please see the KB on Backups and Restores.
P: Are my backups encrypted?
R: Sim. All backups are encrypted at rest.
P: How long are my backups being held?
R: At the time of Relational DB subscription creation, the user will define backup retention policy. Customers can select a retention policy as short as 1 day or as long as 35 days. Customers can also change the backup retention policy post-provisioning through the Subscription details page of the UI or through API.
P: Where are my backups being held?
R: For disaster recovery purposes, backups are held offsite at least 350 miles away from your primary database. All North American instances are held in North America. All GB1 instances remain in London. All GB3 instances remain in Ireland. SG1 backups remain in Singapore.
P: Will the product support the use of standard MySQL management tools including the ability to monitor and report on database tasks within the tool?
R: Sim. Your database instance is on a dedicated VM and there are no restrictions for any management utilities. In fact, we expect that much of the database management will be accomplished using MySQL Command Line Interface or a MySQL client of your choice.
P: Can I use MyISAM?
R: Because MyISAM locks tables, it is not reccomended. InnoDB is the default and should be used when possible in order to avoid issues with tables being locked.
If you have questions or feedback, please submit them to our team by emailing firstname.lastname@example.org.