So far we had a mixed experience with ODX and HP 3PAR , backup was painfull with locked luns , moving vm around was even more painfull with data corruption
So until now we have disabled ODX on everything 3PAR related other arrays have issue with backup , and since its software the solution so far have been a mix between HP and Microsoft
This is “only” a issue when doing backup of a CSV volume standalone host havent been affected again back to the mix between HP and Microsoft
From what we seen so far
2012 R2 with April update and http://support.microsoft.com/kb/2966407 will fix
Assume that you install update 2919355 on a Windows 8.1-based or Windows Server 2012 R2-based computer. When you try to back up some Hyper-V virtual machines that reside on cluster shared volumes, you receive an error message that indicates the backup request has failed.
Here is a sample of the error messages that you may encounter when this issue occurs:
Csv writer is in failed state with unexpected error
On the 3PAR side we have upgraded to 3.1.3 and will apply some more patches tomorrow and continue testing
Windows Server 2012 or Windows Server 2012 R2 hosts with ODX in use with HP 3PAR StoreServ Storage running HP 3PAR OS version 3.1.2 GA, 3.1.2 MU1, 3.1.2 MU2, 3.1.2 EMU2, or 3.1.2 MU3.
Upgrade the HP 3PAR OS on the HP 3PAR StoreServ Storage to 3.1.2 MU2 or later if running a lower HP 3PAR OS version. Next apply the patch as follows:
For 3.1.2 MU2 and 3.1.2 EMU2, apply Patch 11 followed by Patch 36.
For 3.1.2 MU3, apply Patch 30.
So after Windows Patches and Upgraded 3PAR we can now backup mutiple VM (was 2 before) and move data around with ODX enabled.
What remains for the next week is to move VM around with storage migration to verify that the data corruptions also is history.