Hello and welcome to this video on the new Azure NetApp files feature application volume group for SAP HANA. You might have seen that the feature is now in general availability and is planned to be the standard provisioning method for ENF volumes used for SAP HANA. We have put together a series of short videos to explain the application volume group feature and the usage for the different SAP HANA deployments. This video will walk you through the provisioning workflow for an SAP HANA system and HANA system replication. As shown in this figure, the volume provisioning for HANA system replication is a two-steps configuration. First, you need to execute the AVG workflow for HANA single host and then you extend the configuration by adding the volumes for the secondary HANA system replication host.In the first demo, we already provisioned the volumes for HANA singlehost system. And in this demo, we will show how to add the volumes for the secondary host. HANA system replication is typically configured across two different availability zones. The primary system runs for example in zone one, the secondary in zone 2. To ensure that the secondary systems volumes are provisioned in zone 2, a second PPG and availability set must be configured. When issuing the pinning request, you must provide the corresponding zone in the questionnaire. With that in mind, our starting point would be a single host system provisioned in zone one and a secondary host within a PPG and AV set pinned in zone 2. When we go to the application volume group view, the volume group of our single host system is listed. Now we going to add a group to extend the system to a HANA system replication configuration. We enter the same SID as for our single host system. Before the error message about uniqueness of the group name can be ignored since the volume name will get a prefix in a system replication setup. We select HSR secondary to provision the volumes for the HSR secondary host. With the next step, the PPG of the secondary zone must be selected. In our lab, we haven't configured a secondary zone and use the same PPG as before. The further configuration steps are identical to what we have already seen for the single host workflow. The volume preview shows the volume which will be provisioned. Five volumes will be provisioned for the secondary host in the same way as for a single host system. Each volume name has the prefix HA to indicate that it is a secondary volume. Now we start the deployment process which took around 4 minutes in our lab setup. Within the application volume group view, we now have an additional group for the HANA system replication secondary.The volume view shows five volumes with the HA prefix in the name. Ofcourse, same rules apply for the separation of data and lock volume on different storage endpoints with different IP addresses. The final configuration of the volumes for the HANA system replication setup looks like this. We have a group of five volumes for the primary as well as for the secondary HANA host. As explained at the beginning of the video, a second proximity placement group and availability set must be created in zone 2 and the pinning request must include the zone information. The AVG workflow will then place the volumes in the secondary zone. It is then guaranteed that compute and storage resources of the HANA primary and secondary system is separated into different zones. Okay, with that, thanks a lot for watching the video.