TimeFinder snap functionality uses snap pool,  Vmax thin provisioning uses thin pools.  VDEVs are not members of any pool, the do utilize snap pool. Snap pool consists of devices that have "savedev" attributes.  here is my snap pool, notice the SN in the Type column   $ symcfg list -sid 123 -pool -snap -mbSymmetrix ID: 000000000123                         S Y M M E T R I X   P O O L S-------------------------------------------------------------------------------             Ty                                                             Sta Pool         p Dev   Dev             Total  Enabled     Used     Free Full   t Name         e Emul  Config            MBs      MBs      MBs      MBs  (%)   e------------ -- ----- ------------ -------- -------- -------- -------- ---- ---DEFAULT_POOL SN FBA   RAID-5(7+1)   1139366  1139366   169349   970018   14 EnaDEFAULT_POOL SN 3390  Unknown             0        0        0        0    0 DisDEFAULT_POOL SN 3380  Unknown             0        0        0        0    0 DisDEFAULT_POOL SN AS400 Unknown             0        0        0        0    0 DisTotal                              -------- -------- -------- -------- ----MBs                                 1139366  1139366   169349   970018   14Legend for Pool Types:    SN = Snap,  RS = Rdfa DSE  TH = Thin   Here is my other array that has think pools   $ symcfg list -sid 345 -pool -thin -mbSymmetrix ID: 0000000000345                         S Y M M E T R I X   P O O L S-------------------------------------------------------------------------------             Ty                                                             Sta Pool         p Dev   Dev             Total  Enabled     Used     Free Full   t Name         e Emul  Config            MBs      MBs      MBs      MBs  (%)   e------------ -- ----- ------------ -------- -------- -------- -------- ---- ---MYPOOL1       TH FBA   RAID-5(3+1)  16199798 16199798 15219669   980172   93 EnaMYPOOL2       TH FBA   RAID-5(3+1)   9749884  9749884  8614486  1135416   88 EnaTotal                              -------- -------- -------- -------- ----MBs                                25949682 25949682 23834155  2115588   91Legend for Pool Types:    SN = Snap,  RS = Rdfa DSE  TH = Thin  you see above that i have two pools. The reason i have two pools is because when we first bought our VMAX we got it with 300G FC drives, just recently we decided to go to 600G FC drives, so we decided to create a new pool. From now on all our future disk purchases will consist for 600G FC drives. They will be chopped-up into TDATs and added to MYPOOL2. After new capacity will be added, we will run "rebalance" process on the pool.
Do I need to create one single thinpool (of what size ?  size estimates follow ) or do i create separate pool for Timefinder snap usage ??..this vmax is dumped with all the data which currently is existing in the environment as soon as the migrations start imagine the data is about 27 TB. so Do I create the thinpool with little more than 30 TB? or what is the best practice here. The source devices which are going to be snapped is about 4 TB, what is the best approach for thinpool creations meeting above requirements ??  once the pool is created somehow, in order to meet the growing demand, we tend to add data devices to the pool, also there is a need to rebalance the pool with added tdats. (Is adding tdats and issuing rebalance no way effects the connected host with existing storages right?)  Last what are the subcription percetages to be put for the created pools ?
TimeFinder/Snap considerations for thin pool/size for vmax.