We have our Azure API management is provisioned in East US and our hot-standby region is West US.
I know that we can take the backup of the source APIM and restore it on destination APIM. However I want to have a hot-standby running parallel without serving until a DR situation.
How do I configure the Azure API management to support the disaster recovery with automatic fail over?
Would it impact the configured URLs/domains?
Related
I am trying to accomplish one task which is below.
What I am doing it.
All my users are on Premises.
Application is hosted on Azure VM IaaS.
Question =>
Azure cloud application talk with Internet and download huge packages and share with client which is on- Primes. So I am trying to understand the Risk and latency matrix between on-Prime users and Azure cloud application.
If any one has done some sort of thing and encounter latency issues and what will be possible fixes for that?
Note=> I can't Migrate user to Azure cloud as of now.
To encounter latency issues, please try the following:
To reduce the latency between on premises client and azure cloud application make use of Azure HPC cache.
Azure HPC Cache reduces latency for applications where data may be tethered to existing infrastructure because of dataset sizes and operational scale.
Azure HPC caches active data automatically that is present in both on-premises and in Azure.
You can make use of Accelerated networking where communication will be done more fast.
Try eliminating network congestion.
Try reducing number of network nodes needed to traverse from one stage to another.
Make use of Azure ExpressRoute and Azure Analysis Services to reduce Network latency.
Azure ExpressRoute creates a private connection between on-premises sources and the Azure.
Azure Analysis Services avoids the need for an on-premises data gateway and generally eliminates network latency.
For more in detail, please refer below links:
https://azure.microsoft.com/en-us/blog/azure-hpc-cache-reducing-latency-between-azure-and-on-premises-storage/
https://blogit.create.pt/gustavobrito/2017/11/27/latency-test-between-azure-and-on-premises-intro/
https://viniciusdeschamps.com.br/3-ways-to-reduce-network-latency-in-azure/#how-can-I-measure-network-latency
I have a VM in Azure in location Central US . I have some restore points (fullbackups).
Can i restore the VM to a different resourcegroup in West US and reconnect to it with RDP ?
this is for disaster recovery if there is an issue with the Azure location or VM .
Also how can we guarantee that any location wont have issues ?
Interesting question.
You want to restore a VM hosted on the Central US to the West US.
Let's look into the Public Docs.
You could use the Cross Region (secondary region) restore to
restore Azure VMs in the secondary region, which is an Azure
paired region.
You can restore all the Azure VMs for the selected recovery point if
the backup is done in the secondary region.
During the backup, snapshots aren't replicated to the secondary
region. Only the data stored in the vault is replicated. So secondary
region restores are only vault tier restores. The restore time for the
secondary region will be almost the same as the vault tier restore
time for the primary region.
This feature is available for the options below:
Create a VM
Restore Disks
Unfortunately, I don't see the Central US region pairs with the West US region. So for your question if you can select your specific regional pair, answer is no.
Some Azure services rely upon regional pairs, such as Azure's
redundant storage. These services don't allow you to create new
regional pairings. Similarly, because Azure controls planned
maintenance and recovery prioritization for regional pairs, you can't
define your own regional pairs to take advantage of these services.
However, you can create your own disaster recovery solution by
building services in any number of regions and leveraging Azure
services to pair them.
I hope above helped to answer your questions.
If we want to failover Replicated VM in Azure using Azure Site Recovery.
Can we replicate VMs to a different subscription ?
Eg. When configuring ASR - Disaster recovery I gave subscription name 'ABC' for replication to happen.
At the time of failover I want VM to failover to 'PQR' subscription and not 'ABC' where replication was happening till now
Have any one tried this with PowerShell ?
#DBA Admin The Subscription cannot be changed once selected. However, Azure site recovery does offer "Cross-subscription disaster recovery for Azure virtual machines"
I have an Azure Event Hubs in WEST US with Geo-Recovery enabled to sync with EAST US. I don't want to automatically failover to EAST US in case of the Primary outage, can we disable the automatic failover? I want to manually do the failover post business confirmation.
There is no automatic failover from Microsoft end when you have set up the Geo-disaster recovery for the event hub. You need to manually do the failover either from azure portal/REST API's. The failover can also be automated based on your business scenario where your custom application will monitor the resource and based on your business conditions your custom application will be calling the event hub REST endpoint to initiate the failover.
We have an application built of multiple Logic Apps. We will use Azure API Management to consolidate all those endpoints into a single endpoint.
We need this application to be highly available, so we want to deploy it to 2 regions (eg West Europe and North Europe).
As of Nov 2018, the only API Management plan that supports multi-region is the Premium plan that costs 18x the Basic plan. The Premium plan is way out of our budget.
We had the idea to setup two Basic API Management units, one for each region, having both configurations synchronized, and placing a Traffic Manager in front of both.
Assuming that we will only use the gateway functionality of API Management (not developer/publisher portal, authentication etc), what will we be missing with our "Poor Man's Multi Region" solution instead of going with the "native" multi-region of the Premium plan?
Whatever you will have to build will be missing (as you pointed out):
Configuration synchronization - you will have to make sure that configuration is synchronized between multiple services.
Traffic Manager - you will have to have TM or something else on top of services to reroute traffic in case of DR.
Scale and everything else from this list: https://azure.microsoft.com/en-us/pricing/details/api-management/
It is possible to create multi region DR of Azure API Management in Developer/ Basic/ Standard tier.
High level steps -
Create two API Management in Standard mode. One in primary region and other in secondary region.
Configure APIs and related backend in API Management primary. As you API Management standard is not part of VNET, the backend APIs will require public IP to get imported in API Management.
Create Azure AD Application to have necessary permission to make changes in API Management instances in cross region.
Allow rights on resource groups of both API Management in two regions.
Create two logic apps. One to create backup of primary API Management. Second will be used to restore the same backup in secondary region API Management.
Create traffic manager and add API Management IP address/ domains names as endpoint profiles. Configure Traffic manager in Failover/ Priority mode.
Configure status page of API Management in Traffic manager to know health status of API Management for traffic manager so that it can switch to secondary region in case of DR situation.