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"
Related
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.
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?
Today I am noticing that the Azure Group, I dont know when Azure created the
"DefaultResourceGroup-EAU" resource group, and in this group two item is placed
I am not using any Azure Container Registry service and AKS, should I remove this group because it paying in my invoice, I just only have Azure Web Apps and Azure SQL databases and one VM only, should its impact on my above mentioned services after deletion?
certainly not in terms of how those services function, but monitoring might be impaired if you delete those.
Those resources look like they were created alongside AKS cluster. Doesn't mean that they were only being used for that, but highly likely.
We are setting up Azure Site Recovery for a VmWare environment and we've been through the process of setting up the configuration server and the site recovery wizard, but we're a bit stuck at selecting the VMs to replicate. When we select more than 10 it comes with an error "You can select a maximum of 10 items to protect"?
We've built the server using the following specs which according to Microsoft should be enough to accommodate 100 servers.
Spec: 8vCPU, 16GB Memory
Is there a limitation I have missed?
The links I have followed are:
https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-plan-capacity-vmware
https://learn.microsoft.com/en-us/azure/site-recovery/vmware-physical-large-deployment
You can have maximum of 100 server / CS but at a time you can't select more then 10 . Currently, you can protect all of your Azure VMs with Azure Site Recovery, the only limitation is that you can enable replication in batches of 10 VMs at the time This is in order to maintain replication bandwidth and minimize the impact of the cache storage and target store accounts utilization during the initial replication process. Ex: You have 15 Azure virtual machines. You could protect all of them in 2 batches. First batch of 10 VMs (simultaneously) and then a second batch for the remaining 5 VMs.
More info:
IP address retention for Azure virtual machine failover: https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-retain-ip-azure-vm-failover
Azure to Azure replication architecture: https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-architecture
About networking in Azure to Azure replication: https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-about-networking
Create and customize recovery plans: https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-create-recovery-plans
Set up disaster recovery for Azure VMs to a secondary Azure region: https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-tutorial-enable-replication
Run a disaster recovery drill for Azure VMs to a secondary Azure region: https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-tutorial-dr-drill
Fail over and fail back Azure VMs between Azure regions: https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-tutorial-failover-failback
Kindly let us know if the above helps or you need further assistance on this issue.
If I go into the Azure portal and go to a SQL Azure db and click on Geo-Replication I can select another data center to have a secondary database in. I can configure this as "readable." With that done, do I automatically get failover?
So for example, if my primary db is in Central US and I configure Geo-Replication to US East 2, will anything automatically failover my db to US East 2 if there is an error in Central US? Or do i have to initiate the failover through the portal or some code/monitoring solution? And would i have to update my connection string or does the azure infrastructure manage this for me?
I've reviewed a few docs below about this but looking for some more input:
- https://azure.microsoft.com/en-us/documentation/articles/sql-database-designing-cloud-solutions-for-disaster-recovery/?rnd=1
- https://azure.microsoft.com/en-us/documentation/articles/sql-database-geo-replication-failover-portal/
- https://azure.microsoft.com/en-us/documentation/articles/sql-database-geo-replication-overview/
https://azure.microsoft.com/en-us/documentation/articles/sql-database-geo-replication-overview/
do i have to initiate the failover through the portal or some
code/monitoring solution?
Yes, you have to initiate the fail over explicitly. There is no automatic failover in case the primary goes offline.
would i have to update my connection string or does the azure
infrastructure manage this for me?
You would have to update connection string explicitly as well.
FailOver and DR drill sections of this link should provide necessary info, it also talks about keeping firewall rules and users in sync between primary and secondary : https://azure.microsoft.com/en-us/blog/spotlight-on-new-capabilities-of-azure-sql-database-geo-replication/