Article number
000004182
Affected Versions
7.5 Update 3
7.5 Update 2
7.5 Update 1
7.5 Patch 1
7.5
7.0 Update 3
7.0 Update 2 Patch 2
7.0 Update 2 Patch 1
7.0 Update 2
7.0 Update 1 Patch 1
7.0 Update 1
8.0
8.0 Update 1
8.0 Update 1 Patch 1
8.0 Update 2
8.5
8.0 Update 3
8.5 Update 1
8.0 Update 4
8.5 Update 2
7.5 Update 4 Patch 2
8.0 Update 4 Patch 1
Source Hypervisor
Azure
Target Hypervisor
Azure

Problem with Reflection Collection Failures in Azure

Viewed 93 times

Summary

An administrator may notice reflection collection failures, leading to an array of GUI reporting issues, due to the size of the environment and hitting Azure API request limits.

Root Cause

Best practices for Zerto deployments in Azure include having a maximum of 8 ZCAs per Azure subscription. Larger environments have many ZCAs using the same Azure subscription, unaware of one another. When the reflection collection interval is 1 minute (default), Zerto hits an Azure API request limit on the subscription. Starting in Zerto version 7.0 Update 1, there is a configuration change available to increase the interval so as to avoid the API request limit in Azure.

Symptoms

In large-scale Zerto deployments in Azure, customers may experience reflection collection issues pertaining to API request limits, as seen in the ZVM log snippet below:

AzureReflectionProxy,MoveNext,"Failed to get reflection data for region Identifier=<region> in subscription <subscription_GUID>. Error message = Error Message = Operation 'Microsoft.Compute/virtualMachines/read' failed as server encountered too many requests. Please try after '900' seconds. Tracking Id is '<GUID>'., Response = {""error"":{""code"":""ResourceCollectionRequestsThrottled"",""message"":""Operation 'Microsoft.Compute/virtualMachines/read' failed as server encountered too many requests. Please try after '900' seconds. Tracking Id is '<GUID>'.""}}, Error Code = 429, Reason = ..","Microsoft.Rest.Azure.CloudException Void MoveNext() Microsoft.Rest.Azure.CloudException: Operation 'Microsoft.Compute/virtualMachines/read' failed as server encountered too many requests. Please try after '900' seconds. Tracking Id is '<GUID>'.

Symptoms include GUI related issues such as missing networks in a VPG configuration.

Solution

To resolve the issue, kindly engage Zerto Support to apply a configuration change to avoid hitting the API limit further.