Azure Classroomnotes 16/Jul/2022

Azure Migrations (P2V) Continued

• After the installation of mobility Agent and configuring them to the replication instance, the source servers get identified in the Azure Migrate Refer Here
  
• Create a Resource Group and a virtual network. Then select these details in Target settings tab
  
  
  
  
  
  
  
  
  
  
• After the replication is completed,
  • Source might have some new changes For this we need to replicate the disks continuously till the migration is complete.
• Steps:
  • Test the migration
    
    
    
  • Migrate the Server
  • Stop the replication
• Post Migration Steps
  • Change DNS Records as per the needs

Activity

• Consider you have migrate 10 physical servers, The servers are as follows

srv1 -> redhat 5
 srv2 -> redhat 6
 srv3 -> Windows Server 2012 R2
 srv4 -> Windows Server 2019 
 srv5 -> Ubuntu 12.04

 srv2-1 -> redhat 5
 srv2-2 -> redhat 6
 srv2-3 -> Windows Server 2012 R2
 srv2-4 -> Windows Server 2019 
 srv2-5 -> Ubuntu 12.04

• Write down steps which you would follow to migrate above physical servers
• Solution:
  • Verify if all the operating systems are supported for migration or not by Azure
  • If they are not supported, try upgrading the servers to the supported/compatible OS
  • Create a excel sheet with server names ip addresses , cpu, ram, storage (size and type)
  • Create a Replication Instance in your ogranizational network which has connectivity with all the servers above
  • Configure the Replication Instance
  • Download the necessary tar or installables for mobility agent on each of the source server and establish connections between source and replication instance
  • Now we can migrate 10 servers as a batch
  • Now follow the instructions to replicate server by specifying target settings