Cloud and Datacenter Management Blog

Microsoft Hybrid Cloud blogsite about Management


Leave a comment

#Microsoft Azure Migrate Assessments in Action #VMWare to #Cloud

Azure Migrate

This blogpost is about the Microsoft Azure Migrate tool in the Cloud doing Azure Migrate assessments to see if your on-premises Datacenter is ready for Azure Cloud Services. Before you migrate your workloads with Azure Migrate to the Microsoft Azure Cloud, you want to know the costs before the migration and what your options are in the transition. For example when you have hardware in your on-premises Datacenter which is too high qua hardware specs like Memory, CPU and storage and you can do with less Compute power, then the performance assessments are really interesting. From here you see a step-by-step guide for VMWare workload assessment(s) to Azure Cloud.

Azure Migrate preparation for VMware workload

When you search for ‘Azure Migrate’ in your Azure Subscription and click on the services you will see the Azure Migrate Overview screen. When you don’t have a Microsoft Azure subscription yet, you can get one here

Click on Assess and Migrate Servers.

Before we go further with the server migration assessments for VMware, there are more Azure Migration tools available to do assessments and migrations like the following goals :

 

For Databases Microsoft Azure Migrate uses the Data Migration Assistant for the Assessment and the Data migration to Azure SQL Cloud.
The Data Migration Assistant (DMA) helps you upgrade to a modern data platform by detecting compatibility issues that can impact database functionality in your new version of SQL Server or Azure SQL Database. DMA recommends performance and reliability improvements for your target environment and allows you to move your schema, data, and uncontained objects from your source server to your target server.

 

To identify the right Azure SQL Database / Managed Instance SKU for your on-premises Database you can use the CLI with a Script :

Here you find more detailed information about the Data Migration Assistant

When you have a Virtual Desktop Infrastructure on-premises and you want to migrate to Windows Virtual Desktop (WVD) you can use this Azure Migrate tool :

ISV Lakeside with SysTrack

You can vote for the tools or scenarios that you would like to be integrated with Azure Migrate via this Online form

When you are in the beginning of your Cloud Transition journey, what will go first to the Cloud?

  1. On-premises mail to Microsoft Office 365
  2. File Server Clusters to Office 365 into Teams, Onedrive for Business
  3. From Apps On-premises to SaaS or Paas solutions
  4. From On-premises Websites to Azure Cloud Solutions like Azure Web App.
  5. From SQL Clusters On-Premises to Azure SQL Managed Instances in the Cloud
  6. And at last Migrate Servers to Azure IaaS

Of course there are much more scenarios like Lift and Shift or modernize your workload in the Cloud like moving to Azure Kubernetes Services for example instead of IaaS Virtual Machines.

So when you want to start moving your On-premises Website(s) or WebApp, Microsoft Azure Migrate Services has a tool for that too :

Assess any app with an endpoint scan. Download the Migration Assistant and start your .NET and PHP app migration to Azure App Service.

Click on Assess

and from here you can plan your migration.

At last when you have to move a big enterprise On-premises Datacenter to the Azure Cloud with a lot of Servers for example 10.000, you can use Azure Data Box Migration
The Microsoft Azure Data Box cloud solution lets you send terabytes of data into Azure in a quick, inexpensive, and reliable way. The secure data transfer is accelerated by shipping you a proprietary Data Box storage device. Each storage device has a maximum usable storage capacity of 80 TB and is transported to your datacenter through a regional carrier. The device has a rugged casing to protect and secure data during the transit.

Azure Data Box

When you want to read more about Microsoft Azure Migrate go to the website.

Microsoft Azure Migrate assessment for VMware platform

First we make the Azure Migrate Project ready in the Microsoft Azure Portal.

Select the right Azure Subscription and Resource group to collect the metadata reported by your On-premises environment. Give your Migrate project a name and select the geography.

Here you can select from different Assessment Tools
Select Azure Migrate Server Assessment

Here you can select from different Migration Tools
Select Azure Migrate Server Migration

Add your Tools in the Azure Portal.

Here you see both Microsoft Azure Migrate tools for the Assessment and the Migration as well.
We are going for the Assessment quick start, so click on discover

From here we select with VMware vShere Hypervisor, so you can download the Azure Migrate Appliance for VMware ( 12GB Ova file).

You can also work with an Import CSV file but that’s Preview.

Now you can download and Install the Azure Migrate Virtual Appliance on VMware.
Follow the instructions here

When you have installed the Microsoft Azure Migrate Virtual Appliance for VMware successfully in your environment and has access to all the Virtual Machines then you can run the setup in the Appliance to make connectivity with your Azure subscription.

This will check all the prerequisites and get the updates.

Getting access to vCenter Server with the right permissions.

Now when your Azure Migrate Virtual Appliance for VMware is ready and collecting metadata, we see in the Microsoft Azure Portal the discovery running :

Discovery is in Progress.

After a view minutes we have discovered the Servers running on VMware platform On-premises.

Discovered Servers

Now we have the Servers in our metadata, we can do the Assessment(s) to get all the information we want for preparing to migrate to Azure Cloud Services. Click on Assess.

From here you give the Assessment a name and then you go to the properties of the assessment by clicking on View All

Here you can set the parameters for the assessment for example based on :

  1. Reserved instances
  2. Storage types
  3. Sizing criterion like Performance-Based
  4. Percentile Utilization
  5. Azure VM series to use
  6. Discount
  7. VM Uptime
  8. Offer pricing like Enterprise Agreement Support or Pay-As-You-Go
  9. Hybrid Benefit offer.

Here I made different Azure Migrate Assessment groups with different parameters to see the difference in Costs.

Here you see for example Migrate As Is On-Premises and Performance-Based, but also an Azure Migrate Assessment without SQL Cluster Nodes. In this way you can make your own Azure Migrate Assessment with all your Servers or just a view Servers of your On-premises solution which you want to Migrate to Azure Cloud Services.

Overview of your Azure Migrate Assessment

Server is ready for migration

 

Server Ready but with conditions

Microsoft Azure Migrate gives you all the information to make the right decisions to migrate you workload from VMware to Microsoft Azure Cloud. When the Azure Migrate Assessment(s) are ready you can make a CSV export file to check the information before you migrate.

Overview of the Azure Migrate Assessment

Azure Migrate Assessment based on Performance for the VM
and there is a separated tab for Storage.

When your assessment is done, you can do the migration by replicating them to Microsoft Azure.

Here you can see the Azure Migrate for VMware (Agentless) steps

More Microsoft Azure Feature resources :

Dependency mapping helps you to visualize dependencies across machines

Setup Agentless Dependency visualization for assessment (Preview) 

Assess the readiness of a SQL Server data estate migrating to Azure SQL Database using the Data Migration Assistant

Conclusion

Microsoft Azure Migrate gives you insight information about your own On-Premises Datacenter by doing assessments to get the right migration information to move to Microsoft Azure Cloud. It gives you Azure Cloud costs before you do any migration at all, based on Total Cost of Owner (TCO) ship you can calculate if your solution in the Microsoft Azure Cloud is cheaper or not. Realize that’s it is not always about the money but also :

  • Innovations
  • Time to market
  • New Features
  • Flexibility
  • Scalability
  • Availability
  • Not owning hardware anymore
  • Less management (Hardware)

Hope this blog post helps you by your transition journey to Microsoft Azure Cloud


Leave a comment

Backup – Restore – DR strategy in a Fast changing World #Data #Management

The world of data is moving and changing a lot with new IT technologies coming up like leaves on a tree.
Data is everywhere, on Servers, workstations, BYOD Devices in the Cloud but how do you keep your data save and protected for your business today and in the future? There are a lot of reasons why you should Backup your data :

  • One of your employees accidentally deleted important files for example.
  • Your data got compromised by a virus.
  • Your Server crashed
  • You have to save your data for a period of time by Law
  •  And there will be more reasons why you should do backup…………….

A lot of Enterprise organizations are moving to the Cloud with workloads for the Business, but how is your Backup and Disaster Recovery managed today? A lot of data transitions are made but what if your Backup and Disaster Recovery solution is out dated or reaching end of Life? You can have a lot of Questions like :

  • What data should I backup?
  • Should I just upgrade the Backup Solution?
  • How can I make my Data Management Backup -DR Solution Cheaper and ready for the future?
  • How can I make my new Backup-DR Solution independent? ( Vendor Lockin)

And there will be more questions when you are in this scenario where you have to renew your Backup – DR Solution.
Here we have the following Great Backup Solution from 2014 :

Offsite Microsoft DPM Backup Solution since 2014

Here we have 3 System Center Data Protection Manager Backup Pods with a Tape library and One DPM pod connected with a Microsoft Azure Backup Vault in the Cloud. You do the Security updates and the Rollups for Windows Server 2012 R2 and System Center Data Protection Manager 2012 to keep the Solution save and running.

Long Time Protection to Tape

DPM 2012 Server with direct attached Storage for Short time protection

The four DPM Backup Pods have the same Storage configuration for short time protection with a retention time of 15 days. After that Longtime protection is needed with Backup to tape and Backup to Microsoft Azure Backup Vault.
Since 2014 the Backup data is depending on these solution configurations.

Tape Management cost a lot of time and money

The fourth DPM Backup pod got a Azure Backup Vault in the Cloud to save Tape Management time.

DPM Backup to Microsoft Azure Cloud Backup Vault.

So this is the Start of the Journey to a New Data Management Backup – DR Solution transformation. The next Couple of weeks I will search for the different scenarios and solutions on the Internet and talk with the Community looking for Best Practices. I will do Polls on Social Media and a Serie of blogposts for the Data Management Backup – DR Solution to keep the business continuity.

Magic Quadrant for Data Center Backup and Recovery Solutions

Will it be a Cloud Backup – DR Solution?
Will it be a Hybrid Cloud Backup – DR Solution?
Everything in One Management Console?
Or More then One Backup -DR Solution for the right Job?

We will see what the journey will bring us based on Best Practices  😉


Leave a comment

Whitepaper Achieving Compliant Data Residency and Security with #Azure #Cloud

Introduction

Security and compliance–basic elements of the trusted cloud–are top priorities for organizations today. This paper is designed to help customers ensure that their data is handled in a manner that meets their data protection, regulatory, and sovereignty requirements on the global cloud architecture of Microsoft Azure. Transparency and control are also essential to establishing and maintaining trust in cloud technology. Microsoft recognizes that restricted and regulated industries require additional details for their risk management and to ensure compliance at all times. Microsoft provides an industry-leading security and compliance portfolio. Security is built into the Azure platform, beginning with the development process, which is conducted in accordance with the Security Development Lifecycle (SDL), and includes technologies, controls and tools that address data management and governance, Active Directory identity and access controls, network and infrastructure security technologies and tools, threat protection, and encryption to protect data in transit and at rest. Microsoft also provides customers with choices to select and limit the types and locations of data storage on Azure. With the innovation of the security and compliance frameworks, customers in regulated industries can successfully run mission-critical workloads in the cloud and leverage all the advantages of the Microsoft hyperscale cloud. This simple approach can assist customers in meeting the data protection requirements of government regulations or company policies by helping them to:

Understand data protection obligations.

Understand the services and controls that Azure provides to help its customers meet those obligations.

Understand the evidence that customers need to assert compliance.

The paper is structured into these three sections, with each diving deeper into the security and technologies that help Microsoft customers to meet data protection requirements. The final section discusses specific requirements to which industries and organizations in selected European markets are subject.

Download this Awesome whitepaper, “Achieving compliant data residency and security with Azure.”

Learn here more on Compliance, Trust, Security and Responsibilities


Leave a comment

#Microsoft System Center Management Pack (CTP) for #SQL Server vNext Replication #Sysctr #SCOM

Microsoft System Center Management Pack (Community Technology Preview) for SQL Server vNext Replication enables the monitoring of Replication as a set of technologies for copying and distributing data and database objects from one database to another and then synchronizing between the databases to maintain consistency.

Here you can download the System Center MP for SQL Server vNext Replication including documentation.