This post is more than 5 years old
3 Posts
0
1595
March 4th, 2016 08:00
FAST schedule on VMAX3
Hello ,
Can any one tell me how FAST data move is scheduled in VMAX 3 and how to view modify it ? looks like sympotz and symtw doesn't work with SE 8.1 . If you have any white paper could please share with me ?
Thanks,
Hareesh.
No Events found!
Allen Ward
4 Operator
•
2.1K Posts
0
March 8th, 2016 06:00
I'm not sure I understand exactly what you are looking for, but the SLOs in VMAX3 are the mechanism for controlling data placement. SLO uses FAST VP under the covers to make sure that SLO can deliver on the "promises". You don't need to define how much EFD you want dedicated to a certain workload. You just define that you want that workload to have a "Diamond" SLO and HyperMax will make sure the performance is there (in this case by putting the data on EFD). Each of the defined SLOs has some backend "affinity" settings that define what tiers are available and which ones are avoided. I still haven't seen an absolute answer on whether some of the SLOs will allow data placement in a tier that it doesn't have an "affinity" for but my suspicion is that the answer is "no".
Keep in mind that there is also the option to use the "Optimized" SLO which doesn't have any particular data placement rules beyond "Provide the best performance possible with the resources that aren't dedicated to delivering on specific SLO promises.
Not sure of that helps or if it makes things more cloudy. If you could better define your specific use case we might be able to answer you more clearly in terms that will make sense to your environment.
Allen Ward
4 Operator
•
2.1K Posts
0
March 5th, 2016 19:00
My understanding is that this is all "hidden" behind the curtain of SLO now. There is no need to directly control FAST and Hypermax optimizes things automatically to maintain the service levels you have assigned through SLO.
AndrewWinegar
3 Posts
0
March 7th, 2016 10:00
Thanks Allen, So you believe FAST is on all the time and data is moved between tires as needed ? I was trying to see how SLO can satisfy the needs of performance based on higher capacity tire availability . What I mean to say is in VMAX 2 FAST policy will restrict the data flow to higher tire but not sure how SLO deal with capacity un availability in higher tire
rawstorage
3 Apprentice
•
420 Posts
1
March 8th, 2016 06:00
Andrew,
FAST is always on in VMAX3 even in simple configurations. There is no way to modify the move schedule, it will be moving 24 hours. Typically moving data every 5 minutes in chunks as small as 128KB but typically we are moving track groups.
If you are in a database environment then we support Hinting for Databases currently Oracle, but we are releasing support for MS SQL soon. This feature is no Charge and available with Unisphere for VMAX, it requires a readonly account to the database and an account with hinting ability in Unisphere.
We have a couple of papers, for some reason I can't paste the link but Search Service level Provisioning Technote in google and you should get it first hit.
There is also a Database storage analyser technote.
Apologies for lack of links will try different browser and see if I can paste in later.
AndrewWinegar
3 Posts
0
March 9th, 2016 09:00
Thank You Guys.