Azure Site Recovery Failure

Kamal Kotecha 25 Reputation points

Hello

Im having issues Testing fail over on my Azure Server and also fail on test VM Backup (Restore VM)

It says i have reached my core count limit But when i check my quota I havent

Please can you help

Thanks

Kamal

👁 azure quota

👁 azure fail

  1. Manish Deshpande 7,010 Reputation points • Microsoft External Staff • Moderator

    Hello @Kamal Kotecha

    1. What is the Exact VM size of the source VM(s) and what target size/family is ASR trying to use in the failover?
    2. Are the VMs part of an Availability Set? If yes, how many VMs are in that availability set?
    3. In Subscription → Usage + quotas, what does it show for:
      • the standard DADSv5 family core/vCPU quota in ukwest (Current vs Adjustable)?
    4. Are you running Test failover or a planned failover for the same VM, and do both fail at the same prerequisite step?
    5. Do you see any other error IDs/messages besides 28075?

    Pls help me with this questions to get a clear understanding

  2. Kamal Kotecha 25 Reputation points

    Microsoft say that there is an issue with capacity. Perhaps DADSv5 are oversubscribed in UK? My reason for this is to do a Azure Site Recovery Failover TEST, and a Azure Backup Restore VM. Is there another way I can perform the tests whilst Microsoft resolve the capacity issue?

  3. Manish Deshpande 7,010 Reputation points • Microsoft External Staff • Moderator

    Hello @Kamal Kotecha

    I just wanted to kindly follow up to check if you had a chance to review my earlier response.

  4. Kamal Kotecha 25 Reputation points

    Thanks @Manish Deshpande

    1. The VM is Standard_D2ads_v5
    2. No availability sets
    3. In Subscription → Usage + quotas, what does it show for:
      • screenshot attached
    4. Just a test failover and a Test VM Restore from backup
    5. Do you see any other error IDs/messages besides 28075? - Just this error👁 azure quota4
  5. Manish Deshpande 7,010 Reputation points • Microsoft External Staff • Moderator

    Hello @Kamal Kotecha

    I just wanted to kindly follow up to check if you had a chance to review my earlier response.

Sign in to comment

5 answers

  1. The test failover failed because of a region quota limit. Your error log shows the issue clearly.

    Why It Failed Wrong region: The test runs in UK West. Zero quota: Your limit for standardDADsv5Family is 0 cores.

    Two cores needed: The test requires 2 cores. Your earlier screenshot showed your quota for UK South. That is why it looked correct.

    Search for Quotas in Azure Select Compute: Click on the Compute section.

    Filter Region: Change the region filter to UK West.

    Find VM Family: Locate Standard DADsv5 Family vCPUs. Request Increase:

    Click the pencil icon. Set Limit: Request at least 4 cores. Submit: Click save.

    Azure usually approves these requests in 5 minutes. Try the test failover again

    ------------- If this answer was helpful, kindly accept the answer ---------

    0 comments No comments
    Sign in to comment
  2. Kamal Kotecha 25 Reputation points

    Thank you @Manish Deshpande and @Andreas Baumgarten

    It looks like Microsoft were able to raise my quota limit and I have sucessfully done a test restore (both VM Restore and ASR)

    Thank you

    Kamal

    0 comments No comments
    Sign in to comment
  3. Andreas Baumgarten 132.1K Reputation points • MVP • Volunteer Moderator

    Hi @Kamal Kotecha ,

    Microsoft say that there is an issue with capacity. Perhaps DADSv5 are oversubscribed in UK? My reason for this is to do a Azure Site Recovery Failover TEST, and a Azure Backup Restore VM. Is there another way I can perform the tests whilst Microsoft resolve the capacity issue?

    If there is a capacity issue with the DADSv5 series in the target region you can try to modify the target VM SKU (choose a different VM SKU family that is compatible regarding NICs, Disks and local storage) before starting the fail-over test.

    Source: Managing target resources

    (If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

    Regards

    Andreas Baumgarten

    0 comments No comments
    Sign in to comment
  4. Andreas Baumgarten 132.1K Reputation points • MVP • Volunteer Moderator

    Hi @Kamal Kotecha ,

    based on your quota screenshot the displayed region is "UK South".

    The error message is referencing the Azure region "UK West".

    Please verify the "Total Regional vCPUs" and "DADSv5" quotas in the "UK West" region.

    Request quotas "Total Regional vCPUs" and "DADSv5" for the for "UK West" region if required

    (If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

    Regards

    Andreas Baumgarten

    1. Kamal Kotecha 25 Reputation points

      thanks

      i think something is wrong with portal, since i already have 2 vms in uk south. but its showing as 0. and it wont allow me to amend quota. i think microsoft are looking into it👁 azure quota2

      👁 azure quota3

    Sign in to comment

  5. AI answer

    The error is caused by a VM family core quota, not by the overall “Total Regional vCPUs” quota shown in the screenshot.

    Azure Site Recovery test failover must be able to create VMs of the same size (family) as the protected VM in the target region. In the error details, Site Recovery reports:

    The core count limit for family standardDADSv5Family in location ukwest was reached. Maximum limit: 0. Attempted: 2.

    So, even though the overall regional vCPU quota in UK South is not exhausted, the DADSv5 family quota in UK West is set to 0, which blocks Site Recovery from creating the test‑failover VMs.

    To fix this:

    1. In the Azure portal, go to Subscriptions → Usage + quotas for the affected subscription.
    2. Set Provider to Compute and Region to UK West (the failover region in the error message).
    3. Look for the quota entry for the standardDADSv5Family vCPUs (or similar DADSv5 family name).
    4. Submit a New quota request to increase that family’s vCPU quota to at least the number of cores required by the protected VMs (for example, 2 or more).
    5. After the quota increase is approved, rerun the Site Recovery test failover and the test VM restore.

    If multiple protected VMs use different size families, ensure that each required VM family in the target region has enough vCPU quota. Also verify that total regional cores in the target subscription are sufficient for all failover VMs, as failovers will fail if available cores do not meet the required count.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.
Sign in to answer

Your answer