ApsaraDB RDS for MySQL native replication instances let you manage data synchronization and replication topologies using standard MySQL replication commands — giving you native MySQL flexibility within a fully managed cloud database.
Unlike standard RDS instances, native replication instances expose privileged replication controls (CHANGE MASTER, START SLAVE, GTID_NEXT) for direct integration into existing replication architectures spanning on-premises IDCs, Elastic Compute Service (ECS), and other cloud platforms.
Use cases
-
Disaster recovery: Replicate data between on-premises data centers, Alibaba Cloud, and other cloud providers. If the primary database fails, switch to the secondary to minimize downtime.
-
Cloud migration: Use RDS backups combined with native replication to migrate a self-managed MySQL database from an IDC or ECS instance to the cloud with minimal risk. For step-by-step instructions, see Create a cloud-based secondary database using RDS native replication.
-
Cross-cloud high availability: Build a high-availability MySQL cluster across multiple cloud providers (such as AWS and Azure). Configure flexible replication topologies and failover policies to achieve cross-cloud disaster recovery without vendor lock-in.
-
Custom replication topologies: Define complex topologies — primary-replica, primary-primary, or ring — to meet specific architectural requirements.
-
Unified operations: Integrate RDS with Alibaba Cloud ecosystem tools for centralized management. Use RDS backup tools for automated full backups, Database Autonomy Service (DAS) for audits and fault analysis, and Alibaba Cloud big data services for data analytics across hybrid environments.
Key capabilities
MySQL compatibility
Native replication instances are fully compatible with standard MySQL replication commands and protocols. Use CHANGE MASTER, START SLAVE, and GTID_NEXT to manage replication topologies. Integration with existing self-managed MySQL databases, management platforms, and open-source tools like Orchestrator requires no additional configuration.
For configuration details, see Use native replication instances.
Hybrid and multi-cloud connectivity
Connect RDS instances into replication topologies that span on-premises IDCs, ECS, and other cloud platforms including AWS and Azure. Native replication instances break through single-cloud boundaries, enabling cross-cloud data synchronization without third-party middleware.
Intelligent operations and maintenance
-
Replication monitoring: Visual dashboards show replication status in real time.
-
GUI-based management: Integrate with Data Management Service (DMS) for graphical instance management.
-
Intelligent diagnostics: Integrate with DAS for automated performance analysis and fault detection.
-
Online scaling: Upgrade or downgrade instance specifications and kernel versions without replication interruption.
Reliability and security
Native replication instances inherit ApsaraDB RDS stability and security: automatic backups, permission system integration, and compatibility with RDS backup services and big data analytics systems.
Billing
Native replication is not a separately billed feature:
-
New instances: Standard instance pricing applies when you create an instance with native replication enabled. There is no additional charge for the native replication capability itself.
-
Existing instances: Upgrading an existing RDS instance to enable native replication incurs no additional fees.
-
OSS storage: If you import full data by uploading a self-managed database backup to Object Storage Service (OSS), standard OSS storage fees apply while the backup is stored in OSS.