Hi Mohammad,  Apologies for the delay. So yes, everything is based on the storage policy you chose. The system will never know if the admin made a mistake. How could it?  If this was an example with normal LUNs, and you had 3 separate pools without any relation between them (one Flash, one SAS, and one NL-SAS), if your admin creates a VM in the wrong datastore, there is no way the system will correct this either. Neither VMware or the Unity array can ever know that a mistake was made. [IMAGE]  If this was a single pool with 3 tiers however, FAST VP would still kick in and move the hot data up to faster drives if needed (assuming all LUNs were set to relocation policy autotier). But as discussed FAST VP doesn't work in your case (doesn't work across pools, nor does it work across storage policies).  So again, whatever storage policy is chosen, that is what is applied. And that will then map back to whatever drives match that policy.   Andre @ Dell EMC
Hello, I'm confused about Fast VP mechanism in VVOLs.  for example, we have a 3 pool.  1- 1st pool contain SAS Flash disks and SAS Disk 2- 2nd pool contain NL-SAS Disks 3- 3rd pool contain SAS and NL-SAS Disks I create a VVOL datastore and have 30% capacity of 1st pool, 20% capacity of 2nd pool and 50% capacity pf 3rd pool. so 3 capability profile assigned to this VVOL.  I have a storage policy with name "Extreme" in vmware that contain Drive Type: ExtremePerformaceTier.  When a VM is created under Extreme Storage policy, what would happen and where it will be stored?  How Fast VP mechanism act and relocating VM, if selected datastore is not proper? Regards, Mohammad
Fast VP in VVOLs