Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Mirroring in Fabric is an enterprise, cloud-based, zero-ETL, SaaS technology.
In this section, you learn how to create a mirrored Azure Database for MySQL, which creates a read-only, continuously replicated copy of your MySQL data in OneLake.
Prerequisites
- Create or use an existing Azure Database for MySQL.
- If you don't have an Azure Database for MySQL, create a new server.
- As a tutorial, use a copy of one of your existing databases or any existing test or development database that you can recover quickly from a backup. If you want to use a database from an existing backup, see Restore a database from a backup in Azure Database for MySQL.
- An existing capacity for Fabric. If you don't have one, start a Fabric trial.
- The Fabric capacity must be active and running. A paused or deleted capacity also stops Mirroring and no data is replicated.
- Fabric tenant settings. Ensure the following two Fabric Tenant settings are enabled:
- You need a member or admin role in your workspace when creating a mirrored database from the Fabric portal. During creation, the managed identity of Azure Database for MySQL is automatically granted "Read and write" permission on the mirrored database. Users with the contributor role don't have the Reshare permission necessary to complete this step.
- If your server isn't publicly accessible and doesn't allow public access to connect to it, you can create a virtual network data gateway or set up on-premises data gateway to mirror the data. Make sure the Azure Virtual Network or the gateway machine's network can connect to the Azure Database for MySQL and is allowed by the firewall rule.
- Fabric Mirroring isn't supported on a Read Replica, or on a Primary server where a Read Replica exists.
Prepare your Azure Database for MySQL
Mirroring in Azure Database for MySQL is based on Logical Replication and requires some specific prerequisites to be configured before being able to connect to your data.
For detailed instructions, see Mirroring Azure Database for MySQL.
Create a mirrored Azure Database for MySQL
- Open the Fabric portal.
- Use an existing workspace or create a new workspace.
- Go to the Create pane or select the New item button.
- Select + New Item and create a Mirrored Azure Database for MySQL (preview). Fab4.png
Connect to your Azure Database for MySQL and start mirroring
The following steps guide you through the process of creating the connection to your Azure Database for MySQL:
- Under New sources, select Azure Database for MySQL (Preview). Or, select an existing Azure Database for MySQL connection from the OneLake hub.
- If you selected New connection, enter the connection details to the Azure Database for MySQL.
- Server: Find the Server name by going to the Azure Database for MySQL Overview page in the Azure portal. For example,
<server-name>.mysql.database.azure.com. - Database: Enter the name of the database to replicate.
- Connection: Select "Create new connection" or reuse an existing connection.
- Connection name: An automatic name is provided. You can change it.
- Data gateway: Select the default (none) or the name of virtual network data gateway / on-premises data gateway you set up according to your scenario.
- Authentication kind: Basic (MySQL Authentication)
- Leave Use encrypted connection checkbox selected, and This connection can be used with on-premises data gateway and VNET data gateway unselected.
- Server: Find the Server name by going to the Azure Database for MySQL Overview page in the Azure portal. For example,
- Select Connect. If all the credentials are correct, the connection is tested and saved. If the credentials aren't correct, the creation fails with errors.
- After the connection is created successfully, a list of tables in the database mirror is available to select. You can select up to 1,000 tables at a time.
- Select the tables, give the mirror a name, and select Create mirrored database. This action starts the mirror creation.
- After some time (few minutes), you see Rows Replicated and the data is visible in the data warehouse view, also known as Mirrored Database view. The status changes to Running. This view also serves as a management interface to start, stop, and monitor replication. Fab8.png
- Now that your data is up and running, various analytics scenarios are available across all of Fabric.
Monitoring replication
After you create the mirror, monitor the health of replication. For more information, see Monitor Mirrored Database Replication.
Data availability in OneLake
When replication finishes, the SQL Analytics endpoint has all tables available.