As Sean said, check your policies, and also make sure FAST is enabled!
And if you are on the later 76 versions of Enginuity, you should have your FRR (relocation rate) set to 7 or higher. The old default of 5 can be pretty aggressive about moving stuff on the newer releases compared to previous releases.
When I see this sort of thing, it's often because of admins binding TDEVs to SATA (as you noted), and/or using policies that trap workloads that they consider less important in the lower tiers. It sounds like they're already planning on rebinding from SATA to FC, so that should help. They might also want to review their FAST Policies, bearing in mind that just because something is less important to the business, doesn't mean it's a light workload. There are some cases where test/dev/UAT workloads can actually be higher than production.
Trapping these heavy test/dev workloads in the lower tiers can end affecting production workloads, because these tiers are used by both production and test/dev. The easiest way to resolve this would be to start by using a 100/100/100 policy for everything. Then if you need to throttle certain workloads, use Host IO Limits, and/or gradually reduce the amount of EFD/FC capacity available to test/dev.
Yes, I would recommend changing the FRR to 7 in the long term, but if you change policies to try and get some of this active data off of SATA, a lower FRR might make the movements happen faster.
Quincy561
1281 Posts
1374
0
Posted October 16th, 2014 12:00
As Sean said, check your policies, and also make sure FAST is enabled!
And if you are on the later 76 versions of Enginuity, you should have your FRR (relocation rate) set to 7 or higher. The old default of 5 can be pretty aggressive about moving stuff on the newer releases compared to previous releases.