Skip to main content

Azure AzureMigrate

Azure Migrate Steps:

Azure Migrate is having two high level tasks as follows,

Azure Migrate Assessment tools: Discover and Assess

Azure Migrate Migration tools: Discover, Replicate and Migrate.

**************************************************

1. Azure Migrate Assessment tools: Discover and Assess:

Step1: Login to portal.azure.com

Step2: Go to "Azure Migrate" and Choose the right tool. "Azure Migrate" or even you can add a 3rd party tool like "Clounamize".

Step3: Check the valid subscription

Step4: Choose the migration source and install the agents. (Now we can discover the On-Perm environment without installing agent too however Interconnection map needs the agent).

Step5: Choose Discover -> Two way we can discover, Discover using appliance (It is actually a VM to download and run to scan/discover VM environment/collects the data of the size of the VMs/OS/Dependencies. Performance data) and Import using .csv

Discover using appliance: Are your server virtualized?

  Yes, with VMware vSphere Hypervisor

              Yes, with Hyper-V

  Physical or other (AWS, GCP, Xen, etc.)

Step6: Choose the Assessment -> Here we can select the various tools, "Azure Migrate" or 3rd party tool like "Carbonite".

Here we can choose various setting to analyze the cost. Grouping, more.

2. Azure Migrate Migration tools: Discover, Replicate and Migrate:

Step7: Choose Discover under "Migration tools" and Select the workload you have and select target region (eg: east us) and etc. Click "Create Resources" Button.

Step8: Download and Install the "AzureSiteRecoveryProvider.exe) the replication provider on the Hyper-V servers. Download the registration key file to register the Hyper-V host to this Azure Migration Project.

Step9: Click "Finalize Registration" Button.

Step10: It will take few mins to "Registration Finalized"

Step11: Step1: Click "Replication" (Start replicating machine) then select the workload (VM) to migrate

Step12: Select the right migration settings from an assessment from the scroll list

        Yes, apply migration settings from a Azure Migrate assessment

        No, I'll specify the migration settings manually

Step13: Select which systems you want to migrate and etc

Step14: Select the target properties for migration.

 Subscription, Resource group, Virtual Network, Subnet, Azure hybrid benefit yes/no for using existing license.

Step15: You can see the target compute populated automatically however you can customize the Azure VM size, OS Type, OS Disk and Availability Set.

Step16: Disk: Select the managed disk type to use for the disks of the migrated machine. Optionally, you may also choose to exclude certain disks from replication by unselecting those disks from the list of disks to replicate.

Step17: Review and Start Replication

How long this migration going to take is depends on the size and etc.

Step18: Click Overview to see the migration status.

Step19: Check all the values manually

Step20: Step2: Click "Test Migration" (Perform test migrations) and Select the OnPermVM (...) to test. Select the right network and it will initiate the failover the from OnPermVM to Azure.

Step21: Once the "Test Migration (Failover)" completed then Click "Overview"

Step22: Select Manage -> Replicating machines and see the "Cleanup test failover pending" then Click "..." and select "Cleanup test migration" and Put in your Notes (Eg: 100% Good to migrate).

Select the Check Box "Testing is complete, Delete test virtual machine. Click "Cleanup test" Button. It will cleanup the test VM from the Resource group.

Step23: Step3: Click "Migrate" (Migrate to Azure) Select the OnPerm VMs (You may choose "Shutdown machines before migration to minimize the data loss?) Yes, Click "Migrate" Button

        It will start the migration jobs for individual VMs.

Step24: You may notice some "Failed" status under "Error details" and you have to fix the issues. (Eg: OnPerm VM might have 2 NICs and Target Compute size in Azure you selected with 1 NIC, so Modify the no of NICs by selecting the new suitable Compute Size) and initiate the "Migrate" again.

Step25: You can see the status of the OnPerm VMs in Hyper-V server to see the VMs status are off.

Step26: Go Back to Azure and check the "Overview" to make sure the Job status of Migration.

 

Labels:

Comments

Post a Comment

Popular posts from this blog

Multi Cloud Intro

 What is Multi Cloud? Multicloud is a cloud approach made up of more than 1 cloud service, from more than 1 cloud vendor-public or private. For example, Availing different services from different provider (AWS/Azure/GCP), a s well as specialized platform-as-a-service (PaaS), infrastructure-as-a-service (IaaS), or software-as-a-service (SaaS) providers. Major reason for MultiCloud approach, Price competition, Variety of features, Location diversity. Challenges with Implementing Multi-Cloud: Multi-cloud isn’t all rosy: there are some downsides, and complexity to deal with. When deciding on our personal architecture, balance these with the benefits and our goals. 1) Pricing: Public cloud typically becomes more expensive than operating on-premise over time, but volume discounts can soften that blow. By diversifying your application deployment across multiple clouds. 2) Multi-cloud expertise needed: Public clouds are all built very differently, and there’s a learning curve for deploying...
Post a Comment
Read more

Azure Cost Reduction

Looking for the Cost Reduction opportunities post-migration or cloud adoption is a great challenge to do however we can follow the given practices to save the cost for the Customer, Azure Cost Reduction can be achieved by using the following practices: Azure Reservations: Purchase Azure services for 1 or 3 years in advance with significant discounts Reserved instances – Azure Virtual Machines Reserved capacity – Azure Storage, SQL Database vCores, Databricks DBUs, Cosmos DB RUs Software plans – Red Hat, Red Hat OpenShift, SUSE Linux, etc. Reservations are made for 1 or 3 years Azure Spot VMs: Purchase unused Virtual Machine capacity for a significant discount How does it work? Significant discounts for Azure VMs Capacity can be taken away at any time Customers can set maximum price after discount to keep or evict the machine Best for interruptable workloads (batch processing, dev/test environments, large compute workloads, non-critical tasks, etc.) Hybrid use Benefit: Use existing l...
Post a Comment
Read more

AWS Messaging Services

The most important messaging services we need to know when it comes to Application Integration are the following: Remember these keywords against each messaging service SNS: PubSub (Like publisher, subscriber) SQS: Queueing (Like batch) Kinesis: Real-time data Kafka: BigData SWF: State tracker and task coordinator SNS - Amazon Simple Notification Service: SNS is commonly used for sending simple internal emails. So for example when someone sign-ups on a website, We can use the AWS SDK to send a message to an SNS topic which then sends a plain text email. Another way we use SNS is to trigger webhooks in our application. For example, let us say we have a web-app which needs to extract data out of a PDF so we need to use a PDFTK which we have to run in a custom runtime in a Lambda function because of legacy reasons. When that lambda has processed that pdf we want to notify our web-app to tell the user it's done. We can have Lambda tell SNS which will then send an HTTP request to an api...
Post a Comment
Read more