Вы находитесь на странице: 1из 4

EMC Symmetrix Uptime Bulletin

A newsletter from SVPG Engineering


Volume 16—December 2010

Virtual Provisioning Best Practices


Inside this issue:
Virtual Provisioning, one of the most popular features of the Symmetrix® platform, offers many benefits
over standard provisioning—ease of use, speed of deployment, device-level wide striping, and improved Virtual Provisioning 1
capacity utilization. Best Practices
Many Symmetrix users that deploy Virtual Provisioning choose to maximize their capacity utilization by DRT Corner 2
oversubscribing their virtual pools. Oversubscription allows the storage administrator to allocate more
storage to virtual volumes than is physically available in the virtual pool. The alternative to oversubscrip-
Symmetrix Target 3
tion is one-to-one subscription, where the total virtual volume space is available in the virtual pool. The
Code Versions
following discussion applies to oversubscription only.
To ensure that a pool-full condition is not encountered when deploying oversubscribed virtual pools, the EOSL: 5670 3
following actions must be taken by the storage administrator: 5771
5772
• Configure alerts for virtual pool utilization
• Configure management tools to receive SNMP traps when virtual pools are nearing capacity Recent Symmetrix 4
• Monitor allocation and utilization trends over time ETAs

• Plan to add more capacity before existing capacity is completely used up Solutions Enabler 4
Best Practices: Meta
Management of Virtual Pools: Expansion
Symmetrix Management Console (SMC) or SNMP traps must be configured to alert when nearing capacity
full conditions. The Solutions Enabler symevent daemon can be configured to monitor virtual pool utili-
Useful Links 4
zation and to send SNMP traps to a service management platform when user configurable thresholds are
crossed. Monitoring EMC Symmetrix Using the Solutions Enabler Event Daemon Technical Note provides Find us on Powerlink:
details about how to configure the symevent daemon. http://powerlink.emc.com
Symmetrix Performance Analyzer (SPA) or EMC Ionix™ ControlCenter StorageScope™ should be deployed Products >
to monitor allocation and utilization trends over time. Monitoring trends will help identify unusual spikes Hardware/Platforms >
in utilization that may be caused by applications that are not thin friendly. Monitoring also allows the Symmetrix > [Model] >
storage administrator to anticipate when additional capacity should be added to a virtual pool in order to Uptime Bulletins
meet growing demands.
OR
It is imperative to add capacity to a virtual pool when an alert indicating near full capacity is received.
There are several ways to accomplish this: Products >
Hardware/Platforms >
• Adding Data Devices • Unbinding Thin Devices • Performing Zero Reclaim Symmetrix > VMAX >
Uptime Bulletins
Best Practices for Fast Simple Capacity Allocation with EMC Symmetrix Virtual Provisioning Tech Note Subscribe to future Uptime
provides details on performing each operation. The symcfg monitor command can be configured to exe- Bulletins by clicking on the
cute a script to add capacity to a virtual pool automatically when a high utilization threshold is crossed. EMC Symmetrix
Monitoring and trending must work with an understanding of the length of your procurement cycle. At Consolidated Edition “Alert
many locations, the procurement cycle requires justifying a purchase and obtaining several levels of ap- Me!” icon.
proval. Once received, the new hardware must also be installed and configured before it can be allocated
to increase the available space.
Pool-full conditions can be avoided by monitoring allocation and utilization trends over time, setting up
alerts for thin pool utilization and understanding the procurement cycle.
Contact us:
For more detailed information, see the documents above, available in Powerlink®. Also see Powerlink > UptimeFor
Support > Technical Documentation for SMC, SPA, and ControlCenter. Symm@emc.com
Page 2 Uptime Bulletin: EMC Symmetrix Edition

DRT Corner: DR Solution Deployment Best Practices


Business Impact Analysis
Business impact analysis (BIA) is an essential component
of an organization's business continuance plan. It can
reveal vulnerabilities and aid in the development of
strategies for minimizing risk. The output of this exercise
should be a business impact analysis report, which de-
scribes the potential risks specific to the organization
studied. One of the basic assumptions behind BIA is that
every component of the organization is reliant upon the
continued functioning of every other component, but that
some are more crucial than others and require a greater
allocation of funds in the wake of a disaster. Replicate
and mirror what’s important to your business.
Ensure Remote Replication Strategy is Sound and Sized for Growth
Inspect your current SRDF® strategy and be sure that it is resilient and still sized appropriately for your workload prior to deploying
your GDDR solution. If you are deploying a new SRDF replication solution, make certain that each of your infrastructure teams is aware
and on board with the solution being deployed.
Project Planning
Construct a detailed task-level plan and base the project duration on the sum of each task’s time to be undertaken. A common mistake
is to estimate the time by “drawing a line in the sand,” which if wrong will create needless pressure on the project and a temptation to
take shortcuts with quality in order to hit deadlines. It is imperative that all infrastructure business leaders are aligned and involved in
planning your Geographically Dispersed Disaster Restart (GDDR) deployment. The level of complexity within your environment will be a
key factor in the time to deploy. When deploying complex solutions, it is also important to review and enforce a rigid change control
process to reduce the risk of production impact. This level of discipline may extend project timelines, but will protect your business.
Test Environment
A test environment allows testing of infrastructure and software components outside of the production environment. The benefit is
that problems can be detected in these environments prior to production deployment. Test environments also allow operations staff to
obtain and maintain competency without “learning” on live production environments. Without a test facility, your operations staff may
be reluctant to be involved in or may not have a clear understanding of the impact of change in your environment.
Training
Training is essential to build competency in the operations staff. Without a test environment, training is limited to theory. If a test
environment is deployed, even if only for the duration of the project, the operations staff can become competent in an environment
where mistakes can be made without business impact.
Infrastructure
A common cause of failure for large-scale infrastructure projects is poorly and improperly sized solutions. The following bullets cover
these common areas of failures and methods to mitigate the risks.
• Network Infrastructure: EMC has sophisticated design tools that can be used to determine customer bandwidth requirements
whether or not the existing solution is on EMC equipment. Take the time to measure the bandwidth requirement. If you do not
know what tools are available or how to use them, contact your TC (Technical Consultant) to work with a local Mainframe Cham-
pion. Check with the GDDR Solution Support Team to ensure that your network design meets current best practice standards.
• Storage Infrastructure: Complex replication solutions use more resources in arrays than solutions that do not use replication. It is
vital to ensure that the proposed solution is validated to run the proposed infrastructure. Contact your TC to work with a local
“SPEED Guru” to ensure that the proposed solution will be able to sustain the workload and the additional overheads imposed by
replication. A well-designed solution will also have residual capacity to recover from drive rebuilds and planned growth in I/O
workload and capacity.

Symmetrix Power Up for VMAX and DMX-3/4


Drive bays first and system bay last.
You want to have all the drives spinning before powering up the system bay. The power-up sequence is the op-
posite of the power down sequence. More details are available in the the Symmetrix Q1 10 Uptime Bulletin.
Uptime Bulletin: EMC Symmetrix Edition Page 3
Symmetrix Target Revisions
EMC has established target revisions for each product to ensure stable and reliable environments. As a
best practice, it is recommended that you operate at target code levels or above to benefit from the
latest enhancements and fixes available. Search “adoption rates” in Powerlink for current Symmetrix
target code adoption rates.
Enginuity SPA SPA Recommended Enginuity SMC SMC Recommended
Version Version
Revision Minimum Version Revision Minimum Version
5671 1.0.0 2.0.1 5671 6.0.1 6.1.2
5771 1.0.0 2.0.1 5771 6.0.1 6.1.2
5772 1.0.0 2.0.1 5772 6.0.2 6.1.2
5773 1.0.0 2.0.1 5773 6.1.0 6.1.2
5874 1.1.0 2.0.1 5874 7.0.0 7.1.2
Enginuity SE Minimum Version Recommended Enginuity MFE Minimum Recommended
Revision Version Revision Version Version
5671 6.5.0 6.5.3 5671 v5.8.0 (EMC5804) v7.0 (EMC7004)
5771 6.5.0 6.5.3 5771 v5.8.0 (EMC5804) v7.0 (EMC7004)
5772 6.5.0 6.5.3 5772 v5.8.0 (EMC5804) v7.0 (EMC7004)
5773 6.5.0 6.5.3 5773 v5.8.0 (EMC5804) v7.0 (EMC7004)
5874 7.0.0 7.1.2 5874 v7.0 (EMC7004)* v7.0 (EMC7004)
Note: For Solutions Enabler, always refer to Knowledgebase article Note: For Mainframe Enablers, always refer to Knowledgebase
emc201214 for any special considerations. article emc138978 for any special considerations.
* If VMAX is in your configuration, you must be running 7.0!

Symmetrix Model Enginuity Revision Released % Systems Upgrading to the target


revision at least twice a
DMX800, DMX1000, 5671.80.77 04/23/2009 > 34% year is an EMC best
DMX2000, DMX3000 practice. The current target
DMX-3 5771.114.121 08/27/2010 > 1% revisions are located at:
5772.105.94 03/18/2010 > 3% Powerlink > Support > Inter-
Enginuity 5670 is End-of- 5773.160.111 06/08/2010 > 8% operability and Product
Service-Life and is no DMX-4 5772.105.94 03/18/2010 > 3% Lifecycle Information > Tar-
longer supported. get Revisions and Adoption
5773.160.111 06/08/2010 > 8%
Upgrading to 5671 is an Rates
VMAX 5874.230.183 05/26/2010 > 63%
NDU (non-disruptive up-
grade) and adds features!
5771 End-of-Primary-Support on 10/31/2010
Enginuity 5771 and 5772 should be upgraded (NDU) to 5773
Effective October 31, 2010, Enginuity 5771 became End-of-Primary-Support (EOPS) and End-of-Service-Life (EOSL). Maintenance con-
tracts will no longer be renewed for DMX-3 products running Enginuity 5771.
In addition, on March 31, 2011, EMC will discontinue support for Enginuity
5772. Maintenance contracts will not be renewed for DMX-3/4 products Enginuity
running Enginuity 5772 at that time. EMC advises customers to upgrade Release GA Date EOPS EOSL
to Enginuity 5773 to benefit from enhanced support, new features, im- 5567 12/01/00 10/31/2011 10/31/2011
proved performance, and increased stability. Updating to the latest 5773
5568 01/01/02 10/31/2011 10/31/2011
will help assure that hardware support on memory, director, and disk drive
replacements are available. 5670 08/01/03 01/31/2009 01/31/2009
5671 02/01/05 N/A N/A
If you are under warranty or have an active maintenance contract with EMC,
please contact your EMC Sales representative or Customer Engineer to 5771 08/01/05 10/31/2010 10/31/2010
schedule the installation of this no-charge upgrade to Enginuity 5773 at 5772 03/01/07 03/31/2011 03/31/2011
your earliest convenience. 5773 03/01/08 N/A N/A
Customers not covered under warranty or current maintenance contracts, 5874 04/14/09 N/A N/A
please contact EMC to discuss your upgrade options.
Page 4 Uptime Bulletin: EMC Symmetrix Edition
Recent Symmetrix ETAs
Solution ID Symmetrix Technical Advisories

Symmetrix VMAX: Large I/O on FBA meta devices could trigger host timeouts at Enginuity 5874.240.191 and
ETA emc250947
5773.160.111
Symmetrix VMAX: Clone, Virtual SNAP, and Extent SNAP operations may fail in FICON environments running
ETA emc248499
Enginuity 5874.229.182 or 5874.230.183
ETA emc236463 Symmetrix DMX-3, DMX-4, and VMAX: Enginuity 5773 and 5874 while using PowerPath®/VE—Virtual machines
periodically hang, become unresponsive, and disappear from the VI Client after installing PowerPath/VE

An EMC Technical Advisory (ETA) identifies an issue that may cause serious negative impact to a production environment.
You can find the complete ETA list on Powerlink at Support > Technical Documentation and Advisories > Technical Advisories >
Symmetrix—Customer ETA List

Solutions Enabler Best Practices:


Preserving Data During Meta Expansion
Once you have successfully created an initial meta with metamembers, you can add additional metamembers as necessary. What you
may not realize is that you can preserve your existing data while expanding striped metadevices. When expanding a striped metade-
vice, you can specify a BCV meta to preserve the original data, which will be rewritten to the newly configured striped metadevice. To
add additional members to an existing striped metadevice, use the following form:
add dev SymDevName[:SymDevName] to meta SymDevName, protect_data=TRUE, bcv_meta_head=SymDevName;
By setting the protect_data option (only available for striped metas) to a value of true, Configuration Manager automatically creates a
protective copy to the BCV meta of the original device striping. Because this occurs automatically, there is no need to perform a BCV
establish. When enabling protection with the protect_data option, you must specify a BCV meta identical to the existing (original)
striped meta. In addition, when adding new members to an existing striped metadevice, if the data on the metadevice is to be pro-
tected, you must specify the name of a BCV meta that matches the original metadevice in capacity, stripe count, and stripe size.

Useful Links
E-Lab™ Interoperability Navigator https://elabnavigator.emc.com

EMC Symmetrix Procedure Generators Powerlink > Support > Product and Diagnostic Tools > Procedure Generators

Symmetrix Support Matrix E-Lab Interoperability Navigator > PDFs and Guides > ESM by Storage Families

E-Lab Issue Tracker Powerlink > Support > Interoperability and Product Lifecycle Information > E-Lab Issue Tracker
Information > E-Lab Issue Tracker

EMC believes the information in this publication is accurate as of its publication date. The infor-
mation 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 ap-
EMC Corporation plicable software license.
176 South Street EMC2, EMC, E-Lab, Enginuity, Ionix, Powerlink, PowerPath, SRDF, StorageScope, Symmetrix, Sym-
Hopkinton, MA 01748 metrix DMX, Symmetrix VMAX, and where information lives are registered trademarks or trade-
marks of EMC Corporation in the United States and other countries. All other trademarks used
Phone: 508-435-1000 herein are the property of their respective owners. Copyright © 2010 EMC Corporation. All rights
Email: UptimeForSymm@emc.com reserved. Published in the USA. 12/10