Skip to content
Tags

, ,

Azure Virtual Datacenter (VDC) Part I – Migration AS IS and TO BE

03/06/2019

When we work on a Public Cloud migration project and the design is geared towards Azure, the "AS IS" scenarios are very common.

AS IS

For those not started with this term, "AS IS" means to take as English, ie to copy the VMs from one environment to another without any change, using Azure as a hypervisor.

In general, the ISIS migration models are not efficient, because they consume a lot of resources in IaaS (VMs) that are expensive, not taking advantage of services that are cheaper (SaaS or PaaS). However, the advantage is that it is faster and does not require changes.

TO BE (or LIft and Shift)

Good migrations are the "TO BE", which in free translation would be "SERA" in the sense of transformation. The TO BE migration model is premised on using the services and not just migrating VMs.

TO BE Migrations are laborious and time-consuming, since this mapping involves understanding what’s inside the VMs.

The execution cost is much lower because SaaS and PaaS have large financial advantages when compared to the IaaS model.

For example, in AS IS an IIS server and another SQL Server will simply be copied the virtual and initialized disks. In the TO BE model, we will isolate each of the applications that IIS performs and create Web Plan for isolation and Web Services for each site, and in the case of SQL Server we would use the Database service (SaaS or PaaS).

Using Service MAP

The first step to doing a migration is to map what each VMs or physical server performs in the environment.

For this we use the Service MAP: https://msincic.wordpress.com/2018/07/03/azure-log-insights-service-map/

It will be possible to see the interconnections and services that each server uses between the environment and map which service we have to replace.

Understanding the Azure Datacenter Concept

To design a datacenter using VMWare, Hyper-V or KVM, it is necessary that the design of the hosts, network and other details be done by specialists in the hypervisor.

The same goes for Azure, we need to understand the different components to design a datacenter with its features.

For this, it is necessary to study, and much. It is also necessary to break the paradigms of physical datacenter and think about services.

One way to do this is to use Microsoft’s own Guide available at https://docs.microsoft.com/en-us/azure/architecture/vdc/

This guide has all the perspectives of a virtual datacenter, will help you understand the virtualization, network, security, services and lift and shift layers, that is, the transformation to a more efficient model.

To get started download the presentation available at https://aka.ms/VDC/Deck

Conclusion

It is not easy to make a correct migration, but it is possible and the result will be much better.

During the month we will explore the items that make up the VDC and you will see that it is possible to do this type of migration with new resources, more efficient and appropriate costs.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: