Support for High Churn on Azure Seite Recovery replicated VM

[viewegchris]

Is there an existing issue for this?

• I have searched the existing issues

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.

Description

Azure added support for High Churn replication on Azure Site Recovery Vault. This allows to replicate VMs with high data rates as well. The new feature requires the use of Premium_LRS Storage Accounts.

New or Affected Resource(s)/Data Source(s)

azurerm_site_recovery_replicated_vm

Potential Terraform Configuration

resource "azurerm_site_recovery_replicated_vm" "replicated_vm" {
  name                                      = "example-vm"
  recovery_vault_name                       = "recoveryvault01"
  resource_group_name                       = "z-ach-a9999-pr01-01-asr"
  recovery_replication_policy_id            = data.azurerm_site_recovery_replication_policy.policy.id
  source_vm_id                              = module.replicated_vm.virtual_machine_id
  source_recovery_fabric_name               = data.azurerm_site_recovery_fabric.fabric.name
  source_recovery_protection_container_name = data.azurerm_site_recovery_protection_container.primary.name
  target_zone                               = "3"
  target_resource_group_id                  = "/subscriptions/xxx/resourceGroups/z-ach-a9999-pr01-ns1-01-asr"
  target_recovery_fabric_id                 = data.azurerm_site_recovery_fabric.fabric.id
  target_recovery_protection_container_id   = data.azurerm_site_recovery_protection_container.secondary.id
  target_network_id                         = "/subscriptions/xxx/resourceGroups/z-ach-a9999i-pr01-01/providers/Microsoft.Network/virtualNetworks/zacha9999ipr01net01"


  #new configuration
  churn_option                       = "high" # default is "normal"
  #############

  managed_disk {
    disk_id                       = data.azurerm_managed_disk.os_disk.id
    staging_storage_account_id    = azurerm_storage_account.high_churn_test.id
    target_resource_group_id      = "/subscriptions/xxx/resourceGroups/z-ach-a9999-pr01-01-asr"
    target_disk_type              = "Premium_LRS"
    target_replica_disk_type      = "Premium_LRS"
  }

  network_interface {
    source_network_interface_id = "/subscriptions/xxx/resourceGroups/z-ach-a9999-pr01-01/providers/Microsoft.Network/networkInterfaces/examplevmnic01"
    target_subnet_name          = "asr-vms"
    target_static_ip            = "100.114.7.232"
  }

  timeouts {
    create = "8h"
    update = "8h"
    delete = "8h"
  }
}

References

https://learn.microsoft.com/en-us/azure/site-recovery/concepts-azure-to-azure-high-churn-support

[rcskosir]

@viewegchris Thank you for taking the time to open this feature request!

[FreddyAyala]

Hello there, working on a new module to implement this, do you have any news about it?

[wyattfry]

I'll be working on this issue. For the record, I believe this is the location in Azure's API docs that describe the property in question: https://learn.microsoft.com/en-us/rest/api/site-recovery/replication-protected-items/repair-replication?view=rest-site-recovery-2024-10-01&tabs=HTTP#churnoptionselected

[wyattfry]

After extensive investigation and experimenting, I've been unable find a way to manage ChurnOption via the Azure API. I opened an issue on the Azure API Spec repo: Azure/azure-rest-api-specs#32027
As well as opened a ticket through Azure that is being investigated.

[wyattfry]

According to the Microsoft Azure support representative, the churn option will be made available in both the GET and CREATE endpoints for replication protected items in a future version of the Azure API.

[wyattfry]

According to MS rep:

About the ETA on new version, hopefully we should have API updated by Feb end.

To set the churnoption, we need to use PATCH call -

PATCH https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.RecoveryServices/vaults/{resourceName}/replicationFabrics/{fabricName}/replicationProtectionContainers/{protectionContainerName}/replicationProtectedItems/{replicatedProtectedItemName}?api-version=2024-10-01

Content-Type: application/json
Authorization: Bearer {accessToken}
{
  "properties": {
    "providerSpecificDetails": {
      "a2aReplicationDetails": {
        "churnOptionSelected": "YourChurnOption"
      }
    }
  }
}
CREATE - [Replication Protected Items - Create - REST API (Azure Recovery Services - Site Recovery) | Microsoft Learn](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Frest%2Fapi%2Fsite-recovery%2Freplication-protected-items%2Fcreate%3Fview%3Drest-site-recovery-2024-10-01%26tabs%3DHTTP&data=05%7C02%7Csupportmail7%40microsoft.com%7Cc575c819a6034d25841e08dd4235ca83%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638739520981429351%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=eYqLXihQeu6U5P%2FyBOYbkYNdP1575Y7faLC0yDsjsYk%3D&reserved=0)

UPDATE - [Replication Protected Items - Update - REST API (Azure Recovery Services - Site Recovery) | Microsoft Learn](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Flearn.microsoft.com%2Fen-us%2Frest%2Fapi%2Fsite-recovery%2Freplication-protected-items%2Fupdate%3Fview%3Drest-site-recovery-2024-10-01%26tabs%3DHTTP&data=05%7C02%7Csupportmail7%40microsoft.com%7Cc575c819a6034d25841e08dd4235ca83%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638739520981441958%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=2NTOO%2BMgVp5bk4GwGw2zP7Q0W%2FK%2FtmxAEsw2od2XhvM%3D&reserved=0)