This month, the Chinese version of MySQL Database on Azure released two new features:
1. master-Slave copy--read-only instance
Prior to this, the MySQL database on Azure is also supported for master-slave replication, but the MySQL database on slave instance--azure that can only be deployed as on-premises is not available as master.
With this update, we can create one or more slave instances for the MySQL database on Azure: read-only instances.
This makes it easy for users to implement read-write separations for applications that use MySQL, such as retrieving reports from slave. It also improves the usability of MySQL database, and when the master instance fails, the slave instance can be promoted to master manually to ensure the continuity of the business.
The current MySQL database on Azure master-slave replication still has some limitations:
- The slave database must be in the same location/datacenter as master and does not support replication across locations/datacenters.
- The on-premises database cannot be used as a slave.
2, any time point rollback
MySQL database on Azure now allows users to recover the database to any point in the last 7 days, and the recovered databases will run on the user-created server instance. Support for rollback at any point in time allows the user to worry about data corruption or loss, greatly improving the user's ability to detect and repair data.
This function can also be seen as the snapshot of MySQL database.
The user can choose to use a full backup to restore or fall back to a point in time within seven days, while restoring the MySQL database's operating interface.
It is important to note that whether you restore from a full backup or fall back to a point in time, a new MySQL instance is created, not a restore/fallback on the original DB instance.
Finally, share a MySQL example database (equivalent to the SQL Server AdventureWorks sample database) to easily test MySQL database functionality.
https://github.com/datacharmer/test_db
MySQL Database on Azure new features