2.1 migration

Assess, Migrate, Optimize, and Monitor

  1. assessment

full inventory and dependency map
Each application must be fully investigated

app

  • rehost
  • refactor (PAAS)
  • rearchitect
  • rebuild
  • replace

Involve key stakeholders

estimate costs

  1. migrate

Azure Site Recovery

workloads

  • start with small migratio, no business critical
  • Prepare the source (vCenter Server) and target (Azure) environments.
  • Set up and start the replication between the two.
  • Test that the replication has worked.
  • Fail over from the source servers to Azure.

Azure Database migration service

  • Assess your on-premises databases.
  • Migrate the schemas.
  • Create and run an Azure Database Migration Service project to move the data.
  • Monitor the migration.

Decommission on-premises infrastructure

  1. optimize

Analyze running costs

Azure Cost Management

  1. monitor

health and performance monitoring

azure monitor

azure sentinel

Azure Migrate

Assess your environment:

  • agentless environment discovery
  • agents to perform a dependency analysis.

performance-based sizing calculations

Hyper-V and VMware

  1. project

set up in the Azure portal

  1. Discover machines

downloading a lightweight collector appliance

Microsoft Monitoring Agent and Dependency Agent on each VM
Linux and win

  1. Create an assessment

portal: Assessments section, and then select Create assessment

Migrate servers

Add Azure Migrate: Server Migration to your Azure Migrate dashboard

  1. Replicate

100 VMs simultaneously

  1. test replication
  1. Migrate

shut down the virtual machine

virtual machine will be down for a few minutes

  1. Post-migration steps
  • review the security settings (firewall, Azure Disk Encryption)
  • backup
  • Replicating

clean-up tasks for the remaining on-premises servers

azure VM, hyper-V, vmware, phisical win

Migrate databases

online and offline migrations

pricing tiers

  • Standard:
    Supports only offline migrations. There's no charge to use this tier.
  • Premium:
    Supports both offline and online migrations. There's no charge for the first six months. After that period, you'll incur charges.

Destinations

  • Single Azure SQL Database instance:
    A fully managed, single SQL database.
  • Azure SQL Database managed instance
  • SQL Server on Azure Virtual Machines
  • Azure Database for MySQL
  • Azure Database for PostgresSQL
  • Azure Cosmos DB
  1. Prerequisites
  • Download the Data Migration Assistant: on-premises servers running SQL Server.
  • Create an Azure Virtual Network instance
  • Configure the network security group: allow inbound connectivity to the service via ports 443, 53, 9354, 445, and 12000.
  • Configure the Windows Firewall: port 1433 1434
  • Configure credentials:
    • Add CONTROL SERVER permissions to the credentials used to connect to the source SQL Server instance.
    • Add CONTROL DATABASE permissions to the credentials used to connect to the target Azure SQL Database instance.
  • Provision your target database in Azure
  1. Assess

Using the Data Migration Assistant, create an Assessment project

  • servers
  • credentials

report

  1. Migrate the schema

rules for how the data in it is organized and the relationships between data elements

creates an empty structure

  • create a new Migration project
  • select the 2 servers
  • Set the scope of the migration to Schema Only
  • Deploy Schema
  1. Migrate your data
  • Create an instance of Azure Database Migration Service. Choose the pricing tier
  • Create a new migration project
  • Specify source and target server details, including the authentication information.
  • Identify the databases
  • Run and monitor the migration.
    • Select the Run migration button to start the migration
    • Track the progress
  • After all the required databases are migrated, check them to make sure they're working.