Azure Migration

 

There is prerequisite 4 main steps:

1.      Understand and create your Cloud Operating Model

2.      Assess your current environment

3.      Migrate it (using Azure Migrate free tool)

4.      Optimize your utilization

5.      Secure and Manage it

The Assess phase includes three steps:

·        Discover

·        Map on-premises applications

·        Evaluate

Uploading: 147020 of 147020 bytes uploaded.


Azure provides a myriad of services, from compute to data analytics or hosting. This will include:

·        Virtual Machines

·        Azure App Service

·        Azure Functions

·        Container in Azure

Microsoft makes 5 distinct Azure cloud environments available to customers:

6.      Azure public cloud service is available globally

7.      Azure in China is available through a unique partnership between Microsoft and 21Vianet, one of the country’s largest Internet providers

8.      Azure Germany provides services under a data trustee model, which ensures that Customer

9.      Data remains in Germany under the control of T-Systems International GmbH, a subsidiary of Deutsche Telecom, acting as the German data trustee

10.   Azure Government is available from 3 regions in the United States to US government agencies and their partners

11.   Azure Government for DoD is available from 2 regions in the United States to the US

Department of Defence

Azure Migration Strategy

The Azure cloud migration strategy will cover the following areas:

·        Azure Resource Manager (ARM) model to support effective security, policy/compliance enablement and cost attribution

·        Rightsizing of the cloud infrastructure based on collected performance and configuration data to support predicted workload

·        Cloud migration model to support maintenance window schedule and concurrent cloud/on-premise availability

·        Networking topology, such as VNets, firewalls, ExpressRoutes, inbound/outbound availability

·        Plan for Active Directory migration to/integration with Azure Active Directory

·        On-premise to cloud license transition for IaaS workloads

Cloud Deployment

The deployment phase of the Azure cloud migration will consist of creating:

·        Key Azure elements, such as tenants, subscriptions, resource groups and resources

·        Configuration and synchronization of the Azure Active Directory with on-premise Active Directory

·        Networking configuration, such as public/private address spaces, VNet/peering, Network Security Groups (NSG), ExpressRoutes, site to site VPNs, firewalls, etc.

·        Virtual Machine (VM)/Database migration to the new infrastructure using Azure-native tools such as Azure Site Recovery, Azure Backup and SQL Service Migration Assistant

Five simple steps to achieve Azure cloud migration

1. Map application workloads

Use a single interface to view all applications, on-prem and in the cloud. You can then easily understand how applications are connected and develop a reliable plan to move data to the cloud.

2. Identify common service dependencies

Common service dependencies can be anything from Active Directory to DNS to an update service within your environment. Take advantage of Guardicore’s process-level and application dependency visibility, contextual relevance, and real-time and historical views.

3. Identify business dependencies

What other applications depend on your applications? Once you use Guardicore to comprehensively map out dependencies, you can confidently accomplish your legacy applications migration – without breaking or misconfiguring anything.

4. Gradual lift and shift

Achieve your cloud workload migration with speed, clarity, and assurance – and zero downtime. Continually monitor and assure a smooth transition from on-premise to the cloud.

5. Post migration dependency validation and policy enforcement

Implement granular micro segmentation policies, as well as threat detection and response features. Fill the gaps in cloud-native security and keep your critical assets secure.

Technical details of migrating to Azure Cloud Services (extended support)

https://docs.microsoft.com/en-us/azure/cloud-services-extended-support/in-place-migration-technical-details

 

Azure migration journey

Rehost - Lift & Shift

Use case

·        Want to move to the cloud now but modernize later and drive instant reduction in TCO

·        Looking for the quickest way to unlock the benefits of a more flexible and scalable cloud infrastructure

·        Want to consolidate data centres, refresh hardware or looking to move away from on-premises systems

Benefits

·        Potentially high ROI (435% after migration)

·        No need to manage data centres or own/purchase hardware anymore

·        Flexible and scalable infrastructure

Refactor - Containers & PaaS

Use case

·        Looking to unlock advanced cloud benefits but unable or unwilling to change code or rewrite app for cloud-native functionality

·        Using multiple cloud providers and looking for portability and modern DevOps workflows

·        Using multiple stacks and/or OSS at the same time in the same application

·        Need extra capacity for legacy apps, and on-demand ability to scale

 

Benefits

·        Increased agility with built-in DevOps

·        Improved app portability and density

·        Existing languages, frameworks and code can be re-used and extended

Rearchitect - Decompose into Serverless & Microservices

Use case

·        Apps need major revisions to add new functionality or take advantage of cloud capabilities

·        Looking to build a scalable, service-oriented infrastructure with built-in redundancy that handles failures gracefully

·        Support future growth more effectively with re-architected, cloud-native applications

Benefits

·        Improved performance, scalability, resiliency, and agility with cloud-native capabilities

·        Deliver new capabilities with a modernized codebase and an architectural revision from monolithic to distributed while still leveraging existing investments

Rebuild - Build New with Serverless & Microservices

Use case

·        Looking to build for cloud-native PaaS environments from the ground up to eliminate prior technical debt

·        Leveraging previous investments in a cloud platform, e.g. when customer data has already been moved to the cloud and applications are a logical next step

·        Using rapid prototyping and experimentation to facilitate business innovation or the scope of an existing application is too limited in terms of flexibility, functionality or lifespan

Benefits

·        Lower application TCO

·        Build applications faster and fully leverage cloud-native capabilities and advantages

·        Speed up business innovation and digital transformation

Replace - Migrate to SaaS

Use case

·        Common business applications and processes take too much administrative time, and don’t provide any unique business value

·        The most useful and effective solutions are not always available in an on-premise solution

·        The cost and complexity of maintaining individual servers and infrastructure for certain applications no longer compares well with SaaS offerings

Benefits

·        Specialized training and knowledge no longer required for mundane business applications

·        Access to features and functionality that would normally be cost-prohibitive for an organization of a given size

·        Better and faster support options

Different paths - One journey to the cloud

1.      Rehost - Redeploy as-is to cloud

·        Reduce Capex

·        Free datacentre space

·        Quick cloud ROI

2.      Refactor - Minimally alter to take better advantage of cloud

·        Faster, smaller updates

·        Code portability

·        Greater cloud efficiency (resources, speed, cost)

3.      Rearchitect - Materially alter/decompose application to services

·        App scale and agility.

·        Easier adoption of new cloud capabilities/technologies

·        Mix technology stacks

4.      Rebuild/New - New code written with Cloud-Native approach

·        Accelerate innovation

·        Build apps faster

·        Reduce operational cost

5.      Replace - Move workload to SaaS product

·        Reduce Capex.

·        Free up IT staff

·        Better Support

Azure Migrate enables:

       Agentless migration

       VMware, Hyper-V, Physical server migration SQL and non-SQL database migration

       Web app migration

       Migration from on-premises, AWS, and GCP

 

 

 

 

 

 

 

 

 

 

 

 


Core Technologies – Business Results

IaaS: 435% ROI, 73% reduction in datacentre footprint and 83% reduced IT outsourcing cost.

PaaS: 466% ROI, 80% time saved, 5.91M NPV, 50% faster deployments.

Containers: 13x more releases, 10x cost reduction, 65% faster developer onboarding, 62% better availability.

Microsoft Licensing Options

       Bundles vs. A la Carte - Mix and match!

       Enterprise vs. Business Bundles

       Open Volume

       Enterprise Agreements (EAs)

       Migrate SA Benefits from EA to MPSA

       Non-Profit

       Government/Education

       Cloud Service Provider (CSP)

The Modern Microsoft Cloud Model – a suite of applications and services

The Microsoft Cloud Model is based on a suite of applications and services: Azure, Azure IOT, Azure Virtual Machine, Azure SQL, Azure Functions, Docker Helper, Power Apps, Office 365 Suite, Sharepoint, Power BI, Teams, Automate and Dynamics Applications (Business Central is one of them).

What version of SQL Server does Azure use?

With SQL on Azure VMs, you can use any of the platform-provided SQL Server images (which includes a license) or bring your SQL Server license. All the supported SQL Server versions (2008R2, 2012, 2014, 2016, 2017, 2019) and editions (Developer, Express, Web, Standard, Enterprise) are available.

Prerequisites for using the Azure Database Migration Service

https://docs.microsoft.com/en-us/azure/dms/pre-reqs

What About Databases?

·        Built-In High Availability

·        Code parity: Same SQL Server Engine in both cloud and o-premises

·        Lift and shift on-prem applications without making code changes

·        99.99% SLA with backward compatibility through SQL Server 2005

·        The only evergreen SQL service in the cloud: you'll never need to patch or upgrade ever again

What is the size of azure sql database?

Basic tier the maximum size for a database is 2 GB. For a Standard tier the maximum size is 250 GB. For a Premium tier the maximum size is 1 TB. On elastic pools the maximum size is 500 on Premium tier. For more details, please read below article:

https://vincentlauzon.com/2017/01/04/azure-sql-elastic-pool-database-size/

About deciding to go for SQL Server IaaS or SQL Azure Databases (PaaS), the following article will help to decide:

https://docs.microsoft.com/en-us/azure/azure-sql/azure-sql-iaas-vs-paas-what-is-overview

 

 

About that end-of-life thing…

·        SQL Server - Ends July 9, 2022

·        Windows Server - Ends January 14, 2023

·        And with WVD, even Windows 7 Gets Some New Life…

·        Windows 7 Running in WVD - Ends January 14, 2023

Azure Hybrid Use Benefit: -

What is Azure Hybrid Benefit?

A benefit that allows you to migrate to cloud at big savings. You save up to 40% on Windows Server virtual machines by paying base compute1 rates!

How do I qualify?

You need active Software Assurance on your on-premise Windows Server licenses.

How do I activate this benefit?

Deploy a new virtual machine in minutes using Azure Marketplace images. Upload a custom virtual machine. Free migrations with Azure Site Recovery.

Can I apply it retroactively?

You can retag your existing VMs in Azure with this benefit by using the retroactive tagging feature and save more money.

Note: -

1.      Base compute equals Linux rates.

2.      Each Windows Server 2-Processor license or each 16-Core license set is entitled to two Azure instances with up to 8 cores each, or one instance up to 16 cores. Benefit applies both to Standard and Datacentre editions. No program restrictions, i. e. - benefit available irrespective of where customer buys their Azure: EA, CSP, Web direct etc.

3.      Pre-built gallery images are available only for Enterprise Agreement customers.

4.      Free for first 31 days

Microsoft Azure: the cloud for intelligent solutions: -

1.       In addition to having the traditional on-premises enterprise data tools— such as SQL Server—Azure provides SQL services that connects data to AI services

2.       This enables quick adoption of technologies, such as deploying a global mobile application that integrates with facial recognition services

3.       The ease of integration enables anyone to build solutions like that

4.       From bot frameworks to cognitive services, you can fundamentally change the way your business goes to market with Microsoft’s power AI platform

Benefits gained by interviewed customers that migrated or re-architected some or all workloads from on-premises to IaaS include:

·        Greater revenue opportunities from business-to-business (B2B) and customer web channels with a solution that is more mobile and reliable and meets scale and seasonality needs.

·        Increased profits from those revenues.

·        Improved production efficiency.

·        Reduced datacentre, IT resource, and outsourcing costs.

·        Easier and faster software and hardware management (such as patching and support)

Total Cost of Ownership (TCO)

The Total Cost of Ownership (TCO) Calculator can be used to estimate the cost savings you can realize by migrating your workloads to Azure. You specify the details of your existing infrastructure, various cost assumptions you want the tool to work with, and then you receive a report that shows on-premises costs compared to Microsoft Azure costs.

·        DC migration tends to be a higher number since economies of scale kick in when you start moving thousands of VMs vs. a few applications at a time. Best example of this is you’re moving entire racks out of your colo which is why the numbers improve.

·        Rehost is a higher number than refactor because Azure 3-year Reserved VMs are so competitively priced.

·        Rebuild (using App Service) provides similar savings numbers but has a better scalability story (ability to dial down/up based on demand).

The Azure TCO calculator can understand the specific of your environment and then you can further refine your business case. How does it do that?

·        Enable Azure migrate to go back and update TCO with accurate inventory scan

·        Azure migrate also does the right sizing to figure out what type of VM you should be running on.

·        Application dependencies captured by Azure Migrate will get passed to TCO as well

·        TCO calculator displaying Migration options

How can TMC help?

Why we need Azure Migrate?

We need Azure Migrate because:

1.      Unified Migration Platform: It is a single platform to monitor and run the migration to Azure Cloud.

2.      Range of Tools: It offers a wide range of tools for monitoring and migration.

3.      Assessment and Migration: Servers, Databases, Web Applications, Virtual Desktops, and Data can be assessed and migrated using a hub.

 

Azure Migrate Tools

Azure Migrate hub has some integrated tools. These tools are used to migrate servers, databases, web apps, virtual desktops, and data. This helps in easing the migration process. The tools are:

·        Server Assessment

·        Server Migration

·        Database Migration Assistant

·        Database Migration Service

·        Movere

·        Web App Migration Assistant

 

No comments:

Post a Comment

PeopleCode to retrieve Google map between two addresses

  PeopleCode Example: /* Define constants for the API request */ Local string &origin = "123 Main St, Anytown, USA";   /* ...