Unsolved
This post is more than 5 years old
85 Posts
1
946
January 18th, 2012 20:00
FAST Policy implementation
Hi All,
I am new to the FAST Policy on Vmax. I just want to understand how the FAST works in the below Scenario
Configurations
FAST Policy-withthe Two Tiers SSD and FC
Storagegroups contains- FC and SATA Bound Devices
If I apply the FAST policy to the Storage Group how does the FAST works on these devices. What is that Factor decides SATA devices should not be considered as we dont have Pool In the FAST Policy.
Our Assumption is We will not be able to apply the Policy or FAST will reject the SATA devices.
I would like to know Experts Advices and thoughts
Govind
No Events found!
Amita2
93 Posts
1
January 20th, 2012 06:00
Hi,
You can check the following document for FAST. It explains FAST thoroughly:
http://powerlink.emc.com/km/live1/en_US/Offering_Technical/Technical_Documentation/300-010-337.pdf?mtcs=ZXZlbnRUeXBlPUttQ2xpY2tDb250ZW50RXZlbnQsZG9jdW1lbnRJZD0wOTAxNDA2NjgwNTBkM2ZkLG5hdmVOb2RlPVNvZndhcmVEb3dubG9hZHMtMg__
sauravrohilla
859 Posts
0
January 22nd, 2012 20:00
Hi Govind,
There is no restriction in FAST that will stop you from enabling it on SG which has devices from the non fast tiers. Infact, this is where FAST comes in to the picture. If your SG has devices from the tier (SATA in your case) which is not part of your FAST tier then FAST will show your SG as "Out of Policy" and then the compliance (intelligent tiering) algo will kick in and move your SATA devices to either FC or SSD tiers (depending on the policy that you have defined) and make your SG aligned to the policy. If you dont want FAST to work on SATA devices then you can PIN those devices.
regards,
Saurabh Rohilla
SymmetrixForums
31 Posts
0
January 23rd, 2012 09:00
Did the replies to your post answer your question? If so, please mark the helpful and correct posts and if applicable, also mark the post as answered. Doing so helps others identify the most useful posts. Thank you.
rawstorage
4 Apprentice
•
423 Posts
0
January 30th, 2012 02:00
Govind,
assuming we are talking FAST VP you will get an error message stating that your devices aren't bound to any of the tiers in the fast policy or somethign to that effect, however this is not a show stopper, you can use the rebind operation to bind the TDEV to a pool that is in your policy this will allow you to bind the FAST policy. You will however immediately be in violation of capacity constraints as tracks for your storage group will need to be moved to the FC or SSD tiers to comply with the policy applied.
Check out the TechNote Amita has mentioned earlier as this will goes into details on all the restrictions etc. You may wish to control the reolocation speed during this rebalance or do a symmmigrate operation to one of the Tiers in the policy.
Hope this answers your question
RobertDudley
2 Intern
•
448 Posts
0
January 30th, 2012 07:00
When you apply a FAST policy to a storage group that has devices that are not within the policy you are prompted by the compliance rules to pick a pool to move the non-compliant devices to. It uses V-Lun migrator to move the devices into a pool for compliance and then will start managing them under the policy. As they already stated you can pin devices so that FAST will not move them but I think you will have to have the storage group within the compliance model to apply the policy.