Skip to content

Commit 7cd9cae

Browse files
authored
Merge pull request #269316 from MaryMichael-MS/18MarLatest
Incorporated peer review comments.
2 parents acf1230 + adb9338 commit 7cd9cae

File tree

5 files changed

+25
-23
lines changed

5 files changed

+25
-23
lines changed
1.96 KB
Loading
-4.43 KB
Loading
282 Bytes
Loading

articles/migrate/tutorial-assess-sap-systems.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.custom:
1313

1414
# Tutorial: Assess SAP systems for migration to Azure (preview)
1515

16-
As part of your migration journey to Azure, assess which environment on Azure meets the needs of your on-premises SAP inventory and workloads.
16+
As part of your migration journey to Azure, assess the appropriate environment on Azure that meets the needs of your on-premises SAP inventory and workloads.
1717

1818
This tutorial explains how to perform assessments for your on-premises SAP systems using import option for Discovery. This assessment helps to generate an assessment report, featuring cost, and sizing recommendations based on cost and performance.
1919

@@ -36,7 +36,7 @@ Before you get started, ensure that you've:
3636
> [!NOTE]
3737
> - If you want to try this feature in an existing project, ensure you are currently within the same project.
3838
> - If you want to create a new project for assessment, [create a new project](./create-manage-projects.md#create-a-project-for-the-first-time).
39-
> - For SAP discovery and assessment to be accessible, you must create the project in either the Asia or United States geographies. The location selected for the project **doesn't limit** the target regions that you can select in the assessment settings, see [Create an assessment](#create-an-assessment). You can select any Azure region as the target for your assessments.
39+
> - For SAP discovery and assessment to be accessible, you must create the project either in the Asia or United States geographies. The location selected for the project **doesn't limit** the target regions that you can select in the assessment settings, see [Create an assessment](#create-an-assessment). You can select any Azure region as the target for your assessments.
4040
4141

4242
## Create an assessment
@@ -56,9 +56,11 @@ To create an assessment for the discovered SAP systems, follow these steps:
5656
1. On **Edit settings** page, do the following:
5757
1. **Target settings**:
5858
1. **Primary location**: Select Azure region to which you want to migrate. Azure SAP systems configuration and cost recommendations are based on the location that you specify.
59-
1. **Is Disaster Recovery (DR) Environment required?**: Select **Yes** to enable Disaster Recovery (DR) for your SAP systems.
59+
1. **is Disaster Recovery (DR) Environment required?**: Select **Yes** to enable Disaster Recovery (DR) for your SAP systems.
6060
1. **Disaster Recovery (DR) location**: Select DR location if DR is enabled.
6161

62+
:::image type="content" source="./media/tutorial-assess-sap-systems/target-settings-edit.png" alt-text="Screenshot that shows the fields in target settings." lightbox="./media/tutorial-assess-sap-systems/target-settings-edit.png":::
63+
6264
1. **Pricing settings**:
6365
1. **Currency**: Select the currency you want to use for cost view in assessment.
6466
1. **OS license**: Select the OS license.
@@ -76,18 +78,18 @@ To create an assessment for the discovered SAP systems, follow these steps:
7678
:::image type="content" source="./media/tutorial-assess-sap-systems/availability-settings-edit.png" alt-text="Screenshot that shows the fields in availability settings." lightbox="./media/tutorial-assess-sap-systems/availability-settings-edit.png":::
7779

7880
1. **Environment uptime**: Select the uptime % and sizing criteria for the different environments in your SAP estate.
79-
1. **Storage settings (non hana only)**, if you intend to conduct the assessment for Non-HANA DB, select from the available storage settings.
81+
1. **Storage settings (non hana only)**: if you intend to conduct the assessment for Non-HANA DB, select from the available storage settings.
8082
1. Select **Save**.
8183

8284
## Run an assessment
8385

84-
To run the assessment, follow these steps:
86+
To run an assessment, follow these steps:
8587

8688
1. Navigate to the **Create assessment** page and select **Review + create assessment** tab to review your assessment settings.
8789
1. Select **Create assessment**.
8890

8991
> [!NOTE]
90-
> Assessments typically take approximately 5-10 minutes to complete. Wait for 5 to 10 minutes after clicking on **Create assessment**. Then, refresh the page and check if the assessment computation has been completed.
92+
> Assessments take approximately 5-10 minutes to complete. We recommend you to wait for 5 to 10 minutes after you select **Create assessment**. Refresh the page and check if the assessment computation is completed.
9193
9294
## Review an assessment
9395

@@ -98,7 +100,7 @@ To review an assessment, follow these steps:
98100

99101
:::image type="content" source="./media/tutorial-assess-sap-systems/review-assess.png" alt-text="Screenshot that shows the option to access assess." lightbox="./media/tutorial-assess-sap-systems/review-assess.png":::
100102

101-
1. On the **Assessments** page, select a desired assessment name that you wish to view from the list of assessments. <br/>On the **Overview** page, you can view the SAP system details of **Essentials**, **Assessed entities** and **SAP® on Azure** cost estimates.
103+
1. On the **Assessments** page, select a desired assessment name to view from the list of assessments. <br/>On the **Overview** page, you can view the SAP system details of **Essentials**, **Assessed entities** and **SAP® on Azure** cost estimates.
102104
1. Select **SAP on Azure** for the drill-down assessment details at the System ID (SID) level.
103105
1. On the **SAP on Azure** page, select any SID to review the assessment summary such as cost of the SID, including its ASCS, App, and DB server assessments and storage details for the DB server assessments. <br/>If required, you can edit the assessment properties or recalculate the assessment.
104106

articles/migrate/tutorial-discover-sap-systems.md

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.custom:
1111

1212
---
1313

14-
# Tutorial: Discover SAP systems with Azure Migrate: Discovery and Assessment (preview)
14+
# Tutorial: Discover SAP systems with Azure Migrate (preview)
1515

1616
As part of your migration journey to Azure, discover your on-premises SAP inventory and workloads.
1717

@@ -21,8 +21,9 @@ In this tutorial, you learn how to:
2121

2222
> [!div class="checklist"]
2323
> * Set up an Azure Migrate project
24-
> * Prepare an import file
25-
> * Import the server inventory and perform an assessment
24+
> * Prepare the import file
25+
> * Import the SAP systems inventory
26+
> * View discovered SAP systems
2627
2728
> [!NOTE]
2829
> Tutorials show the quickest path for trying out a scenario and using default options.
@@ -43,7 +44,7 @@ To set up a migration project, follow these steps:
4344
2. **Region**: Select the region in which you want to create the project.
4445

4546
> [!Note]
46-
> In the **Advanced** configuration, the default connectivity is set to public endpoint. You can also create an Azure Migrate project with private endpoint connectivity. [Learn more](discover-and-assess-using-private-endpoints.md#create-a-project-with-private-endpoint-connectivity)
47+
> In the **Advanced** configuration, the default connectivity is set to public endpoint. You can also create an Azure Migrate project with private endpoint connectivity. [Learn more.](discover-and-assess-using-private-endpoints.md#create-a-project-with-private-endpoint-connectivity)
4748
4849
1. Select **Create**.
4950

@@ -56,7 +57,6 @@ To set up a migration project, follow these steps:
5657
To prepare the import file, do the following:
5758
1. Download the template file.
5859
1. Add on-premises SAP infrastructure details.
59-
1. Import SAP Systems inventory.
6060

6161
### Download the template file
6262

@@ -86,36 +86,36 @@ The following table summarizes the file fields to fill in:
8686

8787
| **Template Column** | **Description** |
8888
| --- | --- |
89-
| Server Name <sup>*</sup> | Unique server name or host name of the SAP system to identify each server. Include all the virtual machines attached to an SAP system that you intend to migrate to Azure. |
89+
| Server Name <sup>*</sup> | Unique server name or host name of the SAP system to identify each server. Include all the virtual machines attached to a SAP system that you intend to migrate to Azure. |
9090
| Environment <sup>*</sup> | Environment that the server belongs to. |
9191
| SAP Instance Type <sup>*</sup> | The type of SAP instance running on this machine. <br/>For example, App, ASCS, DB, and so on. Single-server and distributed architectures are only supported. |
92-
| Instance SID <sup>*</sup> | This is the instance System ID (SID) for the ASCS/AP/DB instance. |
92+
| Instance SID <sup>*</sup> | Instance System ID (SID) for the ASCS/AP/DB instance. |
9393
| System SID <sup>*</sup> | SID of SAP System. |
9494
| Landscape SID <sup>*</sup> | SID of the customer's production system in each landscape. |
95-
| Application <sup>*</sup> | Optional column to specify any organizational identifier, such as HR, Finance, Marketing, and so on. |
95+
| Application <sup>*</sup> | Any organizational identifier, such as HR, Finance, Marketing, and so on. |
9696
| SAP Product <sup>*</sup> | SAP application component. <br/>For example, SAP S/4HANA 2022, SAP ERP ENHANCE, and so on. |
9797
| SAP Product Version | The version of the SAP product. |
9898
| Operating System <sup>*</sup> | The operating system running on the host server. |
99-
| Database Type <sup>*</sup> | This column is applicable only if **SAP Instance Type** column is **Database**. |
99+
| Database Type | Optional column and it is not applicable for all SAP Instance Types except **Database**.|
100100
| SAPS* | The SAP Application Performance Standard (SAPS) for each server in the SAP system. |
101101
| CPU | The number of CPUs on the on-premises server. |
102102
| Max. CPUload[%] | The maximum CPU load in percentage of the on-premises server. Exclude the percentage symbol while you enter this value. |
103-
| RAM Size (GB) | RAM size in GB of the on-premises server. |
103+
| RAM Size (GB) | RAM size of the on-premises server. |
104104
| CPU Type | CPU type of the on-premises server.<br/> For example, Xeon Platinum 8171M, and Xeon E5-2673 v3. |
105105
| HW Manufacturer | The manufacturer company of the on-premises server. |
106106
| Model | The on-premises hardware is either a physical server or virtual machine. |
107107
| CPU Mhz | The CPU clock speed of the on-premises server. |
108108
| Total Disk Size(GB) <sup>*</sup> | Total disk volume capacity of the on-premises server. Include the disk volume for each individual disk and provide the total sum. |
109109
| Total Disk IOPS <sup>*</sup> | Total disk Input/Output Operations Per Second (IOPS) of all the disks on the on-premises server. |
110110
| Source DB Size(GB) <sup>*</sup> | The size of on-premises database. |
111-
| Target HANA RAM Size(GB) | This is an optional field and is **Not Applicable** for all SAP Instance Types except **DB**. Fill this field only when migrating an AnyDb database to SAP S/4HANA and provide the desired target HANA database size. |
111+
| Target HANA RAM Size(GB) | Optional column and it is **Not Applicable** for all SAP Instance Types except **DB**. Fill this field only when migrating an AnyDb database to SAP S/4HANA and provide the desired target HANA database size. |
112112

113113
<sup>*</sup> These fields are mandatory.
114114

115-
### Import SAP Systems inventory
115+
## Import SAP systems inventory
116116
After you add information to the import file, import the file from your machine to Azure Migrate.
117117

118-
To import SAP Systems inventory, follow these steps:
118+
To import SAP systems inventory, follow these steps:
119119

120120
1. On the **Azure Migrate** page, under **Migration goals**, select **Servers, databases and web apps**.
121121
1. On the **Servers, databases and web apps** page, under **Assessments tools**, from the **Discover** dropdown menu, select **Using import**.
@@ -124,9 +124,9 @@ To import SAP Systems inventory, follow these steps:
124124

125125
:::image type="content" source="./media/tutorial-discover-sap-systems/import-excel.png" alt-text="Screenshot that shows how to import SAP inventory." lightbox="./media/tutorial-discover-sap-systems/import-excel.png":::
126126

127-
Review the import details to check for any errors or validation failures. After the successful import, you can view the discovered SAP systems.
127+
Review the import details to check for any errors or validation failures. After a successful import, you can view the discovered SAP systems.
128128
> [!Note]
129-
> After completing a discovery import, we recommend you wait for 15 minutes before starting a new assessment. This ensures that all Excel data is accurately used during the assessment calculation.
129+
> After you complete a discovery import, we recommend you to wait for 15 minutes before you start a new assessment. This ensures that all Excel data is accurately used during the assessment calculation.
130130
131131
## View discovered SAP systems
132132

@@ -136,7 +136,7 @@ To view the discovered SAP systems, follow these steps:
136136

137137
:::image type="content" source="./media/tutorial-discover-sap-systems/discovered-systems.png" alt-text="Screenshot that shows discovered SAP inventory." lightbox="./media/tutorial-discover-sap-systems/discovered-systems.png":::
138138

139-
1. On the **Discovered SAP® systems** page, select a desired system SID.<br> The **Server instance details** blade displays all attributes of servers that make up the SID.
139+
1. On the **Discovered SAP® systems** page, select a desired system SID.<br> The **Server instance details** blade displays all the attributes of servers that make up the SID.
140140

141141
> [!Note]
142142
> Wait for 10 minutes and ensure that the imported information is fully reflected in the **Server instance details** blade.

0 commit comments

Comments
 (0)