https://docs.microsoft.com/ko-kr/azure/site-recovery/site-recovery-whats-new -> https://support.microsoft.com/help/4602881/

When enabling protection for a VM, there is no requirement to configure test failover settings.

When attempting to further customize production failover settings on a VM such as LB, PPG, etc., the Portal requires you to set test failover configurations just to save the Production changes.

In my view, if this is optional at protection it should be optional after the fact as well.

Currently, ASR does not support monitoring the connection status of multi-VM consistency; customers want the ability to monitor communication between VMs.

Debian 10 is released on July 6th, 2019 but is not on the matrix of the supported systems.
It would be nice to see a roadmap of the development. This allows for better planning.

It would be interesting to be able to backup the VMs that are replicated in Azure via ASR.
Backup and Disaster Recovery plan would be combined in the same place and in the same tool.
This would also avoid the on-premise installation of Azure Backup Server which consumes a lot of disk space.

Dell recommends 4K sector size for Windows server. ASR should support this feature. We just lost a ASR deal and going else where for remote backup.

I would love to have the option to create a replication group upfront and start replication at the moment i choose myself in stead , of push replicate button and start replicating immediately when create the replication group. Got a customer with more then 400 vm's and those need to be collected in groups upfront , and then they want to start replicating group by group but create all the groups before.

It would be really usefull to have integration for log redirection for Log Analytics. Reporting, troubleshooting and monitoring from a single pane of glass will increase the value of this solution.

Troubleshooting right now it's very difficult because of the spread of components across multiple locations.

https://theviralhindi.in/seva-sindhu-portal/

Seva Sindhu Karnataka – ಸೇವಾ ಸಿಂಧು | Seva Sindhu Driver 5000 Registration

we implemented new vCenter on our HQ and migrate all VMs to this new vCenter, after that the VMs that already replicated to Azure Site recovery is in healthy but when check VM setting on Azure Site recovery service i found the vCenter name update but the friendly name still with the old name
So i need to updated the friendly name

kiki0392

Updating this component on many hosts takes a long time. The ability to automate this process (WSUS, SCCM) would be welcome.

It would be awesome if ASR could support disks greater than 8TB, given that you can have managed disks in Azure in such sizes as 32TiB and 64TiB. If I have a workload I want to protect in azure running on disks this size i cannot use ASR.

این است که سیستم درست برئز نشده وهنگ میکند.

Enable ASR to feed Azure Advisor and notify customers when their target region is lacking the VM series capacity. The customer can see these as Recommendations in Security Center. Customers are unaware when the VM in the source cannot failover until the failover occurs and fails with an error stating "The selected VM size is not available for virtual machine...".

e-mail notification required when test failover and failover scenarios to multiple teams for azure site recovery actions. When test failover and failover time need VM location to sent multiple teams and re-protect time also we need where the VM is reprotected.

When we failback a vm the portal doesn't show which recovery plan the vm belongs to.

Hi,

To download all servers ASR status in tenant with all details (like RPO, configuration issues, Agent version, Protection status).

currently we only can choose Target virtual network when enable replication, if I have multiple subnets under the target virtual network, it should support to choose target subnet