> For the complete documentation index, see [llms.txt](https://docs.tessell.com/tessell/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tessell.com/tessell/tessell-for-mysql/db-services/readme-mysql/homepage-mysql/instances-mysql.md). # Instances MySQL database services can be deployed on the Tessell portal with the following configurations: | Instance type | Description | | ----------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Single instance database service | Database service with one instance in a given region and availability zone. | | Multi-AZ database service | Database service with one primary, and one or two synchronous failover replica(s). The instances must be in the same region but can be in the same or different availability zone as the primary instance. The failover replicas are always homogeneous in nature (infrastructure, parameters, storage, IOPS, and so on). All planned operations are performed in rolling mode on these services, keeping downtime to a minimum. | | Database service with Disaster Recovery instance (DR) | Disaster Recovery instances are asynchronous replica instances that can be added in the same or different region as the primary. Multiple DR instances can be added to a database service. No automatic failover support. DR can be added to both single instance and Multi-AZ database services. | | Database service with Read Replica | Read Replica is an asynchronous replica opened in read-only mode. You can use this instance for read-only queries. | ### Create a DR Replica For information on creating a DR replica, see [Adding Disaster Replica](/tessell/tessell-for-mysql/db-services/adding-disaster-replica.md). ### Create a Read Replica For information on creating a read replica, see [Adding Read Replica](/tessell/tessell-for-mysql/db-services/adding-read-replica.md). As an alternative method, use the code to add the instance. 1. Click the **Code** button in the top-right corner to view the **Code for Add New Instance** window. 2. On the left-hand side, view the API, its type, and the payload. 3. On the right-hand side, view the code to create instances in Shell, Python, Go, Java, JavaScript, and PowerShell. 4. Use the copy and download buttons to save the code. 5. Click **Close** to return to the main window. *** The Instances tab displays the list of all configured instances for your database service in tabular format. Each row displays the details of each instance configured per node. Each column provides the following information: * **Name** — Displays the name of the instance configured as per the node, along with the node number. This name is generated automatically in incremental order: * `default-node-0` for primary * `default-node-1` for replica 1, typically an HA replica configured for automatic failover * `-node-` for replica 2 onwards, where the digit starts from 0 for a new Read Replica or DR replica and increases as per the number of nodes configured * **Status** — Displays the status of each instance. The status of the instances can be: | Status | Description | Actions Allowed | | ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | UP | The database instance is up and running. Connections are allowed when it is in UP status. | | | DOWN | The database instance is down. | Raise a Tessell support ticket if the instance needs to be revived. | | STOPPED | The database instance is not running and is completely stopped. | Start the service | | CREATING | Database instance provision is triggered and the creation process is in progress, or a new instance is being added to the existing database service. | No actions allowed | | DELETING | Database instance delete is triggered and the deletion process is in progress, or an instance is selected to be deleted from the database service. Only Read Replica and DR instances can be deleted from a database service. | No actions allowed | | REBUILDING | Compute shape or storage resize is triggered for the instance. | No actions allowed | | REBUILD\_FAILED | Compute resize or storage resize was triggered and did not complete. | All actions are allowed | | PATCHING | Available patches are selected to apply for the database service. | No actions allowed | | PATCH\_FAILED | Patching for the database instance has failed. | All actions are allowed | | UPDATING\_PARAMETER\_PROFILE | Parameter profile update is triggered for the instance. | No actions allowed | | PARAMETER\_PROFILE\_UPDATE\_FAILED | Parameter profile update failed. | All actions are allowed | * **Role** — Displays the role of your instance. The possible values are Primary, HA Replica (Automatic Failover), Read Replica (RR), and Disaster Recovery (DR). Below the role is the name of the server where your instance resides. * **Server** — Displays the server name where the instance is deployed. Clicking the server name takes you to that server's home page in the Servers app. * **Region/Zone** — Displays the name of the cloud and its region on which your instance is hosted. * **Parameter Profile** — Displays the name of the parameter profile selected for your instance at the time of provisioning. * **Compute** — Displays the name of the compute shape selected for your instance at the time of provisioning. The allocated vCPUs and memory for this compute shape are displayed below the name. * **Created** — Displays the date and time at which your instance was created. * **Storage** — Displays the storage size specified during provisioning. To view the storage provider, throughput, and IOPS, click **See details** below the storage size. * **Connection Endpoint** — Displays the host name for your instance. To view the Service URL, Host, Port, and Username, click **See Details** below the host name. * Using the ellipsis icon, you can create private links for DR and RR nodes separately. You can create, update, or delete this private link. > **Note**: Creation of private links for DR and RR nodes is currently supported for AWS cloud only. ### Switchover to failover replica For information on switchover to failover replica, see [Switchover to Failover Replica](/tessell/tessell-for-mysql/db-services/multi-az-deployment-for-mysql.md#switchover-in-multi-az-deployment). ### Switchover to DR replica For information on switchover to DR replica, see [Switchover to DR Replica](/tessell/tessell-for-mysql/db-services/switchover_to_dr.md). **Figure 1: Instances tab** ![](/files/hx6c9OeGGIEgYaolgIeR) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.tessell.com/tessell/tessell-for-mysql/db-services/readme-mysql/homepage-mysql/instances-mysql.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.