Validate the HANA host role before submitting a NetApp volume-group request

Source facts

An Azure NetApp Files application volume group creates volumes for one SAP HANA host. The first host requires data, log and shared volumes, with backup volumes optional. Each additional scale-out host can add only data and log volumes. These groups require manual QoS capacity pools. Microsoft also warns that REST callers do not receive the portal and Resource Manager template’s deployment prechecks and recommendations. Microsoft Learn.

Applicability

Use this review for SAP HANA application-volume-group creation through REST. Identify whether the request represents the first host or an additional scale-out host, and review the complete source’s networking, placement and protocol requirements before deployment.

DSE recommendation

Make host role and expected volume roles explicit inputs to the deployment review. Compare the requested array with an approved host-to-volume map before issuing a write. Keep the first-host example separate from the additional-host example; do not carry shared or backup volume entries into every repeated request. Have the HANA and storage owners agree the intended size and throughput independently of the sample values. Preserve the reviewed payload without access tokens.

Verification

In an approved environment, inspect the returned group and its volume roles against the host map. Verify the selected pool’s QoS mode and the actual requested parameters. Treat a successful API response as provisioning evidence, not certification that the complete HANA design is appropriate. Resolve any extra or missing role before proceeding to another host.

Official references

Microsoft Learn: Configure application volume groups for SAP HANA using REST API.