>> Hey, friends. Moving different types of resources around
the cloud can require downtime and some extra effort.
Azure Resource Mover streamlines your planning process
to accelerate your move and help protect your resources.
Sujay Talasila is here to show me how to move
multiple resources between Azure regions today on Azure Friday.
[MUSIC].
>> Hey friends. I'm Scott Hanselman. It's Azure Friday.
Today, I'm going to learn all about the Azure Resource Mover.
How are you, Sujay?
>> I'm doing good, Scott.
>> I am very excited to talk to you because what I love about
Azure Friday is that people come on and they show me
a tool to solve a problem.
It's always a problem that I have.
That makes me happy because it feels like people
in Azure are listening to customer problems,
and they're like, "Hey, we can solve that."
I'm excited to hear about the solution
that you have to solve my problem.
>> Yes, sure. I'm going to talk about
the Azure Resource Mover Service and how it's
going to help you move
multiple Azure resources across the regions,
which can be helpful in scenarios with your new regions
coming up in Azure every other quarter.
As a customer, you want to move
applications from erstwhile regions to the new region.
Our service is going to help achieve that very easily.
>> How would we do this before?
Would I just have to redeploy if I wanted to
move something from place to place
or would I have to call support?
>> Exactly. Earlier before the service was there,
you had to follow
different mechanism to move different types of resources.
Sometimes you have to do a manual approach.
For example, if it's a virtual machine,
you have to use
Azure Site Recovery replication to
copy the data and then bring up the VM.
If it's the SQL, you have to use SQL geo-replication.
If it's storage account,
you have to manually copy the data.
Every service has a distinct mechanism,
and that is what makes it very complex
for customers because you have
learn how to move different types of
resources and then plan moving your application.
As you-all know, application
in Azure is not just one VM or one SQL database.
It's a collection of resources.
You might have an application which is running on a few VMs,
SQL databases, maybe app services,
maybe the storage account, all of that.
>> All right. You've got
a demo and you can actually show me what this looks like?
>> Yes, I'm going to do a quick demo and show you
how you can easily move across regions.
Let me start off by
showing an application which is running in Central India.
This application is, again, a simple application.
It has a couple of virtual machines,
couple of SQL databases,
and all the networking components
associated with virtual machines.
I'm going to demo how you can easily move this application and
these resources from Central India to East Asia region.
To get started, you can launch Azure Resource Mover.
You can see it in the favorites list here.
If you don't see it,
you can as well search in the resource service list,
and then you can find it here.
Then you click on "Azure Resource Mover".
This takes you to Resource Mover hub experience.
Here you can see
different scenarios ready to move across subscription,
move across the resource groups.
These are the scenarios which have
been existing for sometime in Azure.
The new scenario is moving resources to another region.
I'm going to click on "Move across regions".
This is the subscription where I
have resources which I showed earlier.
Then I'm going to click the source region,
which is "Central India",
and then my target region,
which is "East Asia",
and then click on "Next".
In the second step,
you need to select the resources that you want to move.
These are all the resources in
the subscription running in Central India.
Just to make it easy,
I'm going to filter the resource group
belonging to that specific application which I
showed earlier that remove this one.
Now I'm going to see all the resources that I want to select.
For this demo, what I'm going to do is just select
the virtual machine entity and the database entity because I'm
going to show you further in the demo
how Resource Mover can help you
identify the related dependencies
with the dependency analysis experience that we have.
So I'm going to click "Next".
Here you can preview that you have selected four resources.
You also have a nice specs
explaining what are the further steps
you need to do in the move journey,
and then you click on "Proceed".
I have a few VMs
which I have already added earlier for the demo purpose.
Here you can see the couple of VMs,
a couple of databases,
and the resource group to which these resources belong.
As you can see, you have a pop-up saying, "Hey,
validate and identify dependencies belonging to these resources."
I'm going to click on "Validate".
This is going to take maybe a few seconds.
What it does in the background is it turns
a dependency checker and
identify the related dependencies
for the resources that are already selected.
For example, for the virtual machine and the SQL,
the networking resources and for the SQL Server,
all of those are going to be identified.
After I click on "Add dependencies",
you can see here
the related dependencies that have been automatically identified.
You can review them and add them to the list.
>> I'm curious if I may ask a question.
Can a public IP address be moved between regions
or are there limitations to the external IP address?
>> Public IP address here,
the actual address value is not going to
be same as the source per region IP.
>> Okay.
>> But from a taxonomy perspective,
let's say your application has two public IP address.
After the move, you'll have again
the same application taxonomy in the other region,
where you have two public IP address.
But the actual value may change.
Very similar if you're moving applications from on-prem virtual,
your endpoints are going to change.
Similar thing applies here.
But your application if it has two VMs,
two disks, two public IP address,
two NIC, two NSGs,
all of that is going to remain same.
But the actual value will change because networking doesn't allow
you to have the same IP address value in another region.
>> Okay. What I'm hearing you say is that the need for
your application to have
a public IP address is expressed as a resource in Azure,
its NIC, its network interface card
and the IP address associated with it remains,
it's just the value will change. Cool. Thank you for that.
>> Exactly. Once you click on "Add Dependencies",
the dependencies will get added.
Then the next step in the move journey
is broken into three critical steps.
The first step is to prepare.
What exactly happens in the prepare step is,
if you take a SQL database,
which can run into terabytes of data,
and even watcher your machine disks
can run and copy piece of data.
All of this copying of data
across regions is going to take a lot of time.
For that reason what happens in the prepare step
is the copy of data starts
behind the scenes where
your source watcher machine
or SQL database, all of them keep running.
There's no impact to your source application.
The preparation process will
happen in the background. That's the first step.
I'm going to show you how you can
do to prepare all the resources that you want to move.
I am going to select some of the resources,
and also I'm going to just select a
few just because I want to show
you how this experience is going to,
again, automatically pick all the related resources
belonging to these bits.
For example, I click on "Prepare" and it again,
just revalidate if all the required resources out there.
If not, it will automatically add and start the preparation step.
For simple resources like NIC,
VNet, there's no data that needs to be copied.
The preparation step is going to finish in just a few.
But for resources or virtual machine,
disks, and SQL database,
it might take a few hours and sometimes
maybe a couple of days depending on the size of data.
Once the preparation is done
and the resources move into Initiate move pending stage,
you can click on "Initiate move".
I'm going to show you how you can do it.
You just select the resources that you want
to initiate the move step.
After this step is bid,
the resources will come alive in the target region.
Then you can actually test the sources in the target region.
You have the option to test as many times as possible.
This is the key capability of Resource Mover,
where it lets you test because
the way customers actually move
is they're not going to come and move,
and if you ask, they plan ahead of time.
So they'll take the application that they want to move.
They test it, validate that everything works fine.
Then over a weekend maintenance window
bring the application in the target region
and verify that everything is working fine,
and then you can go ahead and shut
down or delete the source resources.
This is how you can move multiple resources across regions.
>> Can you move across subscriptions,
or is that still the thing that requires support?
>> Moving across subscriptions,
you haven't experienced where you
can move across subscriptions within the same region.
By moving across regions today,
we do not support moving across subscriptions.
What we suggest to customers,
to just minimize the various steps in the move.
You can either move across
subscriptions and then move across regions.
Or you move across regions and then move across subscriptions.
To just minimize the scope of
the move into avoiding this upraising issues,
we ask each of them to distinct data.
I also want to show one more thing.
As part of the move,
what you can do is
if you want to pick
a different configuration in the target region.
Take for example if you have
a virtual machine running with
a specific skew in Central India region,
but you want to pick a different skew in the target region,
either because of your new skewer families
available or a specific skew is not there.
The experience is going to provide that option.
I'm going to show you how you can actually edit
the target configuration as part of the experience itself.
Let me pick a resource and then show you how it can be done.
Click on "Demo VM".
Yeah, I think then the operation in progress.
>> At this point you're looking for
an operation that's already finished?
>> Yes, I am looking for an operation which is already finished.
Or I can show, for example,
the SQL database you want to fix.
This experience is also going to tell if there is
an issue with the target configuration.
You click on "Fix Errors" and it's going to tell
you the target resource name is already in use.
How can you fix it? You can click on
the destination SQL database configuration,
and then you can give it a different name.
Similarly for SQL, again,
if you're moving across regions for reason
where you want to move from
a non-availability zone configuration
to an availability zone configuration.
You are in a region which doesn't support availability zones,
but you want to move to a region
which supports availability zones.
As part of the experience,
you can actually select zone redundancy options for SQL database.
Similar thing you can do for VMs as well,
you can select availability zone
in the target region if that region supports availability zones.
As part of the move at the end,
you will get a VM which has availability zone configuration.
These are some of the target configuration options that are
built-in into the move experience
so that you get them as part of the move.
>> Resource groups in Azure or logical things
where you're drawing a circle around
a group of things and naming it,
so you have your named resource group.
Those resource groups can span all across Azure,
so none of these physical changes
affect your logical resource groups?
Do they or do change your research groups names
while you make a change as well?
>> Your character at the resource groups
are only logical entities.
As part of the move,
you have an option where you can retain
the resource group or you can
pick a different resource group in the target region.
If you see here in the experience,
resource group is also practically printed as another resource,
then you have an option where a new resource
is getting created in the target region,
or you have the option to pick
a different existing resource group.
Because a lot of customers,
actually, even though resource group is logical,
they tend to create
resource group in the region and then keep it local to the region.
For that purpose, we
are not going to restrict them from achieving that.
Also this experience is going to span across resource group.
A lot of customer applications,
they have resources spanning across resource groups.
Like you have VMs in one resource groups,
you can have networking in a different resource group,
so you can move all of that.
This is the experience of this view.
You can see all the resources that are moving from
Central India region to East Asia region in the subscription.
This is kind of a workspace where you can see all of them,
and you can do filtering and select steps for each of them.
Every resource can be at
a different point in time as part of the move journey.
Typically if you have, say 20 applications to move.
This is the workspace where you can come and check
the status and move Application 1 this week,
Application 2 two weeks later.
All of that you can do in this center experience.
>> That's fantastic. This is a dream come true for me.
I feel like I needed this before.
This is going to be really exciting for customers.
>> Yes. In fact we have been receiving a lot of
interest in the last few weeks after the release,
and there are a lot of customers who are
using this to move for scenarios,
especially with some of
the data residency laws and
compliance laws which are introduced to various countries,
some of the customers want to move
their applications to their own country.
For example, France was not
a region available a couple of years ago,
but now that France is available,
there are some customers who want to move from
Amsterdam region to France region.
There's lot of such combinations.
Also, there are some regions which are
announced by Azure recently,
but it's going to take some time for those regions to come alive.
But will the customers have to wait using Azure till then?
Maybe not. That's what we are providing as a solution with this.
For example, New Zealand is a region which is announced,
but it's going to take a few months before it's available.
Now, if you're a customer who is planning to move to Azure,
you can use this opportunity where you can start
hosting your applications in a nearby Australia region,
and say if you caught us
later when New Zealand region is available,
you can move to that region.
You may not wait moving or start
using Azure because the region you want is not yet available.
You can fast track your migration journey to grow.
>> The Resource Mover is available now though.
So even though these regions that you're
talking about are always coming,
there's always going to be a new region somewhere.
I can move my things today because I have
a few things in a region that
I made a mistake deploying
earlier and I've just been too lazy to move it.
This means I can move this just over lunch.
>> Yes, true. Resource Mover has been
announced in general availability at Ignite in March last month.
It's now available in all public regions,
which are currently available.
You can move from any public region to any public region.
As and when new regions get opened up,
Resource Mover is also going to be made
available in those regions so that you can move there.
Moving forward, we're going to add support for Sovereign
and other types of Clouds as well.
You can see this is the Resource Mover service base.
You also have a detailed documentation
on how you can use Resource Mover for various resources.
You can go ahead and start right away,
you can move your resources by today evening.
>> Fantastic. I'm actually going to do it by lunch.
I will have Azure Resources moved before my lunch is over.
This is fantastic stuff.
I appreciate you chatting with us today.
>> Thanks Scott for having me.
>> I am learning all about how simple it
can be to move multiple resources between
Azure regions using the Azure Resource Mover
today on Azure Friday.
>> Hey, thanks for watching this episode of Azure Friday.
Now I need you to like it,
comment on it, tell your friends, retweet it.
Watch more Azure Friday.
[MUSIC]