Migrate pinned TDEV's to their original Pools

Yes, pin the devices and use VLUN to migrate them back to the original pool.   What rohang is saying is not correct.  If you remove a device from FAST VP by no longer associating the storage group with a policy, the extents of the device are not going to "magically" go back to the original thin pool.  They will stay where they are.  You would still have to manually move them back.

yes, it needs to be done through VLUN migration feature.

That's right, Drew. I was incorrect.

VLUN VP has the ability to move all allocated thin device extents from one pool to another, and it is this feature that is the basis for FAST VP.

And when using VLUN VP for devices under FAST VP control, it is recommended to pin the TDEVs to the target thin pool so FAST VP won't move them to other tiers until the user is ready. When TDEVs under FAST VP control are pinned to a thin pool, FAST VP continues to collect statistics, but it won't issue move plans for them.

Thanks.

Hello Andy,

Before selecting the VLUN Migration option for the TDEV, make sure you pin the device.

Use a #symdev pin to pin the TDEV and then a #symmigrate to move it to the bound tier ..

for Unisphere, you should see something like this ..

Thanks.

Thanks very much.

I thought it was that, just wanted to verify. It was very simple.