bhushangawale avatar image
0 Votes"
bhushangawale asked Mike-Ubezzi commented

Replicate production Maria DB server to Maria DB Azure PaaS

Hello all,

we have been working on a customer use case where Maria DB is installed on the Azure VM and contains several large databases that are live in production. Customer wants to get this migrated to Maria DB PaaS service of Azure with minimal downtime and hence the most feasible way to get this done appears to be the replication. (though it has its own requirements and limitations that would still ask to restart the source database server instance resulting into minor downtime).

As per the documentation here , it says that the binary logging has to be enabled on the source server because the replication is primarily driven by that. Upon checking the source system in our scenario, the binary logging does not seem to be enabled. So does this mean that we wont be able to use the replication now?

If the binary logging on the source database is enabled now and if replication is configured, would the replication still occur ensuring all the source content in all databases will be replicated to Maria DB PaaS server instance? Note that what I mean by all content is - the content that was created before enabling binary logging as well as content that is created after enabling it.

Idea is to establish the sync and let the source system running for few days (as it is live) and then perform the cut-over at some point by updating other apps that would now point to the azure instance.

Please share your views in case if you have done similar or have any suggestion to get this working using some different approach?

Thanks in advance.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

Mike-Ubezzi avatar image
0 Votes"
Mike-Ubezzi answered Mike-Ubezzi commented

The binary logging functionality is how replication is facilitated between the master and the replica and is required as new items are written to the on-premise MariaDB instance. For the older events, you would need to run a specific sync or clone as a database seeding effort and then with binary logging enabled on both master and replica, can leverage data-in replication going forward.

1) Set-up and configure the Azure Database for MariaDB service.
2) Set-up replication between on-premise and Azure.
3) Clone the on-premise database to Azure and initiate Data-in Replication.

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thanks for the response. Is it possible to enable the data-in replication for select databases on source server and keep on doing it for other databases gradually rather than enabling all at a time? If yes, any recommendation how to do it? the documentation link referred above seem to be getting it done for all databases on the source server at a time.

0 Votes 0 ·

Hi @bhushangawale That functionality is not currently available and I don't see this as a feature in the pipeline. What you can do is UpVote and comment upon the following feature request with additional details pertaining to being able to configure subsets of databases hosted by the service, instead of everything. Please see: Multisource replication. You are also free to create a new entry with specific details pertaining to your use case.

Please let me know if there are any additional questions.


0 Votes 0 ·