I'm using Azure database for mysql - Flexible server and we would like to have Disaster recovery in another Azure region. As per the below documentation, the cross region read replica is not supported. My question is what is the correct way to have cross region Disaster recovery?
https://learn.microsoft.com/en-us/azure/mysql/flexible-server/concepts-read-replicas
-Suresh
Cross region read replicas for MySQL Flexible Server is part of our backlog and will be coming soon. Meanwhile, you can leverage data-in replication to achieve the same.
https://techcommunity.microsoft.com/t5/azure-database-for-mysql-blog/cross-region-replication-using-data-in-replication-with-azure/ba-p/3563231
not all regions for the azure MySQL server supporting the replicating so the best way and the fastest one is to create another MYSQL server that is supporting the replicating
in the following ling you gonna find how to make the replication :
https://learn.microsoft.com/en-us/cli/azure/sql/db/replica?view=azure-cli-latest
try to create the server in westus for example i remember that is supporting the replication in another region
Related
I hope I am asking this in the correct community. I did check for SQL Azure in others, but could not find anything so here goes.
I am trying to work out the best strategy to create a backup of my SQL Azure DB if my main datacentre has a significant availability or integrity problem. My initial thought was to "Create a Database", in a different region, on a new DB Server, using the "Geo-Replicated Backup" which works excellently. However because it is on a new DB Server I lose all of my Short Term (PITR) and Long Term Retention(LTR) Backups which I might need to restore from for data correction or compliance.
So how can I backup this "history". I may have missed something simple, but my only ideas at present are:
Take automated "Exports" to BACPACs" to Azure Storage, say weekly.
Use specialised Backup software such as VEEAM SQL Azure Backup which retains multiple versions, and can operate at hourly intervals. Works off Transaction Logs.
Use Azure Failover groups which effectively use 2 DB Servers and 2 PITR and LTR setups.
Thanks in advance,
I want to use replication only for table view which I have defined.
However, looking at online document , this seems to be not possible since server name and location is available for parameters.
Is it possible to only replicate table view using replication for Azure DB for PostgresQL?
No, it doesn't.
Azure PostgreSQL as a solution provides a managed database-as-a-service. Consequently, the solution addresses concerns with enablement at the infrastructure level. Therefore, a replication is only applicable to the server.
I have a Azure SQL Database in WEST-US region and it is Geo-Replicated to EAST-US region. Is it possible to enable the read-scale out only for the Geo-replicated database. I have tremendous amount of BI load on secondary region and really want to leverage the read scale out feature only in the secondary region. All BI ETLs directly point to secondary endpoint and would like to optimize the BI workload with the read-scale out feature.
I found the official document here . However, I didn't find it to be clear if I can enable it only for geo-replicated database.
It doesn't really matter(?) You don't have to use the local HA readable secondary even if it is enabled. You control this with the readintent tag on your connection string. (It is already there for premium + vcore databases and it's just a question of whether you want to enable it). So, if you enable it for both and just use it on the geo secondary, that works just fine.
what is the best way to limit latency for SQL Azure in global applications?
My Application uses SQL Azure and would like to know based on the network location of users if its possible to connect SQL Azure near to users.
So Logically would need to have SQL Azure database with global replication but not geo-replication as each copy would serve as Master and not secondary.
Thank you in advance.
You may want to try CosmosDB to distribute data globally and obtain low latency as explained on this article and this documentation.
For replicating data using SQL Data Sync with Azure SQL Database, take in consideration paired regions which may reduce latency. With SQL Data Sync a hub database can be defined and many member database on another region, and data can be synched on both ways between the hub and any member database.
I want to confirm our understanding of how our Azure SQL databases are being backed up to enable point in time restore. We have not currently configured geo-replication to have the database available in another region. We may in the future as some data analysis is done. But my understanding is that the database is still being backed up to a geo redundant location so I could do a geo-restore if there was an issue with the data center that houses my sql database. Is that correct or do I need to enable geo-replication and pay for a second database in order to have a disaster recover option if the datacenter had an issue.
To clarify further: I think this article states what I'm saying in the Geo-Restore section.
https://azure.microsoft.com/en-us/documentation/articles/sql-database-business-continuity/
Thanks
Yes, all databases have a geo-replicated copy for disaster recovery purposes. For more details, please see the following: https://azure.microsoft.com/en-us/blog/azure-sql-database-geo-restore/
Geo-restore uses the same technology as point in time restore with one
important difference. It restores the database from a copy of the most
recent daily backup in geo-replicated blob storage (RA-GRS). For each
active database, the service maintains a backup chain that includes a
weekly full backup, multiple daily differential backups, and
transaction logs saved every 5 minutes. These blobs are geo-replicated
this guarantees that daily backups are available even after a massive
failure in the primary region.
Yes, Azure SQL Databases are automatically backed up to a different Azure data center using Geo-Replication. This is an automatic features of Azure SQL that is baked into the service offering.
Here's a blog post with further information about Azure SQL Data Replication:
https://azure.microsoft.com/en-us/blog/azure-sql-database-standard-geo-replication/