I doubt that auto-tiering has been disabled for over a year. I wonder if there was any activity, like a non-disruptive software upgrade, done on it recently. I mention that because disabling auto-tiering is part of the prep for some such activities, and it may have been disabled on purpose, but not re-enabled by omission.
I would also ask if the backend LUNs are thin or thick. Thin LUNs that grow significantly often become dis-organized, and this shows up as decreased performance for sequential access processing...like backups and integrity checks...This can be addressed (among other ways...) by migrating the LUN to a new new LUN, even if the new one is thin and in the same pool. That process will do something like a re-org/defrag on the data; putting the blocks back in a more sequential manner.
So we ended up turning auto-tiering back on and also replaced a switch that was connected to the VPLEX because it had degraded and wasn't functioning properly. The job times were back in their average run-time range of 2 hours for a couple days but today it jumped back up to 12 hours. Also, the backend LUNs are thick provisioned.
I think it may be a san switch issue, not totally sure though.
I did notice that the monitors in VPLEX gui has breaks in them depending on the director/port. Is this normal?
ZaphodB
195 Posts
0
May 7th, 2014 09:00
I doubt that auto-tiering has been disabled for over a year. I wonder if there was any activity, like a non-disruptive software upgrade, done on it recently. I mention that because disabling auto-tiering is part of the prep for some such activities, and it may have been disabled on purpose, but not re-enabled by omission.
I would also ask if the backend LUNs are thin or thick. Thin LUNs that grow significantly often become dis-organized, and this shows up as decreased performance for sequential access processing...like backups and integrity checks...This can be addressed (among other ways...) by migrating the LUN to a new new LUN, even if the new one is thin and in the same pool. That process will do something like a re-org/defrag on the data; putting the blocks back in a more sequential manner.
andrewkt
3 Posts
0
May 13th, 2014 08:00
Thanks for the reply.
So we ended up turning auto-tiering back on and also replaced a switch that was connected to the VPLEX because it had degraded and wasn't functioning properly. The job times were back in their average run-time range of 2 hours for a couple days but today it jumped back up to 12 hours. Also, the backend LUNs are thick provisioned.
I think it may be a san switch issue, not totally sure though.
I did notice that the monitors in VPLEX gui has breaks in them depending on the director/port. Is this normal?