...
Planner Icons |
| |
|---|---|---|
Fit in Bounds | When “Fit In Bounds” is clicked, the entire graph in migration planner is nicely fit with centering. | |
Zoom Out | Zoom out means to make the image look smaller for pinching out. | |
Zoom In | Zoom in means focusing on a particular place on a image to increase its size or make the image look larger by pinching in | |
Collapse all assets | It will collapse the modified/changed assets | |
Clear All | It will clear any mapped dependencies | |
Undo Migration Planner Changes | Will revert the changes made in Migration Planner | |
Application Inventory Settings | By clicking Application Inventory Settings, it will allow us to select the applications that you want to migrate | |
Build Application-Based Move Groups |
| Build Move groups can be built in multiple ways, by default Move groups are built on application categories, the Cloudamize Platform allows for the creation of new groups or assets by creating Application-Based Move Groups. To make adjustments, click on the More Tools button, and select Build-Application Based Move Groups |
Build Machine-Based Move Groups | In addition to Application-Based Move Groups, the Cloudamize Platform allows for the creation of Machine-Based Move Groups To make adjustments, click on the More Tools button, and select Build-Machine Based Move Groups. A new window will open with two sections, the bottom section lists all processes found during the assessment and the top section, is where we will be adding rules for these machines. | |
Advanced Filtering | Advanced Filtering allows you to create move groups based on nearly any metric collected by the Cloudamize platform. | |
Migrate Your environment |
| |
Upload File |
| |
CSV Builder |
| |
CSV Exporter |
| This Option allows us to know how to migrate a set of machines to respective IAAS using Application Migration Service (MGN). After an installation key has been provided, the MGN agent can be downloaded and installed from the Cloudamize application. Machines which are candidates for migration to AWS will then be available in the MGN dashboard. |
Upload File | An option to be used to upload a .CSV file | |
CSV Builder | The Cloudamize CSV Builder allows you to create custom CSV outputs to provide you with the data which is most important to you. You can choose the categories to display as columns in the downloadable CSV output and you can reorder the columns to fit your needs. Select columns based on machine-centric data such as observed and recommended number of CPU threads, allocated memory, operating system, and many more and the templates can also be created based on application-centric data such as the application category, description, vendor, process, etc. | |
CSV Exporter | This option lets you create a custom template by using an option of drop-down list to select a plan and to apply to the data in the selected templates | |
SQL Server and License Usage |
| |
Migration Planner Table |
| |
NameUsing the Migration Planner, Cloudamize now provides a more in-depth look at the SQL Servers found in the assessed infrastructure. The information provided within the SQL Server and License Usage machine allows you to gain further insight into the on-premise licensing data and view a comparison of host-based versus VM-based SQL licensing. This feature also provides an overview of necessary on-cloud SQL licensing. |
Migration Planner Table | |
|---|---|
Number Of Nodes | The number of nodes in an asset. |
Number Of Communicating Apps | The number of communicating unique applications in an asset. This app can be a client or server app. |
Number Of Inter-Communicating Clients | The number of inter-communicating client nodes in other assets to a server node in this asset. Note that this is a node-level, not an app-level. This shows how many client nodes in other assets communicate to this asset. |
Number Of Inter-Communicating Servers | The number of inter-communicating server nodes in other assets from a client node in this asset. Note that this is a node-level, not an app-level. This shows how many server nodes in other assets are communicated by this asset. |
Number Of Proprietary Apps | The number of proprietary applications. Seems not supported |
Number Of Specialized Apps | The number of specialized applications. Seems not supported |
Number Of Autoscalable Nodes | The number of auto-scalable nodes where node does not run SQL server and the CPU utilization performance is suitable for auto-scaling. |
Number Of Nodes Suitable For GP-SSD | he number of nodes where disk IOPS performance are bursty and suitable for GP-SSD. |
Number Of Nodes Suitable For The t2 Family | The number of nodes where the recommended instance type is t2 family. |
Suitable Instance Types Are Available | The recommended instance type meets the performance requirement with CPU and memory workload. |
Migration Planner Table |
|
|---|---|
Number Of Nodes |
The number of nodes in an asset. |
Number Of Communicating Apps |
The number of communicating unique applications in an asset. This app can be a client or server app. |
Number Of Inter-Communicating Clients |
The number of inter-communicating client nodes in other assets to a server node in this asset. Note that this is a node-level, not an app-level. This shows how many client nodes in other assets communicate to this asset. |
Number Of Inter-Communicating Servers |
The number of inter-communicating server nodes in other assets from a client node in this asset. Note that this is a node-level, not an app-level. This shows how many server nodes in other assets are communicated by this asset. |
Number Of Proprietary Apps |
The number of proprietary applications. Seems not supported |
Number Of Specialized Apps |
The number of specialized applications. Seems not supported |
Number Of Autoscalable Nodes |
The number of auto-scalable nodes where node does not run SQL server and the CPU utilization performance is suitable for auto-scaling. |
Number Of Nodes Suitable For GP-SSD |
he number of nodes where disk IOPS performance are bursty and suitable for GP-SSD. |
Number Of Nodes Suitable For The t2 Family |
The number of nodes where the recommended instance type is t2 family. |
Suitable Instance Types Are Available |
...
The recommended instance type meets the performance requirement with CPU and memory workload. |