vSphere Storage Appliance

 View Only

  • 1.  Mixing Hyper-V and VMware on storage array

    Posted May 08, 2015 05:59 AM

    Hi,

    I hate to admit but soon there will be Hyper-V running in our datacenter along with VMware :-) . We're going through the design sessions right now and one point that came to table was the discussion on wether we should mix Hyper-V and VMware hosts on the same array. The only thing I could come up with to NOT mix them is that an upgrade of ESXi may require a VNX flare / blockOE version that is not yet supported by the Hyper-V hosts. But I'm not sure if this is enough to justify buying a separate array just for Hyper-V.

    Are there any other concerns? LUNs of course will not be shared, but could I share storage pools? Would mixing loads make troubleshooting more difficult?



  • 2.  RE: Mixing Hyper-V and VMware on storage array

    Posted May 08, 2015 03:26 PM

    I think another concern is if you share the storage pool you may not get expected results of Storage I/O Control in VMware.



  • 3.  RE: Mixing Hyper-V and VMware on storage array

    Posted May 08, 2015 03:48 PM

    Richardson Porto wrote:

    I think another concern is if you share the storage pool you may not get expected results of Storage I/O Control in VMware.

    Storage I/O control or Storage DRS ? We're not using Storage DRS since we have FAST VP on the storage pools. And I feel like best practise will at least be to not mix them in the same storage pool. I think :-)



  • 4.  RE: Mixing Hyper-V and VMware on storage array

    Posted May 08, 2015 03:55 PM

    I mean Storage I/O Control (SIOC), but note that Storage DRS uses SIOC too. Take a look at this KB article: VMware KB: Unmanaged I/O workload detected on shared datastore running Storage I/O Control (SIOC) for congestion man…

    This informational event alerts the user of a potential misconfiguration or I/O performance issue caused by a non-ESX workload. It is triggered when Storage I/O Control (SIOC) detects that a workload that is not managed by SIOC is contributing to I/O congestion on a datastore that is managed by SIOC. (Congestion is defined as a datastore's response time being above the SIOC threshold.) Specific situations that can trigger this event include:

    • The storage array is performing a system operation such as replication or RAID reconstruction.
    • VMware Consolidated Backup or vStorage APIs for Data Protection are accessing a snapshot on the datastore for backup purposes.
    • The storage media (spindles, SSD) on which this datastore is located is shared with volumes used by non-vSphere workloads
    • The host is running in an unsupported configuration.