I am trying to migrate a VM in Southeast Asia to Western Europe
After defining the source in the Enable Replication Section, I am not able to select the virtual machine.
Source Details
Select Virtual Machine section shows the VM grayed out.
My account has Owner, Site Recovery Contributor, Site Recovery Operator, Site Recovery Reader and Virtual Machine Contributor roles.
Currently, native replication of Azure VMs using managed disks are not supported.
You can use "Physical to Azure" option in this document to migrate VMs with managed disks.
More details bout Migrate Azure IaaS virtual machines between Azure regions with Azure Site Recovery , you can refer to this document.
Within Azure Site Recovery, are you running an unplanned failover? Per Microsoft's documentation your VM has to meet these requirements to be used. Once you've confirmed that, confirm that you meed the pre-requisites for failover (there is a link at the bottom of the MS requirements document.)
If all those are met, then go to Replicated Items, select your VM, choose the More menu, then Failover, in the Failover dialog box there is a From box, your VM should be an option in that box. Then follow the steps for a failover per Microsoft.
There are other sources for using Azure failover that may be informative.
Related
I currently have an app running on Azure VMs and the outbound traffic using UDR is funneled through Azure Firewall.
I understand the VMs can be replicated to a secondary region using Azure but not sure how to handle the networking components. With Azure Firewall being a PaaS service, do I have to create an Azure Firewall instance in the secondary region at the time of failover? Same concern with UDRs.
We can handle/protect the networking components using below following steps
I have created the vm with recovery vaults
After creating enabled the recovery vaults and I am able to see my recovery site is healthy
Open the replica item in the over view clicked on test failure before beginning the failure I shutdown the machine and the operation will be started and processed successfully
To finish the failure click on Commit to complete the failure
To reprotect the VM on the keyvault overview click on Re-Protect button
Verify the replication direction and review the target settings for the regions by click on ok to start the reprotect process
Use this Microsoft Document for more information
For setting up for URD Refer this document
In Azure there are 2 options available to create virtual machines.
A. normal VM
B. Classic VM
Does anybody know what is the difference between both option? When do we use one over other?
Short answer to your question is Normal VM or Virtual Machines is the new way of deploying your Virtual Machines whereas Classic VM or Virtual Machines (Classic) is the old way of deploying them. Azure is pushing towards the new way of deploying resources so the recommendation would be to use it instead of old way. However please keep in mind that there're some features which are available in the old way that have not been ported on to the new way so you just have to compare the features offered and only if something that you need is not available in new way, you use the old way.
Now comes the long answer :)
Essentially there's a REST API using which you interact with Azure Infrastructure.
When Azure started out, this API was called Service Management API (SMAPI) which served its purpose quite well at that time (and to some extent today). However as Azure grew, so does the requirements of users and that's where SMAPI was found limiting. A good example is access control. In SMAPI, there was access control but it was more like all-or-none kind of access control. It lacked the granularity asked by users.
Instead of patching SMAPI to meet user's requirement, Azure team decided to rewrite the entire API which was much simpler, more robust and feature rich. This API is called Azure Resource Manager API (ARM). ARM has many features that are not there in SMAPI (my personal favorite is Role-based access control - RBAC).
If you have noticed that there are two Azure portals today - https://manage.windowsazure.com (old) and https://portal.azure.com (new). Old portal supports SMAPI whereas new portal supports ARM. In order to surface resources created via old portal into new portal (so that you can have a unified experience), Azure team ended up creating a resource provider for old stuff and their names will always end with (Classic) so you will see Virtual Machines (Classic), Storage Accounts (Classic) etc. So the resources you create in old portal can be seen in the new portal (provided the new portal supports them) but any resources you create in the new portal using ARM are not shown in the old portal.
The Azure Virtual Machine (classic) is based on the old Azure Service Management Model (ASM). Which revolved around the concept of a cloud service. Everything was contained inside a cloud service, and that was the gateway to the internet. While it is still used (extensively) Azure is now moving over to the Azure Resource Management Model (ARM).
ARM uses the concept of declarative templates to configure an entire solution (rather than individual components) So you can create an entire Sharepoint stack, rather than just a singular machine.
ARM also has a much more logical approach to networking. Instead of having a monolithic VM in an obscure cloud service. You have a VM, that you attach a network card to. You can then put the Network card into a VNet and attach a public IP (if you need one)
Unless you have a compelling reason to use ASM (classic) You should create your solution using ARM. As this is the MS recommendation going forward (todo find a link to that) It also means that you can create templates for your deployments, so you can have a repeatable solution.
On the negative, the old portal manage.windowsazure.com can not manage anything that is deployed using ARM, and there are still parts of ASM that haven't been migrated over to ARM yet. For instance you cannot configure Azure VM backup, since Azure backup is ASM and it can't 'see' ARM VMs
It very largely depends on your circumstances though, what it is you are planning for, the method you are going to deploy with. If you are just looking to stand a machine up to do a single task, it makes very little difference. If you are looking to deploy into an environment that will have some concepts of DevOps going forward, then ARM is the way to go.
The one big differences is for resource management. For that new version is called Azure Resource Manager VM (ARM VM).
ARM VM is better in terms of;
Classic VM must be tied with Cloud Service, and Cloud Service consumes resource limitation and not-so-flexible network configuration.
ARM VM is managed under Azure Resource Manager (ARM) which can be organized with/without other Azure services. ARM is like a folder of Azure services, and it gives you more fine-grained resource management.
Classic VM can be migrated to ARM VM version, but you have to afford service downtime. To migrate from classic VM, read the official article: Considerations for Virtual Machines.
Azure provides two deploy models now: Azure Resource Manager(Normal) and Azure Service Management(Classic) and some important considerations you should care when working Virtual Machines.
Virtual machines deployed with the classic deployment model cannot be included in a virtual network deployed with Resource Manager.
Virtual machines deployed with the Resource Manager deployment model must be included in a virtual network.
Virtual machines deployed with the classic deployment model don't have to be included in a virtual network.
I see some Microsoft Azure services are marked as (classic) in Azure Portal, such as OS images, VMs, and Storage account.
Does it mean they're planned to deprecated or what? Where to find the modern services correspond to them?
The new Azure Resource Manager (which uses a new API) spins up resources in a slightly different way than the old API's did. The classic API stack is still operational, but you'll see those resources show up in the new (Ibiza) portal as classic, including virtual machines, vm images, storage, OS disks, reserved IP addresses, and virtual networks (based on what I can see in the portal right now; I don't have insight into what will show up or be removed in the future).
Resource Manager: This is the newest deployment model for Azure resources. Most newer resources already support this deployment model and eventually all resources will.
Classic: This model is supported by most existing Azure resources today. New resources added to Azure will not support this model.
https://azure.microsoft.com/en-gb/documentation/articles/azure-classic-rm/
I just created a windows 2012 datacenter VM in azure, however I notice in management portal that Azure also created a cloud service with same name. Is this normal?I don't want to be double charged..
This is normal. You are not charged for Cloud Services. You're only charged for actual VM's deployed in them. Cloud Service is just a record in a database and a concept that is used to group Azure resources together
The VM Role preview in Windows Azure ends on May 31, 2013 and Microsoft urges to migrate VM Roles to "proper" Virtual Machines that are in General Availability as described here:
http://msdn.microsoft.com/library/3dae01d2-2397-47ed-a134-f9ffe58a9b52.aspx
But how do I know which of the Virtual Machines running in Azure are VM Roles and which are Windows Azure Virtual Machines?
I wrote a blog post that may help: Do I have VM Roles that I should migrate? at http://blogs.msdn.com/b/benjguin/archive/2013/04/19/do-i-have-vm-roles-that-i-should-migrate.aspx
You probably see it easily in the portal, but an easy check could be to store something on your disk and stop/delete and recreate the machine. If the file is no longer there, that means it's a VM role.
I also believe you cannot see VMRole in the new portal (and only in the old portal)