There has been a shift towards server-less computing happening for some time now. What does it mean for storage, files, and how we access data such as files? I’ve had the good fortune to work with some amazing technical people over the years and I’ve recently had a couple of colleagues ask me about what it may mean for their career with this shift to server-less computing…
Read the full article…
In my last article, you were introduced to Azure Site Recovery and Azure Migrate. These services allow you to discover, assess, and migrate workloads into Azure quickly using a framework built using the foundations of Azure Site Recovery. We talked a lot about disaster recovery foundations, technical requirements, and some key differences between ASR and Azure Migrate. Today, we’ll be working in Azure Migrate and we want to get you ready to do a test fail-over of a workload from your VMWare environment into Azure. There are lots of steps to follow, so give yourself about 3 hours to work through all the reading and steps. You may need to step out of this article to perform changes in your VMWare environment as part of your readiness. I want you to be comfortable using Azure Migrate so let’s get started!
Azure Migrate allows you to discover, assess, and migrate workloads into Azure quickly using a framework built using the foundations of Azure Site Recovery. Starting out with ASR is a solid and well-built foundation that allows you to replicate a source environment into Azure. Azure Migrate service is built on top of the foundation elements of Azure Site Recovery and provides a highly reliable and rapid method to sync your current data from VMWware, Hyper-V, physical servers on-premise, and AWS into Azure. This can be part of your disaster recovery plan, migration strategy, and migration testing. Azure Site Recovery has often been deployed as a major part of disaster recovery strategies for on-premise or existing Azure virtual machines.
A bit of basic information first. Azure Site Recovery will help you with:
• Console to manage discovery and connectivity to Azure
• Replication from source to Azure
• Testing your migration to ensure that you get your VMs in Azure as expected
• Cut-over migration into Azure