Merge pull request #268307 from b-ahibbard/avg-extension-one

AVG extension one

Author: v-dirichards

articles/azure-netapp-files/application-volume-group-add-hosts.md

@@ -1,6 +1,6 @@
 ---
 title: Add hosts to a multiple-host SAP HANA system using Azure NetApp Files application volume group for SAP HANA | Microsoft Docs
-description: Describes how to add additional HANA hosts after you have created the first host in an SAP HANA multiple-host setup.
+description: Describes how to add more HANA hosts after you've created the first host in an SAP HANA multiple-host setup.
 services: azure-netapp-files
 author: b-hchen
 ms.service: azure-netapp-files
@@ -10,60 +10,62 @@ ms.author: anfdocs
 ---
 # Add hosts to a multiple-host SAP HANA system using application volume group for SAP HANA
 
-Building a multiple-host SAP HANA database always starts with creating a volume group for the first host. You need to have created the first host in an SAP HANA multiple-host setup (see [Deploy the first SAP HANA host](application-volume-group-deploy-first-host.md)). After that, you can add additional HANA hosts by following steps in this article. 
+Building a multiple-host SAP HANA database always starts with creating a volume group for the first host. To begin, you must create the first host in an SAP HANA multiple-host setup (see [Deploy the first SAP HANA host](application-volume-group-deploy-first-host.md)). After that, you can add additional HANA hosts by following steps in this article. 
 
 > [!IMPORTANT]
 > SAP recommends that you size the HANA shared volume to 1 x RAM of a HANA host for every four SAP HANA hosts of a multiple-host SAP HANA database. You might need to adjust the size for the shared volume you created with the initial host to adapt for the required capacity.
 
 ## Steps
 
-1. From your NetApp account, select **Application volume groups**, and click **+Add Group**.  Then in Deployment Type, select **SAP HANA** and click **Next**.   
+1. From your NetApp account, select **Application volume groups**, and select **+Add Group**. In Deployment Type, select **SAP HANA** then **Next**.   
 
 2. In the **SAP HANA** tab for adding a volume group, specify the following information:  
 
     * **SAP ID (SID)**:    
         The three alphanumeric-character SAP HANA system identifier.
     * **Group name**:  
-        The volume group name. For a multiple-host SAP HANA, each host will create its own group.   
-        In the example screenshot below, the group name `SAP-HANA-SH9-{HostId}` is a generic name. `{HostId}` will be replaced with the corresponding numeric host ID for each host you add. `{HostId}` will also be replaced with the numeric host ID for the volume group description. If `{HostId}` is not specified, it is appended to the end for both the group name and description.
+        The volume group name. For a multiple-host SAP HANA, each host creates its own group.   
+        In the example screenshot below, the group name `SAP-HANA-SH9-{HostId}` is a generic name. The corresponding numeric host ID for each host you add replaces `{HostId}`. Also, the numeric host ID for the volume group description replaces `{HostId}`. If `{HostId}` isn't specified, it's appended to the end for both the group name and description.
     * **SAP node memory**:   
-        This value defines the size of the SAP HANA database on the host. It is used to calculate the required volume size and throughput. 
+        This value defines the size of the SAP HANA database on the host and used to calculate the required volume size and throughput. 
     * **Capacity overhead (%)**:   
-        When you use snapshots for data protection, you need to plan for extra capacity. This field will add an additional size (%) for the data volume.  
+        When you use snapshots for data protection, you need to plan for extra capacity. This field adds a size (%) for the data volume.  
         You can estimate this value by using `"change rate per day" X "number of days retention"`.
     * **Multiple-host**:   
-        Select this option to add additional hosts to a multiple-host HANA.
+        Select this option to add more hosts to a multiple-host HANA.
     * **First host ID**:   
-        Specify the number of the first host you want to add. This value is typically "2" if you are adding hosts for the first time.
+        Specify the number of the first host you want to add. This value is typically "2" if you're adding hosts for the first time.
     * **Host count**:   
         Specify the number of hosts you want to add to the multiple-host setup.
 
-    Click **Next: Volume Group**.
+    Select **Next: Volume Group**.
 
     [ ![Screenshot that shows the HANA section for adding hosts.](./media/application-volume-group-add-hosts/application-multiple-hosts-sap-hana.png) ](./media/application-volume-group-add-hosts/application-multiple-hosts-sap-hana.png#lightbox)
 
 3. In the **Volume group** tab, provide identical input as you did when you created the first HANA host.  
 
-    Then click **Next** and continue through the **Protocol** and **Tags** sections, providing the same input as the first HANA host. (See Step 4 through Step 6 in [Deploy the first SAP HANA host](application-volume-group-deploy-first-host.md).)   
+    Select **Next** and continue through the **Protocol** and **Tags** sections, providing the same input as the first HANA host. (See Step 4 through Step 6 in [Deploy the first SAP HANA host](application-volume-group-deploy-first-host.md).)   
 
-    Click **Next: Volumes** when you reach the end of the sections. 
+    [!INCLUDE [Extension 1 interface call-out](./includes/extension-one.md)]
 
-    For additional hosts that you add, only the data and the log volumes will be created. The **Volumes** page displays the two volumes in a generic form, using the `{HostId}` as a placeholder. This process simplifies the workflow, because changes are made only once for the data and log volumes for all the hosts that are being created.
+    Select **Next: Volumes** when you reach the end of the sections. 
+
+    For hosts that you add, only the data and the log volumes are created. The **Volumes** page displays the two volumes in a generic form, using the `{HostId}` as a placeholder. This process simplifies the workflow, because changes are made only once for the data and log volumes for all the hosts that are being created.
 
     > [!NOTE]
     > SAP HANA allows you to add different compute volume types to a multiple-host setup. If you use this setup, you should add only one host for the same compute type at one time.
 
-    Click **Next: Review + Create**.  
+    Select **Next: Review + Create**.  
 
     [ ![Screenshot that shows the Volumes section for adding hosts.](./media/application-volume-group-add-hosts/application-multiple-hosts-volumes.png) ](./media/application-volume-group-add-hosts/application-multiple-hosts-volumes.png#lightbox)
 
 4. In the **Review + Create** tab, the `{HostId}` placeholder is replaced with the individual numbers for each of the volume groups that will be created. 
 
-    You can click **Next Group** to navigate through all volume groups that are being created (one for each host). You can also click a particular volume to view its details.
+    You can select **Next Group** to navigate through all volume groups that are being created (one for each host). You can also select a particular volume to view its details.
 
     [ ![Screenshot that shows the Review and Create section for adding hosts.](./media/application-volume-group-add-hosts/application-multiple-review-create.png) ](./media/application-volume-group-add-hosts/application-multiple-review-create.png#lightbox)
 
-5. After you navigate through the volume groups, click **Create All Groups** to create all the volumes for the HANA hosts you are adding. 
+5. After you navigate through the volume groups, select **Create All Groups** to create all the volumes for the HANA hosts you're adding. 
 
     [ ![Screenshot that shows the Create All Groups button.](./media/application-volume-group-add-hosts/application-multiple-create-groups.png) ](./media/application-volume-group-add-hosts/application-multiple-create-groups.png#lightbox)
 

articles/azure-netapp-files/application-volume-group-add-volume-secondary.md

@@ -25,15 +25,19 @@ The following diagram illustrates the concept of HSR:
  ![Diagram that explains HANA System Replication.](./media/application-volume-group-add-volume-secondary/application-hana-system-replication.png) 
 
 
-To enable HSR, the configuration of the secondary SAP HANA system must be identical to the primary SAP HANA system. That is, if the primary system is a single-host HANA system, then the secondary SAP HANA system also needs to be a single-hosts system. The same applies for multiple host systems.
+To enable HSR, the configuration of the secondary SAP HANA system must be identical to the primary SAP HANA system. That is, if the primary system is a single-host HANA system, then the secondary SAP HANA system also needs to be a single-host system. The same applies for multiple host systems.
 
 The workflow for creating a secondary SAP HANA system is similar to the workflow for creating the primary SAP HANA system. However, a key difference is that you need to select the **HSR secondary** option in the SAP HANA tab to indicate that you are creating a replication secondary system for the SAP HANA system.
 
 ## Steps
 
 This section shows an example of creating a single-host, secondary SAP HANA system.
 
-1. From your NetApp account, select **Application volume groups**, and click **+Add Group**. Then, in Deployment Type, select **SAP HANA** and click **Next**. 
+[!INCLUDE [Extension 1 interface call-out](./includes/extension-one.md)]
+
+### [Without Extension 1](#tab/without-extension-one)
+
+1. From your NetApp account, select **Application volume groups**, and select **+Add Group**. In Deployment Type, select **SAP HANA** then **Next**. 
 
 2. In the **SAP HANA** tab, provide HANA-specific information. 
 
@@ -58,7 +62,7 @@ This section shows an example of creating a single-host, secondary SAP HANA syst
 
         Selecting **HSR secondary** also triggers the naming convention for the volume group name to include `"-HA-"` to indicate the HA setup.   
 
-    Click **Next: Volume Group** to continue.
+    Select **Next: Volume Group** to continue.
 
     [ ![Screenshot that shows the HANA section in HSR configuration.](./media/application-volume-group-add-volume-secondary/application-secondary-sap-hana.png) ](./media/application-volume-group-add-volume-secondary/application-secondary-sap-hana.png#lightbox)
 
@@ -74,11 +78,11 @@ This section shows an example of creating a single-host, secondary SAP HANA syst
     * **Subnet**:  
         Specify the delegated subnet where the IP addresses for the NFS exports will be created. Ensure that you have a delegated subnet with enough free IP addresses.
 
-    Click **Next: Protocol**.
+    Select **Next: Protocol**.
 
 4. In the **Protocols** section of the Volume Group tab, you can modify the **Export Policy**, which should be common to all volumes.  
 
-    Click **Next: Tags**.
+    Select **Next: Tags**.
 
 5. Because the **HSR secondary** option is selected, the **Tags** section of the Volume Group tab is populated with the tag `HSRPartnerStorageResourceId`. 
 
@@ -89,7 +93,7 @@ This section shows an example of creating a single-host, secondary SAP HANA syst
     > [!IMPORTANT]
     > At the group level, filling the tag will populate all the volumes in the group with the same volume ID. You will need to change the volume ID for each individual volume later in the workflow or when you update the volumes. Using this tag is optional; it’s for documentation purposes only.
 
-    Click **Next: Volumes**.
+    Select **Next: Volumes**.
 
     [ ![Screenshot that shows the Tags section of the Volume Group tab.](./media/application-volume-group-add-volume-secondary/application-secondary-volume-group-tags.png) ](./media/application-volume-group-add-volume-secondary/application-secondary-volume-group-tags.png#lightbox)
 
@@ -105,9 +109,101 @@ This section shows an example of creating a single-host, secondary SAP HANA syst
 
     [ ![Screenshot that shows the tag details.](./media/application-volume-group-add-volume-secondary/application-secondary-volumes-tag-details.png) ](./media/application-volume-group-add-volume-secondary/application-secondary-volumes-tag-details.png#lightbox)
 
-    Click **Volumes** to return to the Volumes overview page.  
+    Select **Volumes** to return to the Volumes overview page.  
+
+8. Select **Review + Create** to list all volumes that will be created. Select **Create Volume Group** to start the volume group creation. 
+
+
+### [Extension 1](#tab/extension-1)
+
+1. From your NetApp account, select **Application volume groups**, and select **+Add Group**. In Deployment Type, select **SAP HANA** then **Next**. 
+
+2. In the **SAP HANA** tab, provide HANA-specific information. 
+
+    > [!IMPORTANT]
+    > Be sure to select the **HSR secondary** option to indicate that you are creating a replication secondary system for the HANA system.  
+
+    * **SAP ID (SID)**:   
+        The three alphanumeric-character SAP HANA system identifier.
+    * **Group name**:  
+        The volume group name. 
+    * **SAP node memory**:  
+        This value defines the size of the SAP HANA database on the host. It is used to calculate the required volume size and throughput. 
+    * **Capacity overhead (%)**:  
+        When you use snapshots for data protection, you need to plan for extra capacity. This field will add additional size (%) for the data volume.  
+        You can estimate this value by using `"change rate per day" X "number of days retention"`.
+    * **Single-host**:  
+        Select this option for an SAP HANA single-host system or the first host for a multiple-host system. Shared and backup volumes can be created only with the first host.
+    * **Multiple-host**:  
+        Select this option to add additional hosts to a multiple-hosts HANA system.
+    * **HSR secondary**:  
+        Select this option to create a HANA database that will be a replication secondary system for SAP HANA System Replication (HSR).
+
+        Selecting **HSR secondary** also triggers the naming convention for the volume group name to include `"-HA-"` to indicate the HA setup.   
+
+    Select **Next: Volume Group** to continue.
+
+    [ ![Screenshot that shows the HANA section in HSR configuration.](./media/application-volume-group-add-volume-secondary/application-secondary-sap-hana.png) ](./media/application-volume-group-add-volume-secondary/application-secondary-sap-hana.png#lightbox)
+
+3.	In the **Volume group** tab, provide information for creating the volume group:  
+
+    * **Availability option**:
+        Select either **Availability zone** or **Proximity placement group**. 
+        When selecting **Availability zone**, you must select the appropriate availability zone in the next field. 
+        * **Proximity placement group (PPG)**:  
+            Specifies that the data, log, and shared volumes are to be created close to the VMs.
+        * **Availability Zone**: 
+            This option lets you deploy the volumes in the logical availability zone that you specify. Select an availability zone where Azure NetApp Files resources are present. For details, see [Manage availability zone volume placement](manage-availability-zone-volume-placement.md).
+    * **Network features**: 
+        Standard network features is the default, however you can still use Basic network features. 
+        See [Configure network features for a volume](configure-network-features.md) and [Guidelines for Azure NetApp Files network planning](azure-netapp-files-network-topologies.md) for details.
+    * **Capacity pool**:  
+        All volumes are placed in a single manual QoS capacity pool. 
+        If you want to create the log-backup and data-backup volumes in a separate capacity pool, you can choose not to add those volumes to the volume group.
+    * **Virtual network**:  
+        Specify an existing VNet where the VMs are placed. 
+    * **Subnet**:  
+        Specify the delegated subnet where the IP addresses for the NFS exports are created. Ensure that you have a delegated subnet with enough free IP addresses.
+    
+    Select **Next: Protocol**.
+
+    :::image type="content" source="./media/application-volume-group-add-volume-secondary/application-volume-group-create-extension-one.png" alt-text="Screenshot of create application volume group interface for extension one." lightbox="./media/application-volume-group-add-volume-secondary/application-volume-group-create-extension-one.png":::
+
+4. In the **Protocols** section of the Volume Group tab, you can modify the **Export Policy**, which should be common to all volumes.  
+
+    Select **Next: Tags**.
+
+5. Because the **HSR secondary** option is selected, the **Tags** section of the Volume Group tab is populated with the tag `HSRPartnerStorageResourceId`. 
+
+    This tag marks the volume resource ID of the corresponding primary volume in the HSR setup, so that the primary volume can be identified for each secondary volume that will be created. 
+
+    You can modify this tag for each volume. 
+
+    > [!IMPORTANT]
+    > At the group level, filling the tag will populate all the volumes in the group with the same volume ID. You will need to change the volume ID for each individual volume later in the workflow or when you update the volumes. Using this tag is optional; it’s for documentation purposes only.
+
+    Select **Next: Volumes**.
+
+    [ ![Screenshot that shows the Tags section of the Volume Group tab.](./media/application-volume-group-add-volume-secondary/application-secondary-volume-group-tags.png) ](./media/application-volume-group-add-volume-secondary/application-secondary-volume-group-tags.png#lightbox)
+
+6. The **Volumes** tab displays information about the volumes that are being created.  
+
+    The volume naming convention includes an `"HA-"` prefix to indicate that the volume belongs to the secondary system of an HSR setup.
+
+    [ ![Screenshot that shows the Volume Group tab.](./media/application-volume-group-add-volume-secondary/application-secondary-volumes-tags-extension-one.png) ](./media/application-volume-group-add-volume-secondary/application-secondary-volumes-tags-extension-one.png#lightbox)
+
+7. In the **Volumes** tab, you can select each volume to view or change the volume details, including the protocol and tag for the volume.
+
+    In the **Tags** section of a volume, you can populate the `HSRPartnerStorageResourceId` tag with the resource ID of the corresponding primary volume. This action only marks the primary volume; it does not validate the provided resource ID.
+
+    [ ![Screenshot that shows the tag details.](./media/application-volume-group-add-volume-secondary/application-secondary-volumes-tag-details.png) ](./media/application-volume-group-add-volume-secondary/application-secondary-volumes-tag-details.png#lightbox)
+
+    Select **Volumes** to return to the Volumes overview page.  
+
+8. Select **Review + Create** to list all volumes that will be created. Select **Create Volume Group** to start the volume group creation. 
 
-8. Click **Review + Create** to list all volumes that will be created. Click **Create Volume Group** to start the volume group creation. 
+
+---
 
 To add more HANA hosts for a multiple-host SAP HANA system, follow steps in [Add hosts to a multiple-host SAP HANA system](application-volume-group-add-hosts.md). Be sure to select the **HSR secondary** option in the SAP HANA tab to indicate the replication secondary system.