HP StoreOnce VSA Deployment and Configuration Guide (TC458-96024)

4. Click VMFS3.
5. Update the field in VMFS3.MaxHeapSizeMB.
In ESXi 5.1 Update 1, the maximum heap size is 640 MB. This allows a maximum of 60 TB of
open storage per ESXi host.
In vSphere 5.5, VMware introduces a much improved heap eviction process and there is no need
for the larger heap size, which consumes memory. vSphere 5.5, with a maximum of 256MB of
heap, enables vSphere hosts to access all the address space of a 64TB VMFS. Refer to http://
www.vmware.com/files/pdf/vsphere/VMware-vSphere-Platform-Whats-New.pdf for more details.
Supported datastores on Hyper-V
StoreOnce VSA is supported on NTFS file system based storage.
Hyper-V does not support NFS datastores. Hyper-V VSA is also not supported on pass-through
disks and ReFS based storage.
Supported server and network adapter configurations with Hyper-V
It has been observed that sometimes Hyper-V 2012 R2 virtual machines lose network connectivity;
this depends on the server and network card models being used. More information can be found
on these in the Troubleshooting section in the HP StoreOnce VSA Deployment and Configuration
guide. As a general guideline, StoreOnce VSA has been tested on the following configurations.
RecommendationsPlatform
Recommended configurationHP ProLiant G8 Intel CPU + Emulex network card
Recommended configurationHP ProLiant G8 Intel CPU + Broadcom network card
Not recommendedHP ProLiant G8 AMD CPU + Emulex network card
Recommended configurationHP ProLiant G8 AMD CPU + Broadcom network card
Most of the connectivity issues have been seen on HP Proliant G8 AMD CPU + Emulex network
adapter configuration, and it is recommended to avoid using this combination.
AMD Platform NUMA Settings (Hyper-V only)
With Hyper-V server on AMD based hardware, please review the virtual NUMA settings before
deploying the StoreOnce VSA.
Once the VSA is deployed on Hyper-V, check the settings of the virtual machine for virtual NUMA.
In the following example, the virtual NUMA node has a RAM of 31542 MB, which is less than
32768 MB (32 GB) that was allocated to the VSA. In this case, the VSA does not boot up properly.
This applies to any virtual machine in general. For more information, please refer to the Microsoft
documentation, How to Configure Virtual NUMA for VMM, at http://technet.microsoft.com/en-us/
library/jj614459.aspx.
8 Introduction