We are setting up Azure Site Recovery for a VmWare environment and we've been through the process of setting up the configuration server and the site recovery wizard, but we're a bit stuck at selecting the VMs to replicate. When we select more than 10 it comes with an error "You can select a maximum of 10 items to protect"?
We've built the server using the following specs which according to Microsoft should be enough to accommodate 100 servers.
Spec: 8vCPU, 16GB Memory
Is there a limitation I have missed?
The links I have followed are:
https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-plan-capacity-vmware
https://learn.microsoft.com/en-us/azure/site-recovery/vmware-physical-large-deployment
You can have maximum of 100 server / CS but at a time you can't select more then 10 . Currently, you can protect all of your Azure VMs with Azure Site Recovery, the only limitation is that you can enable replication in batches of 10 VMs at the time This is in order to maintain replication bandwidth and minimize the impact of the cache storage and target store accounts utilization during the initial replication process. Ex: You have 15 Azure virtual machines. You could protect all of them in 2 batches. First batch of 10 VMs (simultaneously) and then a second batch for the remaining 5 VMs.
More info:
IP address retention for Azure virtual machine failover: https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-retain-ip-azure-vm-failover
Azure to Azure replication architecture: https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-architecture
About networking in Azure to Azure replication: https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-about-networking
Create and customize recovery plans: https://learn.microsoft.com/en-us/azure/site-recovery/site-recovery-create-recovery-plans
Set up disaster recovery for Azure VMs to a secondary Azure region: https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-tutorial-enable-replication
Run a disaster recovery drill for Azure VMs to a secondary Azure region: https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-tutorial-dr-drill
Fail over and fail back Azure VMs between Azure regions: https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-tutorial-failover-failback
Kindly let us know if the above helps or you need further assistance on this issue.
Related
The scenario is as follows:
In company premise, there is a network that consists few machines.
The company has an Azure subscription.
Requirement:
To monitor the company's Network/Machines via Azure
If the company resource goes beyond a threshold limit then trigger alerts. Example, network bandwidth consumption, machine CPU/Memory usage, etc.
When such alerts occur then spin up new virtual machines or VM scale sets in Azure to handle the load.
The purpose is if the machines in on-prem goes above threshold limit then automatically provision VMs in Azure, as there are only few on-prem machines.
Please guide how to implement these use cases?
your question is a little confusing. You mention machines on premises and using Azure to monitor them. You can monitor on premises VMs using Azure but then you mention provisioning new Azure VMs via Scale Sets.
I'm not 100% where your workload is but assuming it is in Azure then if you are using VM Scale Sets it's very easy to scale in and out based on resource utilisation.
This can be configured as described here: https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-autoscale-portal
If we want to failover Replicated VM in Azure using Azure Site Recovery.
Can we replicate VMs to a different subscription ?
Eg. When configuring ASR - Disaster recovery I gave subscription name 'ABC' for replication to happen.
At the time of failover I want VM to failover to 'PQR' subscription and not 'ABC' where replication was happening till now
Have any one tried this with PowerShell ?
#DBA Admin The Subscription cannot be changed once selected. However, Azure site recovery does offer "Cross-subscription disaster recovery for Azure virtual machines"
I have few (around 10) Windows Services on my existing environment. We are planning to migrate to Azure with the following.
Host our database on Azure SQL Database.
Install all the 10 Windows Services in a Azure Virtual Machine. Please note that these Windows Services does bulk inserts into the Azure SQL databases.
Take 2 instances of VM (specified in #2 above) and configure them in an Availability Set to avail the SLA.
I have two questions.
Do I need to install all my 10 Services to both the VMs?
Will that NOT be reduntant running the Windows Services in both the VMs? So, the Bulk Inserts will be duplicated to the Azure SQL Databases.
Please let me know if I am thinking in the right direction or are there any alternate methods (like Worker Roles) of utilizing the existing Windows Services on Azure with minimum or no changes?
It looks like, I got an answer to my question. When there are two VMs in a given Availability Set, ONLY one will be up and running. The other VM will come into picture only when the primary VM is down.
Thanks,
Prawin
If you are to take advantage of Azures SLA you will need to have at least 2 VM's (from within the same family) in an availability set. The SLA covers the VM's in the availability set NOT what you are running on the OS. For example if you have all services running on one instance and that box goes down, you lose those services till the box recycles. Microsoft is still covered on their SLA because at least one of the VM's in the availability set is available.
I am trying to change the Virtual machine size from - 8 Cores, 14 GB to A 6 - 4 core, 28 GB for one of of my MSSQL Azure IaaS server.
I am getting the following error:
Unable to upgrade the deployment. The requested VM size may not be
available in the resources supporting the existing deployment. Please
try again later, try with a smaller VM size or smaller number of role
instances, or create a deployment under an empty hosted service with a
new affinity group or no affinity group binding. The long running
operation tracking ID was: 1d8145d1977877978d1d8dffdd045d83.
I understand that there is a limitation on how much one can get from one subscription. However, this is the live server and I have another 4 servers running under same subscription. Is there any way I can move this Virtual machine from one subscription to an another?
Otherwise, what is the right approach on increasing the size of this server?
Please advise the earliest.
I got the answer from Support as :
When customer initially deployed service it got deployed under the
cluster which does not support high memory VM's. Since customer is
having deployment under the hosted service it cannot be
pinned/migrated to a cluster which supports A6 or higher VM size. This
is a by design behaviour as of now. Unfortunately, the only way
customer can deploy a A6 VM is to delete and recreate deployment with
A6 size under the given hosted service. When customer tries to create
it, then he/she will be allocated a cluster which supports A6 or
higher VM size.
We have SQL server VM.
We were facing following problems with it on 26/09/2013.
-Not able to take its remote control
-Status was running , End point was perfect
-Restarted but doesnt worked
We have changed the VM size from small to medium as similer thread suggested, It worked.
1 ) Can you advise what would be impacts of reducing size of this SQL server VM ?
2 ) How this kind of problem can be handled at monitoring dashboard for VM? i.e. azure can alert/mail when VM is out of reach!! ?
Azure recommends a minimum of medium VM size for most of their SQL Server images (if you happen to be using one of their images). Depending on the version of SQL server you're using, you may have issues with the low RAM on a small VM as your DB's grow.
As far as monitoring, in the azure portal, under Management Services you can set up alerts for your VM which will email you if any of your conditions are triggered.