What you're seeing (no FAST movements) is the expected behavior in this case -- when you disassociate a device from a FAST Policy (which is what happened when you moved the dev out of a FAST-managed SG), the extents just remain where they were at the time of disassociation.
If you'd like the extents to be moved back to the bound pool, then you can execute a VLUN migration (symmigrate), or you can associate this SG to a different FAST Policy and let the FAST engine perform promotions/demotions again.
seancummins
2 Intern
•
226 Posts
2
September 19th, 2014 09:00
Hi Brandon,
What you're seeing (no FAST movements) is the expected behavior in this case -- when you disassociate a device from a FAST Policy (which is what happened when you moved the dev out of a FAST-managed SG), the extents just remain where they were at the time of disassociation.
If you'd like the extents to be moved back to the bound pool, then you can execute a VLUN migration (symmigrate), or you can associate this SG to a different FAST Policy and let the FAST engine perform promotions/demotions again.
Thanks,
- Sean