Summary of TaurusDB Best Practices
This document describes some detailed common practices to help you easily use TaurusDB.
| Category | Reference | Description |
|---|---|---|
| Data migration | Describes how to migrate data from self-managed MySQL databases to TaurusDB. | |
| Describes how to migrate data from MySQL databases on other clouds to TaurusDB. | ||
| Read/Write splitting | Describes how to grant remote login permissions to an account. | |
| Describes how to configure a connection health check mechanism. | ||
| Describes how read requests are routed to the primary instance. | ||
| Backup and restoration | Describes how to restore deleted instance data on the console. | |
| Describes how to restore deleted database data on the console. | ||
| Describes how to restore deleted table data on the console. | ||
| Cold and hot data separation | Describes how to implement cold and hot data separation for partitioned tables. | |
| Describes how to implement database-level cold and hot data separation. | ||
| Security | Provides guidance on TaurusDB security configurations. | |
| Monitoring alarms | Describes how to configure TaurusDB metric alarm rules. |
What is your overall rating for this page?
Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot
