Tag Archives: Azure Migration

Using Azure Site Recovery for Migrations (Part 2)

Posted on by
Reply

KB ID 0001514

Problem

Back in PART ONE, we setup our Azure Site Replication Server, now we create a “Replication Policy“, and perform a test failover. In addition to the pre-requisites we needed before to perform the following steps, we will also require you to create a “Storage Account” in your Azure Subscription.

Solution

Locate the Replication Vault we already created > SiteRecovery > Prepare Infrastructure > Set your requirements > OK.

I have not run the deployment planner, this is a PowerShell tool that will give you some stats on what your replication performance will be like, with your VMs and internet connection. I am simply putting “I will run it later: > OK.

Select your onsite Configuration Server > Select your vCenter/Hyper-V server > OK.

Note: I was worried about the “vCenter discovery status is NotConnected Click here to read more” Notice, but everything worked OK?

Select your Storage Account > and LAN/Subnet > OK.

Azure Create an ASR Replication Policy

Create and Associate.

Give the policy a name (accept the defaults) > OK.

Once you are “all-green” > OK.

Select Step 1: Replicate Application > Select your replication preferences > OK.

Enter the Azure ‘target VM‘ settings > OK.

Select the VM(s) that you want to replicate > OK.

Make sure an account with the correct access is chosen > OK.

OK.

Enable Replication.

Obviously, this may take some time, I left it running and checked the following day.

Replication Vault > Overview > Sire Recovery > Wait until all your replicated items are “Healthy”.

Azure SRS Perform Test Failover

Replication Vault > Replicated Items > Select your replicated machine > Test Failover.

Select your latest replication > and destination network > OK.

Wait till we are “all-green” In practicality you need to wait a while longer, you will see, (if you go to boot login and watch the screen), the VM will boot up install new hardware items, it will be a while before you see the login screen.

At this point if you have failed over into a ‘production LAN” you will be able to connect to the failed over machine. 

Warning: The failed over machine will have a DHCP address, if you have failed over a domain controller, or asset that needs a static IP, then you will need to manually rectify that, when moving it into production.

In my case I just want to give my machine a Public IP so I can connect to to via RDP (to Test)

Azure: How To Assign a Public IP to a VM

All Services > Public IP addresses > Create Public IP Addresses > Give it a name > Choose your Resource Group > OK.

On your VM > Networking > Select the NIC.

IP Configuration  > Select the configuration.

Select “Enabled” > Assign the public IP object > Save.

You can now connect to your VM.

You can now, perform a “Cleanup Test Failover” and perform a live failover.

Related Articles, References, Credits, or External Links

NA

Veeam: Restore / Migrate a VM to Azure

Posted on by
2

KB ID 0001511

Problem

Veeam is both a great company, and backup and recovery is the best product in its class by a country mile, (yes Zerto is great but it costs a fortune!) With Backup and Recovery 9.5 Update 4. You can recover a VM straight into Azure, (and Azure Stack).

Which pretty much means you can use Veeam to Migrate your VMs (or physical machines) from vCenter (or Hyper-V) into Azure/Azure Stack. You need to have a successful backup, (or replication) in Veeam before you start. (That goes without saying but I’ll get emails if I don’t point that out!)

Obviously you also need an Azure Subscription, and you will need to have (pre configured) the following;

  • A Resource Group
  • A Storage Account
  • A Virtual Network 
  • A Network Security Group

Veeam B&R Server Pre-Requisites

Veeam Backup and Recovery Download

Veeam Backup For Azure Download

You will need to disable IE Enhanced Security, (or as I refer to it, the “Randomly break things, before you discover it’s on and disable it feature”).

Add the following URLs to IE’s trusted sites & ensure Protected Mode is not enabled for this zone, (this is the default as shown);

  • https://login.live.com/
  • https://login.microsoftonline.com/
  • https://secure.aadcdn.microsoftonline-p.com/
  • https://auth.gfx.ms/
  • about:security_veeam.backup.shell.exe?ver=95u4

Add in the Azure PowerShell Snap-ins;

[box]Install-Module -Name AzureRM.Automation -RequiredVersion 5.1.1[/box]

To connect to Azure you will need an Access Key > Login to Azure > All services > Storage Accounts > Select your storage Account > Access Keys > Copy a key to the clipboard.

Veeam: Adding Azure Accounts

From the main menu > Manage Cloud Credentials > Add > Microsoft Azure Storage Account > Supply your Azure Login > Paste in the key (from above) > OK.

Repeat the procedure, but this time add ‘Microsoft Azure compute account”.

Next.

Microsoft Azure > Next

Add > Supply your Azure credentials > OK > Next.

Finish (that was easy!)

Veeam: Restore or Migrate a VM to Azure

Home > Restore > (select the platform, here I only have VMware vSphere) > Restore from Backup.

Entire VM Restore > Restore to Microsoft Azure.

Add in the VM to restore > Next > Select the subscription and location  > Next.

Edit > Add in your Azure Storage Account > Select a VM size (WARNING The bigger, the more expensive!) > OK > Next > Group > Select your Resource Group > OK > Next.

Network > Add in your virtual network and subnet > Next > Group > Add in your Azure Network Security Group > Next.

I’m not going to scan my VM, but if you are recovering from an infection you might want to > Next > Next.

Finish > When successfully completed > Close.

Give your VM a while to power on, you can enable boot diagnostics to see if it is at the logon screen (Note: you need to manually refresh this screen).

Then you can connect via RDP. Note: You may need to enable TCP Port 3389 inbound before this will work.

Don’t forget to remove VMware tools!

Related Articles, References, Credits, or External Links

NA