bind pool EFD and migrate from sata and FC whitout FASTVP

Your customer will need to perform a VLUN migration using the "symmigrate" command. Simply performing a re-bind will not move the data.

Also they must be properly licensed to use VLUN migrator. In the past, customers have needed the optimizer license to use this functionality.

Hello KW160,

I think the question is not how to make  LUN Migrate, i believe Joshua mean if a EFD Pool can to work properly with a whole database or if is according to the best practices or its implications, i need to know that too

You can use EFD for everything if you have enough space.  However using FC/EFD and FAST VP may make the most effective use of the EFD capacity, rather than putting idle data on EFD.

It's excellent to follow the docs of EMC

On Thu, Jul 31, 2014 at 3:40 AM, Quincy56

Moving entirely to an EFD pool may not necessarily increase the performance if you have a skewed workload. If the workload does not change drastically then it might be a good idea to migrate the symm devs to a faster pool, EFD in this case.

You can use VLUN Migration to achieve this.VLUN Migration can use the storage of existing devices that do not contain live data or unconfigured disk space.

VLUN Migration allows thin devices to be moved between pools.For a given list of devices, the data tracks can be moved from their current pool to a target pool. In addition, if the devices themselves are not already bound to the target pool, they will be rebound to the target pool.

Please refer the CLI Array Control guide for cli commands.

1. Create new devices and bind them to EFD.

2. Assuming ASM is being used, have the DBA add EFD LUNs and kick out the FC/SATA Luns.

Writes are not a horrible thing for EFD drives.  They can do more IOPs even with writes than FC, however the benefit to the host is non-existent if you are not hitting WP limits. 

The workloads that benefit most are those that are waiting for the drive response time, such as read miss.

You get the best utilization from EFDs by using FAST VP to only put the most active data on EFDs.

create new device with bind them to EFD , and migrate tdevs to EDF ,  would cause excessive  problems of write misses in EFD. ? ;  therefore get performance problems