The Azure Site Recovery error code 95613 indicates a capacity or quota limitation within your Azure subscription for the target region

 

  • 161025
  • There aren't sufficient cores available to failover all virtual machines in subscription '5e942c09-acdb-4908-b444-32344cb34fd6' and location 'centralindia'. Current core limit (subscription): 50. Required cores: 108. Required cores may also include a few cores used by temporary virtual machines that are created during failover. These temporary virtual machines are deleted before completion of failover.
  • Delete some of virtual machines or contact Azure support to increase the quota for cores. Go to http://aka.ms/getazuresupport and open a new support request with issue type: Quota
The Azure Site Recovery error code 95613 indicates a capacity or quota limitation within your Azure subscription for the target region. Specifically, Azure is unable to create the necessary Virtual Machines (VMs) in the specified target location due to a lack of available resources or insufficient quota for the required VM sizes.
Possible Causes
  • Subscription Disabled/Insufficient Quota: Your Azure subscription is not enabled, or lacks the sufficient quota, to create any VMs or specific VM sizes in the chosen target region.
  • No Suitable VM Size: Azure Site Recovery could not find a suitable target VM size that matches the source VM's configuration (e.g., Network Interface Card (NIC) count) within the allowed quota for your subscription in the target location.
Recommended Actions
To resolve this error, follow these steps:
  • Contact Azure Support for Quota Increase: The primary solution is to raise a support request to increase the quota for the required VM sizes in the target location.
    • Navigate to the Azure portal and create a technical support ticket.
    • Specify that you need an increase in the core count or VM family size quota in the affected region.
    • Reference the error code and the necessary VM sizes to expedite the process.
  • Select an Alternate Target Location: If increasing the quota is not feasible or time-sensitive, you can disable replication to the current location and enable it to a different Azure region where your subscription has sufficient quota and capacity to create the required VMs.

Comments

Post a Comment

Popular posts from this blog

How to install VNX Launcher that has embedded java and Firefox

Image
  Alternative for Adobe Flash Player to access Unisphere. Symptoms VNXe Unisphere in older OE revisions is not accessible after December 31, 2020. The Adobe Flash Player plug-in is no longer supported in browsers. VNXe Unisphere used to require a browser with the Flash Player plug-in. Cause When VNXe is running an older OE revision, Adobe Flash Player is required by Unisphere. Refer: https://elabnavigator.emc.com/vault/pdf/EMC_VNXe_ESSM.pdf?key=1588743011568 Adobe has expired Flash Player as of December 31, 2020.   Details: https://www.adobe.com/products/flashplayer/end-of-life.html Resolution Newer VNXe OE revisions support HTML5. Once the VNXe is upgraded, Unisphere will work. Since December 31, 2020 browsers do not support Adobe Flash Player. Most browsers support HTML5. VNXe Unisphere must also support HTML5 in order to use VNXe Unisphere. HTML5 support is delivered in these VNXe revisions:       ...
Read more

DHCP FAILED APIPA IS USED

Image
Hi to all, In a Cisco packet tracer while i am trying to connect the dhcp server to pc it will getting the error like dhcp failed. APIPA is being used. For this issues this is also one reason.dhcp is not configured correctly. If we create a  vlan's in the switch's and we configured dhcp server in the layer 3 switch or layer 2 switch or in router. VLAN 10 NAME SALES VLAN 20 NAME DATA We created two vlan's now creating dhcp server for that  Switch(config)#ip dhcp pool name sales (should be the vlan name. not any other name.) Switch(Dhcp-config)#network 192.168.10.0 255.255.255.0  Switch(dhcp-config)#default-router 192.168.10.1 Switch(dhcp-config)#exit Swithc(config)#ip dhcp pool name data Switch(dhcp-config)#network 192.168.20.0 255.255.255.0 Switch(dhcp-config)#default-router 192.168.20.1 Switch(dhcp-config)#exit
Read more

Zabbix Server is not working: the information dispaly may not be current

Image
  Details  Cannot display item queue. Connection to Zabbix server "localhost:10051" refused. Possible reasons: 1. Incorrect "NodeAddress" or "ListenPort" in the "zabbix_server.conf" or server IP/DNS override in the "zabbix.conf.php"; 2. Security environment (for example, SELinux) is blocking the connection; 3. Zabbix server daemon not running; 4. Firewall is blocking TCP connection. Connection refused Observation:- In Centos 9 [root@nmtool ~]# systemctl status zabbix-server.service ● zabbix-server.service - Zabbix Server      Loaded: loaded (/usr/lib/systemd/system/zabbix-server.service; enabled; vendor preset: d>     Active: activating (auto-restart) (Result: exit-code) since Fri 2023-02-03 10:36:52 IST;>    Process: 57289 ExecStart=/usr/sbin/zabbix_server -c $CONFFILE (code=exited, status=0/SUCC>    Process: 57295 ExecStop=/bin/kill -SIGTERM $MAINPID (code=exited, status=1/FAILURE)    Main PID: 57291 (cod...
Read more