FAST VP Step by Step Module 2

Welcome to FAST VP – Step by Step.
Copyright © 2012 EMC Corporation. All rights reserved
Welcome to FAST VP – Step by Step.
Copyright © 1996, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012 EMC
Corporation. All Rights Reserved. EMC believes the information in this publication is accurate as of its
publication date. The information is subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO
REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS
PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable
software license.
EMC2, EMC, Data Domain, RSA, EMC Centera, EMC ControlCenter, EMC LifeLine, EMC OnCourse, EMC
Proven, EMC Snap, EMC SourceOne, EMC Storage Administrator, Acartus, Access Logix, AdvantEdge,
AlphaStor, ApplicationXtender, ArchiveXtender, Atmos, Authentica, Authentic Problems, Automated
Resource Manager, AutoStart, AutoSwap, AVALONidm, Avamar, Captiva, Catalog Solution, C-Clip,
Celerra, Celerra Replicator, Centera, CenterStage, CentraStar, ClaimPack, ClaimsEditor, CLARiiON,
ClientPak, Codebook Correlation Technology, Common Information Model, Configuration Intelligence,
Configuresoft, Connectrix, CopyCross, CopyPoint, Dantz, DatabaseXtender, Direct Matrix Architecture,
DiskXtender, DiskXtender 2000, Document Sciences, Documentum, elnput, E-Lab, EmailXaminer,
EmailXtender, Enginuity, eRoom, Event Explorer, FarPoint, FirstPass, FLARE, FormWare, Geosynchrony,
Global File Virtualization, Graphic Visualization, Greenplum, HighRoad, HomeBase, InfoMover, Infoscape,
Infra, InputAccel, InputAccel Express, Invista, Ionix, ISIS, Max Retriever, MediaStor, MirrorView,
Navisphere, NetWorker, nLayers, OnAlert, OpenScale, PixTools, Powerlink, PowerPath, PowerSnap,
QuickScan, Rainfinity, RepliCare, RepliStor, ResourcePak, Retrospect, RSA, the RSA logo, SafeLine, SAN
Advisor, SAN Copy, SAN Manager, Smarts, SnapImage, SnapSure, SnapView, SRDF, StorageScope,
SupportMate, SymmAPI, SymmEnabler, Symmetrix, Symmetrix DMX, Symmetrix VMAX, TimeFinder,
UltraFlex, UltraPoint, UltraScale, Unisphere, VMAX, Vblock, Viewlets, Virtual Matrix, Virtual Matrix
Architecture, Virtual Provisioning, VisualSAN, VisualSRM, Voyence, VPLEX, VSAM-Assist, WebXtender,
xPression, xPresso, YottaYotta, the EMC logo, and where information lives, are registered trademarks or
trademarks of EMC Corporation in the United States and other countries.
All other trademarks used herein are the property of their respective owners.
© Copyright 2012 EMC Corporation. All rights reserved. Published in the China.
1Module 2: Managing FAST VP

Upon completion of this class, you should be able to:
Upon completion of this class, you should be able to:
•Implement FAST VP using SMC and SYMCLI
• Set time windows
• Set FAST VP Control Parameters
• Create FAST VP Tiers
• Create FAST VP Policies
• Associate storage groups with FAST VP policies

Upon completion of this lesson, you should be able to:
Copyright © 2012 EMC Corporation. All rights reserved 4
•Implement FAST VP using SMC
Module 2: Managing FAST VP

These are the steps to implement FAST.
These are the steps to implement FAST.
The Advanced Software Suite for VMAXe license covers the license FAST VP.
A full description of Symmetrix software licensing is out of the scope of this course.

Symmetrix Management Console (SMC) provides a FAST Configuration Wizard to allow a user to
Symmetrix Management Console (SMC) provides a FAST Configuration Wizard to allow a user to
quickly configure the FAST environment on a Symmetrix V-Max storage array. The FAST
configuration wizard guides the user through the process of configuring FAST.
Use of the FAST configuration wizard, is recommended for use in less complex environments;
possibly where only one Symmetrix physical disk group is configured for each disk technology
type within the array, or where simple performance/device movement windows will suffice.

FAST and FAST VP require license keys. License keys can be entered using the Manage Licenses
FAST and FAST VP require license keys. License keys can be entered using the Manage Licenses
menu choice. The Show License Usage displays the licenses installed for this Symmetrix.

To check the status of FAST – Right click on a Symmetrix then choose FAST followed by FAST
To check the status of FAST – Right click on a Symmetrix then choose FAST followed by FAST
Status Report …
This gives us a status report on FAST. Here we see that FAST VP is enabled, Performance and
Move Time windows are open.

To Enable/Disable FAST VP – Right click on a Symmetrix choose FAST, then FAST Control
To Enable/Disable FAST VP – Right click on a Symmetrix choose FAST, then FAST Control
Parameters and then select Enable/Disable FAST

This is where we check FAST and Optimizer control parameters. The first half of the screen refers
This is where we check FAST and Optimizer control parameters. The first half of the screen refers
to parameters that are shared between FAST, FAST VP, and Optimizer.
The second half contains parameters that are specific to FAST and FAST VP.
The value of the control parameters that apply to FAST VP are highlighted on the slide by the
black boxes.
In our lab environment, we have set the Workload Analysis period and the Time to Sample
before First Analysis to two hours. In a production environment, these times would be typically
a week or more.
Please note that on VMAXe Arrays, SMC will only show the settings relevant FAST VP. VMAXe
arrays only support virtual provisioning.

To set FAST Performance Time Windows: Right click Symmetrix > FAST > FAST Control
To set FAST Performance Time Windows: Right click Symmetrix > FAST > FAST Control
Parameters > Settings
Select the Performance Time Window Tab
In this example we see that the inclusive windows allows performance gathering for all days of
the week, 24 hours a day. We also have an exclusive window which prevents performance data
gathering for a specified set of days.
If no user defined performance/move time window exists, click the New button to create one.

To set FAST Move Time Windows: Right click Symmetrix > FAST > FAST Control Parameters >
To set FAST Move Time Windows: Right click Symmetrix > FAST > FAST Control Parameters >
Settings
Select the Move Time Window Tab
Choose the Virtual Pool radio button to set FAST VP move windows.
In this example we see an inclusive move window which allows FAST VP data movement for all
days of the week, 24 hours a day.
If no user defined performance/move time window exists, click the New button to create one.

To create a new Tier: Right click the FAST folder in a Symmetrix Tier Management Create
To create a new Tier: Right click the FAST folder in a Symmetrix Tier Management Create
Tier
Once at the Tier – Create dialog box opens and a tier can be created by entering the appropriate
values in the Tier Name, Technology, and Protection fields. Once the Technology and Protection
have been picked the selection will only list the Thin Pools that meet the criteria. Check off the
Thin Pools that should belong to the tier and then click Ok to create the Tier.

Click the Virtual Pool Tiers under the Symmetrix Tiers folder to display the VP Tiers.
Click the Virtual Pool Tiers under the Symmetrix Tiers folder to display the VP Tiers.

To create a new FAST Policy : Right click a Symmetrix or the FAST folder in a Symmetrix FAST
To create a new FAST Policy : Right click a Symmetrix or the FAST folder in a Symmetrix FAST
FAST Policy Management Create Policy
A FAST Policy is a logical grouping of 1, 2, or 3 storage tiers and an assigned percentage of how
much capacity in each tier that an associated storage group can consume.
When creating a policy, the total percentage usage of all tiers combined should be at least
100%; but each tier can go as high as 100%.
One can also associate a Storage Group with the FAST VP policy while it is being created by
clicking on the Associate Storage Groups button.

Drill down into the Policies folder under the FAST folder and then into the Virtual Pool Polices
Drill down into the Policies folder under the FAST folder and then into the Virtual Pool Polices
folder to view the policy just created. Click on a specific policy to see its properties.

Storage groups can be associated with a FAST policy by:
Storage groups can be associated with a FAST policy by:
Right clicking a FAST VP Policy, then choosing FAST FAST Policy Management Associate
Storage Group
Or
Right clicking a Storage Group, then choosing FAST FAST Policy Management Associate
FAST Policy
The creation of Storage Groups with SMC was covered earlier in the Autoprovisioining module.
When creating Storage Groups for devices that have to be placed under FAST control, the
storage group must be associated with a FAST policy in order to bring it under FAST or FAST VP
control.
Note: that a Storage Group can be associated with only one policy.
Note: that Storage Groups can be associated with a FAST policy while the policy is being created.

An examination of the FAST policy called ALL100 shows that the policy contains three tiers
An examination of the FAST policy called ALL100 shows that the policy contains three tiers
RAID1_FC_VP , RAID5_EFD_VP and RAID6_SATA_VP.
Each tier has a limit of 100% usage. This means that the Symmetrix is allowed the flexibility to
make tier movement decisions based exclusively on the FAST VP algorithms. There is one
storage group called sun200_FVP that is associated with this policy.

An examination of the storage group sun200_FVP shows that the data on devices 24D:24E, is
An examination of the storage group sun200_FVP shows that the data on devices 24D:24E, is
allowed to reside in tiers RAID1_FC_VP, RAID5_EFD_VP and RAID6_SATA_VP.
Since the Max SG% is 100% for all pools, the group may have all its storage located in either tier
- depending on the discretion of FAST.
Currently, all the storage is being used from the RAID1_FC_VP tier.

A view of the three pools that belong to the tiers in the FAST VP policy, confirms what we saw
A view of the three pools that belong to the tiers in the FAST VP policy, confirms what we saw
earlier.
One hundred percent (100%) of sun200_FVP storage is being provided by the 2FCR1 pool.

A screen from the ‘Demand’ folder also shows that sun200_FVP is occupying space in the FC
A screen from the ‘Demand’ folder also shows that sun200_FVP is occupying space in the FC
Tier.

We now generated some write I/O (8K random reads and 8K random writes) to both Thin
Devices using a Unix program called IORATE.
IORATE is a piece of shareware that was developed at EMC and is available on the EMC website
at the ftp://ftp.emc.com/pub/symm3000/iorate/ .
IORATE is capable of running on all Unix platforms.
As time passes, we see that the storage allocation is almost entirely in the EDF tier, because the
EDF tier performs better than the FC and SATA tiers for the workload that we ran.

Copyright © 2012 EMC Corporation. All rights reserved 23
•Implement FAST and FAST VP using SYMCLI
Module 2: Managing FAST VP

FAST VP requires a license key.
FAST VP requires a license key.
License keys for each Enginuity software product are obtainable from EMC and entered and
viewed using the symlmf command.

The performance time windows used by FAST VP are shared with Optimizer and FAST.
The performance time windows used by FAST VP are shared with Optimizer and FAST.
Two types of data movement windows can be created – one that determines when full LUN
movement can occur for Optimizer and FAST, and another that determines when sub-LUN
movement can occur for FAST VP.
Time windows to be used by FAST VP can be created with the symtw SYMCLI command or via
SMC. The time window should specify the information shown on the slide.

The default performance time window is an “inclusive” window that collects performance
The default performance time window is an “inclusive” window that collects performance
metrics 24-hours a day. The are no default data movement windows. This by default FAST VP
will not move any data.

An inclusive move time window must be specified to allow FAST VP to move extents to the
An inclusive move time window must be specified to allow FAST VP to move extents to the
appropriate tier. In this example we have setup an inclusive move window for FAST VP which
allows moves round the clock. Multiple include and exclude windows can be defined as
required.

In the example shown an exclusive time window is setup to prevent performance data collection
In the example shown an exclusive time window is setup to prevent performance data collection
for over a specific weekend.
To achieve the full benefit of FAST, it is important that only IO activity during time windows that
represent the critical workloads is considered in the calculations, and activity during time
periods where the workload is not characteristic is excluded.
For example, the workload during normal business hours may be important, but IO activity
when backup is running could be disregarded. This is referred to as the Performance Collection
Window and defines the dates and times to include or exclude IO activity. Multiple include and
exclude windows can be defined as required.

Check the FAST VP Status
Check the FAST VP Status
If FAST VP is not enabled on the Symmetrix, it can be enabled by using the command:
symfast -sid <SymmID> enable -vp

The initial analysis period (min_perf_period) specifies a period of time that performance data is
The initial analysis period (min_perf_period) specifies a period of time that performance data is
initially gathered before FAST makes any performance based configuration change plans. This
value is specified in hours and can be set for 2 to 672 hours (4 weeks).
In our lab environment, this parameter was set to two hours. In a production environment, the
time would be typically one or more days.
The FAST Engine workload analysis period (workload_period) specifies the number of samplings
that FAST will consider for performance analysis. This is typically set for days or weeks so that
uncharacteristic peaks in activity do not result in movement.
In our lab environment, this parameter was set to two hours. In a production environment, the
time would be typically a week or more.
The VP data move mode applies to Thin Devices. Values can be set to Auto or None.
The VP relocation rate determines the aggressiveness of data movement for Thin Devices.
The pool reserved capacity (PRC) is a percentage of the capacity of each virtual pool that will be
reserved for non-FAST activities. If the free space in a given pool (as a percentage of pool-
enabled capacity) falls below the PRC, the FAST controller does not move any more chunks into
that pool.
To move any new chunks to the pool, the FAST controller must first move some chunks from
that pool to another pool to free up space. Enforcement of the PRC is best-effort; FAST may
move chunks to a virtual pool resulting in a violation of the PRC, because non-FAST activities
(such as new allocations for writes to a Thin Device) can simultaneously consume pool free
capacity. The minimum value is 1, the maximum is 80, and the default is 10.

Here we set the FAST VP control parameters and examine them after they are set.
Here we set the FAST VP control parameters and examine them after they are set.

The three thin pools listed on the slide will be used to demonstrate the implementation of FAST
The three thin pools listed on the slide will be used to demonstrate the implementation of FAST
VP in this module.
The pool, 2FCR1, has used tracks, because it has pool bound Thin Devices as shown on the next
page.
The three pools have different RAID types and different disk technologies.

The two Thin Devices bound to pool 2FCR1are currently 92 percent allocated and are using 61%
The two Thin Devices bound to pool 2FCR1are currently 92 percent allocated and are using 61%
of the available pool space.
The Thin Devices are already part of a larger storage group that has been mapped to this host
using the masking view called sun200_mv as the following output shows:
sun200 /VMAXe> symaccess show sun200_sg -sid 95 -type storage
Symmetrix ID : 000195900495
Storage Group Name : sun200_sg
Last updated at : 11:47:08 AM on Tue Nov 29,2011
Devices : 0035:003A 0203:0205 024D:0250
Masking View Names
{
sun200_mv
}

Here we create a new storage group sun200_FVP and then add devices 24D:24Eto this new
Here we create a new storage group sun200_FVP and then add devices 24D:24Eto this new
group.
Storage group sun200_FVPGroup will be used for FAST VP management.

Here we create three thin tiers:
Here we create three thin tiers:
RAID1_FC_VP contains the Thin Pool 2FCR1. That pool has RAID 1 devices and resides on 15K
RPM FC drives.
RAID5_EFD_VP contains the pool 1EFDR5. It is RAID 5 protected and resides on EFD disk drives.
RAID6_SATA_VP contains the pool3SATAR6. It is RAID 6 protected and resides on 7200 RPM
SATA drives.

Here we create a policy 50FC50SATA_VP that states that 50% of Thin Device storage associated
Here we create a policy 50FC50SATA_VP that states that 50% of Thin Device storage associated
with the policy must be on the tier RAID1_FC_VP and the other 50% should be on the tier
RAID6_SATA_VP.

The storage group sun200_FVP has all its storage associated with pool 1FCR1 at the time it was
The storage group sun200_FVP has all its storage associated with pool 1FCR1 at the time it was
created. Consequently, the association of the storage group sun200_FVP with the policy
50FC50SATA_VP causes the storage group to be non-compliant.

This command shows that the storage group sun1_FastVPGroup has exceeded the allowed
This command shows that the storage group sun1_FastVPGroup has exceeded the allowed
capacity in tier RAID1_FC_VP by 873MB, while there is room for it to grow 1032MB in the tier
RAID6_SATA_VP.

After some time elapses, FAST VP moves enough allocated tracks from pool 2FCR1 to 3SATAR6
After some time elapses, FAST VP moves enough allocated tracks from pool 2FCR1 to 3SATAR6
to bring the storage group into policy compliance.
FAST VP has a tolerance level of 200 MB. A growth potential of 159 MB is not an issue since the
FAST VP usage of storage in the pool is within policy constraints.
A growth potential of -99 shows that tier usage exceeds allowable limits by 99 MB. This falls
within the 200 MB tolerance.

After the FAST VP move, part of the Thin Device allocation is hosted by pool 2FCR1 and …
After the FAST VP move, part of the Thin Device allocation is hosted by pool 2FCR1 and …

…the remainder of the TDEV allocations is hosted by the pool 3SATAR6.
…the remainder of the TDEV allocations is hosted by the pool 3SATAR6.
Note: that though the Thin Devices are bound to pool2FCR1, some of the storage is located in
the3SATAR6.

Here we create a policy ALL100 that states that 100% of Thin Device storage associated with the
Here we create a policy ALL100 that states that 100% of Thin Device storage associated with the
policy may be on any of the three tiers RAID5_EFD_VP, RAID1_FC_VP or RAID6_SATA_VP.

Before associating the sun200_FVP storage group with the new policy, we have to dissociate it
Before associating the sun200_FVP storage group with the new policy, we have to dissociate it
form the FAST VP policy that it was currently associated with.
After association with the new policy, we examine the association and the tiers participating in
the new policy.

This command shows that the storage group sun200_FVP is policy compliant. In this example
This command shows that the storage group sun200_FVP is policy compliant. In this example
we have set the Max SG percent for each of the tiers to 100%, thus the storage group will
always be policy compliant.
All the storage is currently distributed between the FC and SATA Tiers. The EFD tier is currently
unused.

Devices using a Unix program called IORATE.
IORATE is a piece of shareware that was developed at EMC and is available on the EMC website
at the ftp://ftp.emc.com/pub/symm3000/iorate/ .
IORATE is capable of running on all Unix platforms.
We inspect the demand report after running I/O to the Thin Devices after some time has
elapsed, almost all the allocations are now in the EFD tier.

Key points covered in this class:
Key points covered in this class:
•FAST VP implementation
• Time windows
• FAST VP Control Parameters
• FAST VP Tiers
• FAST VP Policies
• Association of storage groups with FAST VP policies
• FAST VP compliance moves
• FAST VP performance moves

Please feel free to contact me if you have any questions.
Please feel free to contact me if you have any questions.
Kevin Wang (kevin.y.wang@emc.com)

FAST VP Step by Step Module 2

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to FAST VP Step by Step Module 2

Similar to FAST VP Step by Step Module 2 (20)

FAST VP Step by Step Module 2