Site Recovery
Microsoft Azure Site Recovery Manager helps you automate protection and orchestrate recovery for your private clouds. In case of a disaster, users can initiate a recovery plan failover that can recover the virtual machines on the target site in orderly manner.
-
Windows Azure Support for Windows Server Failover Cluster (WSFC)
Windows Server Failover Cluster (WSFC) is a state of the art HA technology for on premise world. It would be great to have support on Windows Azure, and specially to have support for SHARE DISKS. By supporting WSFC, Windows Azure would be the first IaaS platform that supports application HA!!
222 votesWe are working to understand the requirements of this feature and deliver it. If you have any scenarios or examples that might help us take a decision kindly give a detailed comment below.
-
ASR to keep track of VM changes in target region
Issue:
VM selection logic to auto-select the VM size for failover does not automatically change when there is any change (like decommissioning of VMsize selected during protection) on target region.
Even when we manually change the Vmsize under compute and Network it shows all available and unavailable VMsizes for selections
For the VM Size selections available not warning or details is available with the billing implications for the sameRequirement:
Need a feature where there is a cycle of check done for the auto selected VM Size to see if they are available on target region and run the logic…161 votesCurrently working to understand the requirements for scenarios. Will update the thread soon
-
Replicate NSG - via ASR
Allow replication of NSG and replication or NSG rules between two NSG in Azure regions for DR.
154 votesHi, we are looking at possible improvements we can make in replication of networking components. Would be great if you can share some insights on what features you’d like us to build, by filling this survey : https://aka.ms/networkreplicationsurvey
-
Support long term retention or Backup integration
When using Azure Site Recovery from an on-prem Hyper-V host (without VMM/DPM), storing 24 hours of snapshots doesn't met business requirements for Backup.
Problem
Azure Backup and ASR can't protect the same workload (and Azure Backup doesn't protect on premise VM's)Solution(s):
Allow ASR to store long term retentionorImplement an integration into Azure Backup.
Notes: Given Azure backup DOES support backing up Azure VM's - if there was a way to schedule a backup of a test ASR VM that might work (as long as the test VM only spun up just long enough for the backup -…
102 votesInteresting requirements. We are reviewing this. Will reach out to you for more details. Please use the comments to give more examples.
-
Please increase maximum retention to 5 days or more.
Please consider the following scenario:
A client in the UK gets a ransomware attack on Friday 30th March. The business is closed on Friday 30th (bank Holiday), Sat-Sun (weekend) and Monday 2nd (bank holiday). The IT Team return on Tuesday morning to find that the 24 hour of retention point are also all encrypted by the ransomware attack. If the client was only using premium storage then this would be the case even even there was not an extended bank holiday weekend. Microsoft must trust their partners who engage with real customers and deal with real scenarios in the real…
97 votesThe ransomware scenario is protected by backup. Currently we are working to understand other reasons for this requirement
-
Reporting for ASR
It would be very useful to be able to generate a monthly report on the warnings and failures etc.. that ASR generates.
Number of critical alerts
Alerts by server
Alerts by typeNumber of warnings
Warnings by server
Warning by typeIf possible, a (probable) reason for each alert
1. The RPO being breached. (We set our RPO to a value less than agreed for the project so that we can flag any issues before they breach the actual RPO)
2. Network/Connectivity/Maintenance (Updates/hardware replacment/failures)
3. Disk resize.
4. Replication services stopping/not starting correctly
5. Conflicts during periods of high activity79 votesCurrently working to understand the requirements for scenarios. Will update the thread soon.
-
Support for multiple IP's on NIC
Support for multiple IP's on NIC using ASR.
74 votesCurrently working to understand the requirements for scenarios. Will update the thread soon
-
Support for Linux VMs on Hyper-V with a static IP address
The current version of ASR will protect a Generation 1 VM running Linux, but if the guest operating system is using a static IP address (more than likely if it's a server) then when the protected VM is failed over in to Azure, the network interface is not reconfigured to support the DHCP requirements for the Azure Resource Manager Network Interface.
This has the effect that the VM's networking stack never initialises properly and the failover cannot complete successfully.
From the same environment, a VM running Windows with a static IP is reconfigured correctly during the failover process and the…
52 votesCurrently working to understand the requirements for scenarios. Will update the thread soon.
-
Ability to define subnet & IP address for Test Failovers
Test failover is an important tool to ensure that all VM configuration is done properly. It is a dress rehearsal for real DR. We need the identical features for Test failover as we do for planned/unplanned failover. However as of now we can only select VNET for TFO while we can select subnet and even define IP for a VM for planned/unplanned failover. Similarly we should be able to define recovery point.
46 votesCurrently working to understand the requirements for scenarios. Will update the thread soon
-
Allow access to preserve D:\ Drive during migration
Problem
1. Azure reserves D:\ for volatile storage
2. It is very common for on-prem server infrastructure to use this drive letter for application installs etc
3. When migrating a machine to Azure, the D:\ drive letter is not preserved
4. Application breaks after migration since it is now located at E:\ instead of D:\Workaround
Use DISKPART on the source machine to set SAN POLICY=ONLINEALL, Azure will then allocate the next available drive letter for volatile storage, therefore preserving the D:\ assignment.How to improve the Azure Site Recovery Service
Have this as an option when configuring protection for…32 votesSince Agent is installed only in Vmware scenarios – this is possible only in that. Would that be enough? Please use the comments to let us know
1. Is Manual workaround not enough?
2. When we come back to On-prem – would you expect it to be reset? -
Failback to on-premise Hyper-V host after Failover from Physical to Azure
Most of Microsoft customers use Hyper-V and Physical servers. These customer expect failing-back to Hyper-V for their physical servers after they are failed-over to Azure.
30 votesWe are looking into this ask and working wit some customers to give us more data. Kindly give the needs around why you need to failback to Physical and not virtual machines instead.
Please give your feedback in comments so that we can address the ask.
-
Support for localized OS configuration on the source server in Physical/VM-to-VMware scenario
Currently, ASR 'between VMware sites' scenario doesn't support Non-English OS on protected servers. A Customer is looking for protecting non-English language primarily on Windows but also Redhat and Oracle Linux from the sites in Germany, Italy and France.
27 votesCurrently working to understand the requirements for scenarios. Will update the thread soon
-
Replication from Azure to on premises
In a disaster recovery/business continuity situation it would be helpful to have a replicated version of server on premises should the worst happen such as the data centre becoming inaccessible or the internet lines from our business being down.
25 votesThank you for the feedbacks. Ensure that the experience requirements are mentioned in the comments.
-
Enable replication to Standard storage account and failover to SSD with VMWare to Azure
Would it be possible for you to a feature where you replicate the VMs into a standard storage account and when a failover (or test failover) happens we can start the VMs using Premium storage.
25 votesCurrently working to understand the requirements for scenarios. Will update the thread soon
-
Provide an option to replicate from Azure to local site
Similar to how local servers replicate periodically up to Azure, I'd like the same option to exist when the servers are running in Azure. I'd like the Azure VMs to be able to replicate down to the local site (as opposed to having to copy the entire contents, then commit the failback).
20 votesWe are working with Azure on enabling this.
Kindly give us more requirements or your experiences with current failback from Azure so that we address them holistically. -
Provide Recovery Services for the North Central US Region
Currently there is no backup vault for the North Central US Region. Please make this available!
16 votesThank you for your feedback – we are looking into enabling ASR in as many GEOs as possible – very soon.
Will update you when we have release dates. -
Protect encrypted volumes
Ability to protect volumes that are encrypted or protected by BitLocker will be useful
15 votesWe are looking into this requirement. If you have any more requirements around this – kindly let us know via the comments.
-
Retain public IP support in ASR for failover to Azure (Cloud Services)
To comply with security reason, customers need to use same public IP for each failover to Azure using ASR. Currently this is not a supported scenario whereas Azure has this feature available and customers using ASR want to leverage the same Azure feature in ASR to retain the public IP which helps not only to comply with security but also reducting the effort in updating the public DNS name, on-premises connectivity that rely on the cloud services public IP address.
12 votesWe are already working on this ask. Stay tuned.
-
Use Azure site Recovery between Two Stacks
Use Azure site recovery for disaster recovery puposes between two Azure Stacks deployements
10 votesMoved to Site Recovery forum.
-
Support Hyper-V 2012 without R2 for On-Premises Hyper-V Site and Azure
Our shop would love to use azure site recovery, but there is no chance of an R2 Hyper-V update.
So there is no chance to move some of our workloads permanently to azure with ASR.
10 votesThank you for your feedback. We are already looking into this ask. Stay tuned.
- Don't see your idea?