Introduction
When you create new resources , you need to choose where are you going to host those resources ,and here we talk about the region .
It is very important to choose were you are going to host your resources , for example let’s say you have created a backend for your service in France and you have created the Front-End (web app ) in East Asia .
well from this point we can see that you may encounter high latency issue because the Front-End and the backend are in deferent areas more than that , you should consider saving money $$ too .
Saving Money
By comparing regions within your desired “area” as illustrated in picture below, the savings over a quantity of instances can be significant. Good region selection is fundamental to controlling Azure costs, and for costs across the other clouds as well.
simple calculation : 0.92*720hours (brazil south) =662.4$ ,
0.68(canada central) *720=489.6 $
You might move resources to different Azure regions to:
- Align to a region launch: Move resources to a newly introduced Azure region that wasn’t previously available.
- Align for services/features: Move resources to take advantage of services or features that are available in a specific region.
- Respond to business developments: Move resources to a region in response to business changes, such as mergers or acquisitions.
- Align for proximity: Move resources to a region local to your business.
- Meet data requirements: Move resources to align with data residency requirements, or data classification needs.
- Respond to deployment requirements: Move resources that were deployed in error, or move in response to capacity needs.
- Respond to decommissioning: Move resources because a region is decommissioned.
What resources can I move across regions?
Using Resource Mover, you can currently move the following resources across regions:
- Azure VMs and associated disks
- NICs
- Availability sets
- Azure virtual networks
- Public IP addresses
- Network security groups (NSGs)
- Internal and public load balancers
- Azure SQL databases and elastic pools
How to ?
To move resources across regions, you select the resources that you want to move. Resource Mover validates those resources, and resolves any dependencies they have on other resources.
In this demo we are going to move a SQL-Server and databases from East-US to France .
What we already have ?
We have a SQL-Server that contain a database and that database contain one table .
This SQL server is East-US and we have been asked to move it to France central .
PS : Do not forget to Update database connection strings before you commit.
Follow the steps below to migrate your resources from region to region .
Here we create the resource group where we are going to migrate our resources.
Here we are going to start the moving process :
- In Move resources > Source + destination, select the source subscription and region.
- In Destination, select the region to which you want to move the resources. Then click Next.
- In Resources to move, click Select resources.
- In Select resources, select the resources. You can only add resources supported for move. Then click Done.
