One thing you might want to add (that the docs gloss over) is the IP connectivity required for VVols. vCentre AND the ESXi hosts need to be able to talk to the 3PAR over IP .. used for initial setup of the VVol datastore and when creating new VVols, snapshots and other management stuff.
Hello Calvin! I was using 3.3.1 MU5 , with vsphere 7.0.2 , when i trying create storage policy with enabled compression or dedup , compliance check does not show my any compatible datastore , but when i disable compression or dedup, compliance check fine and shows me compatible datastore
Hey Calvin, have a 3par with two CPG's. Keen to look at VVOL's but nervous as this is our production SAN. Can you think of anything that I need to check or confirm before I commit to creating the storage container via the SSMC?
You can definitely run VMFS and VVols on the same 3PAR. Here's the VMware implementation guide: support.hpe.com/hpsc/doc/public/display?docId=emr_na-c03290624&lang=en-us&cc=us. Here's the 3PAR and VVols implementation guide: h20195.www2.hpe.com/v2/getpdf.aspx/4AA5-6907ENW.pdf Recommend that you have 3PAR OS 3.3.1 T05 (this added new features and increased scalability) or 3.3.1 MU3 is a good one to have as well.
Hi. When you are creating HPE 3PAR StoreServ rules, you have the Compression rule. I have VVols on vSphere 6.5 and don't have this rule available. Which version of vSphere are you on? Why I don't have this rule?
This is a function of the 3PAR OS and not version of VMware. You need 3PAR OS 3.3.1 MU5 for that capability; it was something that was in the demo that I didn't realize wasn 't publicly available yet. MU5 should be out in the next few weeks.
One thing you might want to add (that the docs gloss over) is the IP connectivity required for VVols. vCentre AND the ESXi hosts need to be able to talk to the 3PAR over IP .. used for initial setup of the VVol datastore and when creating new VVols, snapshots and other management stuff.
Hi Calvin, can you make another video about 3PAR VVOLs with replication? step by step process to adding replication to VVOL's between two 3PAR's.
Hello Calvin! I was using 3.3.1 MU5 , with vsphere 7.0.2 , when i trying create storage policy with enabled compression or dedup , compliance check does not show my any compatible datastore , but when i disable compression or dedup, compliance check fine and shows me compatible datastore
Hey Calvin, have a 3par with two CPG's. Keen to look at VVOL's but nervous as this is our production SAN. Can you think of anything that I need to check or confirm before I commit to creating the storage container via the SSMC?
You can definitely run VMFS and VVols on the same 3PAR. Here's the VMware implementation guide: support.hpe.com/hpsc/doc/public/display?docId=emr_na-c03290624&lang=en-us&cc=us. Here's the 3PAR and VVols implementation guide: h20195.www2.hpe.com/v2/getpdf.aspx/4AA5-6907ENW.pdf
Recommend that you have 3PAR OS 3.3.1 T05 (this added new features and increased scalability) or 3.3.1 MU3 is a good one to have as well.
You Rock.. keep up the good work..!!
Hi. When you are creating HPE 3PAR StoreServ rules, you have the Compression rule. I have VVols on vSphere 6.5 and don't have this rule available. Which version of vSphere are you on? Why I don't have this rule?
This is a function of the 3PAR OS and not version of VMware. You need 3PAR OS 3.3.1 MU5 for that capability; it was something that was in the demo that I didn't realize wasn 't publicly available yet. MU5 should be out in the next few weeks.
@@CalvinZito Thank you very much for your answer.