Discovery
and Assessment Tools for Migration to Azure
There are so many tools available for Discovery and
Assessment prior to Migration or First phase of Migration as we all know,
Migration to cloud or any general migration goes through 4 phase :
Assess – Discover
the current assets and check the suitability for migration to Azure
Migrate – Actual
migration of data, apps and objects to Azure
Optimize –
Streamlining of resources for max performance and efficiency after Migration.
Secure and Manage
– Once above 3 phase completed successfully we use Azure resources like
security center, Azure Advisor etc to govern, secure and monitor cloud apps in
Azure.
In this article, we will be discussing Deployment planner
and Azure Migrate. Which are well known and provide detailed analysis and
presentable chart that too free of cost. Let’s start Deployment Planner in this
article and in next article we will discuss Azure Migrate.
Deployment
Planner
Deployment Planner is a command line tool available for both
Hyper-V or VMware to Azure disaster recovery or Migration process. This tool is
used to profile VM’s with no production Impact to understand the Bandwidth and
Azure storage requirements for successful replication and test failover. As per
MS recommendation this planned should be deployed on a server that meets minimum
requirements of the Site Recovery Configuration server. This tool can be run
without installing any site recovery components on-premises.
Configuration/Process server
requirements
|
|
Component
|
Requirement
|
HARDWARE
SETTINGS
|
|
CPU
cores
|
8
|
RAM
|
16
GB
|
Number
of disks
|
3,
including the OS disk, process server cache disk, and retention drive for
failback
|
Free
disk space (process server cache)
|
600
GB
|
Free
disk space (retention disk)
|
600
GB
|
SOFTWARE
SETTINGS
|
|
Operating
system
|
Windows
Server 2012 R2
|
Windows
Server 2016
|
|
Operating
system locale
|
English
(en-us)
|
Windows
Server roles
|
Don't
enable these roles:
|
-
Active Directory Domain Services
|
|
-
Internet Information Services
|
|
-
Hyper-V
|
|
Group
policies
|
Don't
enable these group policies:
|
-
Prevent access to the command prompt.
|
|
-
Prevent access to registry editing tools.
|
|
-
Trust logic for file attachments.
|
|
IIS
|
-
No preexisting default website
|
-
No preexisting website/application listening on port 443
|
|
NETWORK
SETTINGS
|
|
IP
address type
|
Static
|
Internet
access
|
The
server needs access to these URLs (directly or via proxy):
|
-
*.accesscontrol.windows.net
|
|
-
*.backup.windowsazure.com
|
|
-
*.store.core.windows.net
|
|
-
*.blob.core.windows.net
|
|
-
*.hypervrecoverymanager.windowsazure.com
|
|
-
https://management.azure.com
|
|
-
*.services.visualstudio.com
|
|
-
time.nist.gov
|
|
-
time.windows.com
|
|
OVF
also needs access to the following URLs:
|
|
-
https://login.microsoftonline.com
|
|
-
https://secure.aadcdn.microsoftonline-p.com
|
|
-
https://login.live.com
|
|
-
https://auth.gfx.ms
|
|
-
https://graph.windows.net
|
|
-
https://login.windows.net
|
|
-
https://www.live.com
|
|
-
https://www.microsoft.com
|
|
-
https://dev.mysql.com/get/Downloads/MySQLInstaller/mysql-installer-community-5.7.20.0.msi
|
|
Ports
|
443
(Control channel orchestration)
|
9443
(Data transport)
|
|
NIC
type
|
VMXNET3
(if the Configuration Server is a VMware VM)
|
SOFTWARE
TO INSTALL
|
|
VMware
vSphere PowerCLI
|
|
MYSQL
|
MySQL
should be installed. You can install manually, or Site Recovery can install
it.
|
Configuration/Process server sizing
requirements
|
||||
CPU
|
Memory
|
Cache
disk
|
Data
change rate
|
Replicated
machines
|
8
vCPUs
|
16GB
|
300
GB
|
500
GB or less
|
<
100 machines
|
2
sockets * 4 cores @ 2.5 GHz
|
||||
12
vCPUs
|
18
GB
|
600
GB
|
500
GB-1 TB
|
100
to 150 machines
|
2
socks * 6 cores @ 2.5 GHz
|
||||
16
vCPUs
|
32
GB
|
1
TB
|
1-2
TB
|
150
-200 machines
|
2
socks * 8 cores @ 2.5 GHz
|
Above details captured from MS Docs, Please refer below
article for latest information:
Deployment
Planner Tool Provides following details :-
Compatibility assessment
·
A VM eligibility assessment, based on number of
disks, disk size, IOPS, churn, boot type(EFI/BIOS), and OS version
Network bandwidth need versus RPO assessment
·
The estimated network bandwidth that’s required
for delta replication
·
The throughput that Site Recovery can get from
on-premises to Azure
·
The number of VMs to batch, based on the
estimated bandwidth to complete initial replication in a given amount of time
·
RPO that can be achieved for a given bandwidth
·
Impact on the desired RPO if lower bandwidth is
provisioned.
Azure infrastructure requirements
·
The storage type (standard or premium storage
account) requirement for each VM
·
The total number of standard and premium storage
accounts to be set up for replication
·
Storage-account naming suggestions, based on
Azure Storage guidance
·
The storage-account placement for all VMs
·
The number of Azure cores to be set up before
test failover or failover on the subscription
·
The Azure VM-recommended size for each
on-premises VM
On-premises infrastructure requirements
·
The required number of configuration servers and
process servers to be deployed on-premises
Estimated DR cost to Azure
·
Estimated total DR cost to Azure: compute,
storage, network, and Azure Site Recovery license cost
·
Detail cost analysis per VM
Steps to
Configure Deployment Planner:
Step 1 – Create a list of VMs to profile
Launch the VMware vSphere PowerCLI and run the
following commands: –
Add-PSSnapin VMware.VimAutomation.Core
Connect-VIServer -Server 1.1.1.1 -User
domain\username -Password <password>
Get-VM | Select Name | Sort-Object -Property
Name > C:\<File_Path>\outputfile.txt - All VMs
attached to the vCenter server are exported to the text file
Step 2 – Profile VMs
Open PowerShell and navigate to the path where
the ASRDP is ‘installed’. Run the following command substituting the server
FQDN/IP Address & username as required.
.\ASRDeploymentPlanner.exe -Operation
StartProfiling -Virtualization VMware -Directory “C:\Binaries\Profiled_Data”
-Server 1.1.1.1 -VMListFile
“C:\Binaries\Profiled_Data\ProfileVMList1.txt” -NoOfMinutesToProfile
30 -User domain\xyz
Step 3 – Generate Reports
.\ASRDeploymentPlanner.exe -Operation GenerateReport
-Virtualization VMware -Server 1.1.1.1 -Directory “C:\Binaries\Profiled_Data”
-VMListFile “C:\Binaries\Profiled_Data\ProfileVMList1.txt”
thanks for sharing !!
ReplyDelete