Azure Site Recovery for Migration Date: 08/05/2016

Index Page Numbers

Migration Agenda and Challenges 2-3

Availability on Demand 3-5

Why Migrate to Azure 5-7

Azure Site recovery paths 7-8

Migrating VMware VMs and Physical Machines

And Architecture 8-13

System requirements for process server, Configuration server

& Master Target Server 13-13

VMware machines migration demo 13-30

Hyper-V to Azure Migration Architecture 31-32

Azure to Azure Migration 33-37

1|Page
Azure Site Recovery for Migration Date: 08/05/2016

2|Page
Azure Site Recovery for Migration Date: 08/05/2016

What we hear from customers now a days are:

Microsoft come up with the Availability on Demand

3|Page
Azure Site Recovery for Migration Date: 08/05/2016

Under the Microsoft On demand umbrella, we have following in plan.

Recovery and Cloud Backup are known stuff to us.

4|Page
Azure Site Recovery for Migration Date: 08/05/2016

Azure site recovery is pitched as Disaster recovery now a day.

Recovery is on availability on Demand helps us in disaster recovery, migration and failover scenarios like
Either on Azure or on premises to fall back.

DevTest is very helpful as we need to test the right patches being installed before entering into
production environment.

Cloud bursting: where as in you can scale up your environment as you need to but this is Nish
technology as of now.

Analytics and reporting: where as in you dont want to run deep analysis on your production machines
then you can choose analytics and reporting to analyze some applications and reporting and then you
can discard them. Again this is also Nish technology.

Availability on Demand is a suite but today we are going to talk about Azure Site Recovery in
Migrations.

Why migrate to Azure?

5|Page
Azure Site Recovery for Migration Date: 08/05/2016

Migrate workloads to Azure: Key Considerations are

1. While migrating onto azure, it will not disturb the number of users connected to production
machine
2. We need to test the application in Azure before we migrate.
3. Replicate data to azure only once, and use it for both Migration and recovery.

6|Page
Azure Site Recovery for Migration Date: 08/05/2016

Azure site recovery and migration paths which we are looking for:

1. Migrating virtual machines from Hyper-V machines

7|Page
Azure Site Recovery for Migration Date: 08/05/2016

2. VMware workload and upload onto Azure

Lets get into Details:

1. Migrating VMware VMs and Physical Machines:

Architectural diagram as below:

In order to start the migration there should be something on the VMware vms or physical machines to
help in migration onto Azure. That is Mobility Service

Mobility Service: is an in guest and light weight agent and this is sitting inside your VMware vms or
physical machine. It captures all data writes from memory and replicate them onto Azure.

8|Page
Azure Site Recovery for Migration Date: 08/05/2016

The Mobility service is capturing writes in memory and replicating them to Azure. The Key point is, once
you have some amount of replication done for what we called initial replication. Mobility service works
based on delta, so as there are changes it captures delta values and send them off onto azure.

Initial replication is the time which depends on your machine size and the bandwidth you have between
yours on premise to Azure.

If You dont want to send the data without caching, compression and encryption onto Azure hence we
introduced a service called, Process Server.

Process server is the one which holds the complete Caching, compression and encryption from Mobility
service agent. Remember Mobility service agent is a light weight agent which is sitting inside your
machine. Process server is the one which make sure there is no IO impact on the existing production
machine while its in the process of the migration.

9|Page
Azure Site Recovery for Migration Date: 08/05/2016

Now we have things ready on premises and we need something to handle the Process server requests in
Azure which is called Master Target Server.

Master Target Server will handle the traffic from process server.

10 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

In Azure we go with the active-passive migration, where as in your machine should be active and Master
Target server write the data onto vhds which are attached to the Master Target Server. Only we issue
migration or test cases then will spin off the actual virtual machine.

Master Target server is based on the operating system which you choose, if we are handling windows
Migrations then we need to have Windows Master Target Server, if Linux then should have Linux Master
Target Server.

Now the last component which is Config Server which is the management server for the migration and
all the servers: Mobility service, Process server, Master Target server need to be register under Config
server.

Migration Accelerator service has been shut down and all its features been combined in the Azure Site
Recovery.

11 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

Here are some pre-requisites for Process server, Target server and Config server.

12 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

Lets move onto Demo:

1. First thing which we need to create in Azure is Site Recovery Vault

Its the billing property and all your migration stuff stored here.

2. Select the region and create Site Recovery Vault.

3. Once you created the Site Recovery Vault then click on it, you would see below options.

Once you select the option Between an on-premises site with the VMware/physical servers and azure

You would see below things which we need to configure:

13 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

First step, deploying the Configuration servers. Click on it and you would see below screen.

14 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

Provide Configuration Server Name

Provide Username and password

Then choose your network: you need to be careful whether you are going to use your exiting vpn
network or internet. Based on it you need to choose, for example, see below picture.

Then select the subnet and provide IP address of the configuration Server.

Once Configuration server setup has been complete, you would see it.

Next server which we need to configure is Master Target Server

15 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

Click on Master Target Server and follow the onscreen.

Selecting VM size is critical as you need to know how many disks you need based on that you need to
pick the vm size

There are A4 comes with the 16 Disks and D14 comes with the 32 Disks.

16 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

While configuring the Master Server, you need to provide the Config server information and network.

After Master Target server deployment go to Config server and click on it. You would see below similar
screen.

17 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

The next step would be Process Server, as it should be on premises and reachable to the planned
migration servers.

You can have your windows 2012 Server then Download and install process server on top of it, at the
end it will prompt you to enter Config server details in order to register with the config server.

If you look at below screen, you could see three process servers have been registered onto Config
Server.

Go to Config Server configure tab and you see whether you wanted to use VPN or None-VPN.

18 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

So far, we have configured : Config Server, Target Master Server and Process Server.

Now in order to process, we need to add Vcenter Server/ESX server.

Go to Config Server and and click on Add Vcenterserver/ESX server.

19 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

When you click on Add Vcenter Server, you need to provide below inputs:

Vcenter Server IP and Port number

Server Name

Username

Password

And Process server name.

Once that is done, you can see the Vcente server.

Now we need to enable replication:

20 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

Protection Groups: we need to create protection group in order to proceed with the migration, as the
protection groups gives the plan for your group of virtual machines.

Create a protection group as below screen says :

When you click next

21 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

Multi VM Consistency : Its the ability to consistency to failover and replicated between set of vms.

RPO : Recovery Point Object threshold

Recovery Point Retention: its similar to our azure recovery, when we migrate, Master Target server will
hold the vhd, so here it says how many hours you want to hold the vhd in.

App Consistency Frequency : Its the ability to provide consistency between your apps replicated
between Azure and on premise.

Set the parameters as per the below screen:

22 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

Once that is done, you can see it as per below screen.

23 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

If you want to see what are the jobs successed, then you can click on Jobs and see.

Now its time to add virtual machines to Protection Group which you created.

Go to protection group and click on it and it will ask you to add virtual machines.

Click on Add Virtual machines then you would get navigated to Vcenter Server which we added and it
will list the vms which are part of Vcenter Server.

24 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

Here you can select your vm and move on, let say the server which you selected doesnt have Mobility
service not installed, but when you select and move on here, it will automatically push the Mobility
service onto the vm.

25 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

Once that is done, click next and see below screen.

Please select the process server, master target server and storage account which you plan to use for
migration.

Give credentials to push the migration:

26 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

Once done, it takes 30-40 minutes and migration completes.

In the process of migration, first we need to create migration plan, usually we follow below sequence:

AD/Domain Server

SQL server

App Server

Web server

Plan it this way.

27 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

For a failover, then click on back and go and choose failover as per below screen:

When you click on Failover then you see below screen:

28 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

This kicks for VM creation and attaching disks and it going to take 30 minutes to 1 Hr time.

Summary of actions:

29 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

For Hyper-V to Azure

1. We need to install Microsoft azure recovery service agent onto Hyper-V Host and then follow
the similar process which we followed for VMware to azure.

Here are the steps:

30 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

Azure to Azure Migration Plans:

31 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

32 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

33 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

1. From the location where you want to migrate VM, there should be Process Server installed
2. Browse the VM which you want to migrate from the subscription (East Asia location)
3. Make a note of the VM IP address
4. Go to the Region where you want to transfer the vm
5. Go to protected Groups
6. Click on Add physical server
7. Provide the vm IP address
8. Give Operating system name

34 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

Then click next

35 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

Process Server, Master Target Server and Storage Account and click next.

If this doesnt have Mobility service installed, then it will install onto the machine.

For VM failover, you can navigate as per below screen.

36 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

37 | P a g e
Azure Site Recovery for Migration Date: 08/05/2016

38 | P a g e