This use case provides a basic framework for exploring how CRGs can work for your SAP HANA databases. For nonproduction SAP HANA landscapes, you might want to implement greater consolidation and use larger PowerOne CRGs with vSphere to create a cost-optimized landscape. The goal is to use virtual machines within the CRG to run multiple independent SAP HANA databases. In this use case, we configure a CRG to run eight SAP HANA databases in virtual machines.
Assuming that each virtual machine requires four vCPUs and 2 TB of memory, with eight nonproduction SAP HANA databases, our minimum configuration for the CRG is 24 vCPUs and 16 TB of memory. Because the PowerOne system automatically provisions the CRG based on the total requirements, you do not need to calculate the number of MX blade servers that are required.
By following SAP and VMware guidelines, you can use a large CRG to save time and optimize costs for nonproduction SAP HANA landscapes and focus on the total requirements for the SAP HANA cluster. For VMware architecture guidance for SAP HANA deployments, see Architecture guidelines and best practices for deployment of SAP HANA on VMware vSphere.