EMC Proven Professional Knowledge Sharingeducation.emc.com/main/common/documents/ks_articles/knowledg… · Thomas Mitrovits , Global Development ... sync, consistent fracture, resume

$Page 1: EMC Proven Professional Knowledge Sharingeducation.emc.com/main/common/documents/ks_articles/knowledg… · Thomas Mitrovits , Global Development ... sync, consistent fracture, resume$
Compilation

EMC Proven™ ProfessionalKnowledge Sharing

Abstracts 2007

Compilation of Abstracts Submitted by EMC Proven Professionals for EMC’sFirst Annual Knowledge Sharing Initiative

EMC Proven Professional Knowledge Sharing 2

Disclaimer: The views, processes or methodologies published in this compilation are those of theauthors. They do not necessarily reflect EMC Corporation’s views, processes, or methodologies.

Edited by Michelle Lavoie, EMC Global Services(Education Services)

Best Practices for Deploying FCIP and iFCP Solutions Using ConnectrixMulti-Protocol Routersby Venugopal Reddy (EMC Corporation)

Migration of File Servers to NAS and Multi-Tiered Storage by Bryan Horton (A Leading Healthcare Provider)

Challenges and Best Practices in the Deployment and Managementof IPTV Networksby Paul Brant (EMC Corporation)

Best Case Study—Storing Taming the Data Tiger by John Bowling (Busata Systems)

Best Case Study—Protecting Local Replication and Availabilityin a CLARiiON Environment: The Clone Task Force by Fernando Moreno Liso (Comparex)

Best Case Study—Optimizing StorageScope Validates Storage Area Network before Migration to New SAN by Barry Nelson (EMC Corporation)

3rd

2nd

1st

The Winners

Contents

Introduction ....................................................................................................................6

Serial Advanced Technology Attachment (ATA) Drives in CLARiiON ArraysVictor Franco, Lead Instructor, Education Services, EMC Corporation ................................7

Local Replication and Availability in a CLARiiON Environment: The Clone Task ForceFernando Moreno Liso, Systems Executive Engineer, Comparex ......................................8

How CLARiiON Helped our Exchange OrganizationTodd Simmons, Senior Consultant, Citizens Bank ............................................................9

Choosing the Right CLARiiON Data Replication Method: A Performance-Based ApproachAndre Rossouw, Advisory Technology Solutions Educational Consultant, EMC Corporation......10

CLARiiON Performance Monitoring ScriptingDerek Yu, Senior Consultant, Bell ICT Solutions ..............................................................11

Best Practices for Deploying FCIP and iFCP Solutions Using ConnectrixMulti-Protocol RoutersVenugopal Reddy, Senior Engineer, Problem Resolution & Escalation, EMC Corporation ..12

Brocade Fibre Channel Routing (FCR) Technology Overview and FundamentalsJoe Holbrook, Consultant, Brocade Solutions ................................................................13

The Importance of Being EarnestAlastair Adamson, SAN Architect ..................................................................................14

Real-Life Challenges in Today’s Storage WorldKiran Ghag, Senior Systems Administrator, HSBC ..........................................................15

How to Deploy a Celerra iSCSI Solution John Shubeck, Technical Business Consultant, EMC Corporation ....................................16

Setting Up an Invista EnvironmentAdam Jones, Senior Technology Consultant, EMC Corporation ........................................17

Deploying an SQL 2005 Cluster in a Virtualized SAN EnvironmentBartley Corbin, Implementation Specialist, EMC Corporation ..........................................18

Backing Up a Large Oracle Database with EMC NetWorker and EMC Business ContinuitySolutionsMaciej Mianowski, Regional Software Specialist, EMC Corporation ................................19

Designing and Implementing a Backup, Recovery, and Archiving (BURA) Solution in a Pharmaceutical CompanyCarmen Marcano, Solutions Architect, EMC Corporation ................................................21


Contents

NetWorker Best Practices—Designing for PerformanceMatt Steinberg, Senior Solutions Architect, Cambridge Computer Services Inc. ..............22

Integrating the EMC Disk Library with Veritas NetbackupAdam Jones, Senior Technology Consultant, EMC Corporation ........................................23

EMC NetWorker: Wearing Belts and Suspenders—Suggestions for Improving Security, Performance, and Life-Span using EMC NetWorkerTor Eikanger, Senior Systems Engineer, Ementor Norge AS ............................................24

Utilizing EMC Replication Technologies to Help Save Texas Electricity ConsumersBillions of DollarsMichael Solari, Manager, Storage Engineer, Electric Reliability Council of Texas ..............25

Implementing Replication Manager/SE for ExchangeCarl Granfelt, Storage Implementation Consultant, Posetiv Ltd.......................................26

Symmetrix Local Replication from A-Z: All the Choices and Which to ChooseDonald Fried-Tanzer, Education Services Consultant, EMC Corporation............................27

Mainframe SRDF/A and MSC Best PracticesMichael Smialek, Solutions Architect, EMC Corporation ................................................29

Backup-to-Disk for Mainframe using the Mainframe Disk LibraryDoug Morris, Senior Technical Consultant, EMC Corporation ..........................................30

Stars of EMCDavid Pena, Technology Consultant, EMC Corporation ....................................................31

An International Mainframe Consolidation Project: Strategy and TechnologyMichael Zimmermann, Account Technology Consultant, EMC Corporationand Richard Herbst, Technical Business Consultant, EMC Corporation ............................32

StorageScope Validates Storage Area Network before Migration to New SANBarry Nelson, Solutions Architect, EMC Corporation ......................................................33

Global Storage Resource ManagementRich Ayala, VP Senior Architect, A Leading Financial Institution ......................................34

Taming the Data TigerJohn Bowling, Data Architect, Busata Systems ..............................................................36

Automation of Customized and Localized Reporting SungWook Hyung, Senior Technology Consultant, EMC Corporation ..............................38


Contents

Data Gathering and Analysis for Migration, Disaster Recovery, and BusinessContinuance in Symmetrix Environments: The Solution Architect’s Role Michael Schwartz, Senior Solutions Architect, EMC Corporation ....................................39

Migrating Data from DMX1000 to DMX-3Henry Zhang, Senior Infrastructure Specialist, EDS ........................................................41

Migration of File Servers to NAS and Multi-Tiered StorageBryan Horton, Systems Engineer, A Leading Healthcare Provider ..................................42

ISL Security Monitoring within EMC MirrorView/SRDFThomas Mitrovits, Global Development Business Manager—Storage Networking, ADVA Optical Networking AG ........................................................................................43

EMC Security Initiatives: A Market DifferentiatorJenny Beazley, Senior Project Manager, EMC Corporation ..............................................44

Challenges and Best Practices in the Deployment and Management of IPTV NetworksPaul Brant, Senior Advisory Technology Consultant, EMC Corporation ............................46

Project Delivery Approach: Pre-work or Re-work?Lalit Mohan, Senior Solutions Architect, EMC Corporation..............................................47

Business Information Management Reengineering (BIMR)Eugene Demigillo, Technical Development Consultant, EMC Corporation ........................48


Introduction

The EMC Proven™ Professional program was developed in response to the growing demandfor storage and IT professionals with the knowledge and skills to store, protect, optimize, andleverage their information infrastructures. There is an industry-acknowledged requirementfor increasing levels of expertise, and the program has begun to play an important role inhelping participants to assess, acquire, and validate the skills required to build and manageefficient information storage and management environments.

The Knowledge Sharing initiative creates a platform for EMC Proven-certified professionals toshare their work, best practices, and experiences with other fellow certified professionals. In ourfirst year, this initiative attracted dozens of submissions from EMC® customers, partners, andemployees. We are proud to have abstracts and papers from around the globe and to createa global community of EMC Proven Professionals who are willing to share their experiences.

On behalf of EMC Education Services, and all of your colleagues who will learn from your work,we would like to thank everyone who submitted abstracts and papers.

Tom ClancyVice-President (Education Services)EMC Global Services

Alok ShrivastavaSenior Director (Education Services)EMC Global Services


EMC Proven Professionals

can access the complete

papers by going to

http://education.EMC.com.

Serial Advanced Technology Attachment (ATA) Drivesin CLARiiON Arrays

Victor Franco, Lead Instructor, Education ServicesEMC Corporation

Serial ATA is a computer bus technology designed to transfer data to and from a hard disk.There are three specifications regarding this technology, the third is pending.

The second-generation specs were documented mid-2004, but the implementations were notdeployed until approximately 2006. So, EMC has begun to support SATA II drives, though thisnaming convention is improper as it does not mean 3 Gb/s.

If we compare the performance of Serial ATA Disks and FC (SCSI) disks, besides the obvious dif-ferences in rotational speed, we achieve similar transfer rates. Why are we told that Serial ATA driveperformance ranges from 25 percent to 90 percent of Fibre Channel (FC) drives? This paper arguesthat the answer depends on the application. Performance is very similar for sequential access andvery different for random access.

The underlying reason is that FC drives implement a Command Queuing technology calledTagged Command Queuing (TCQ) with an effective reordering of eight (8) IOs. Conversely,Serial ATA drives do not implement this or if they do (SATA II drives use Native CommandQueuing, NCQ), they use an effective queue depth of two (2).

The implications of this technology difference impact two main areas:

• Data Safety. More head movement equals more heat generation. More heat increases thelikelihood of failure. Also, longer rebuild times yield more data exposure.

• Performance. More head movement means more time to get data serviced.

To compensate for EMC CLARiiON® arrays using Serial ATA drives, a number of counter-measures have been taken concerning data safety and data performance. This paper detailsmethods to implement sequential access to the drive and not to the logical unit number(LUN).


Local Replication and Availability in a CLARiiON Environment:The Clone Task Force

Fernando Moreno Liso, Systems Executive EngineerComparex

Designing: Needs and Challenge.Availability and protection are among the final steps in a project that included establishingan infrastructure and designing and implementing a storage information architecture.

Once the systems were in production, we needed to implement a task to keep the systemsrunning while performing availability task routines. A backup can seriously impact a customer,so we needed to test the routine under crash conditions.

This article, based upon EMC best practices, relates the challenge of implementing local replication,backup, restore, and recovery of AIX and Linux (SLES) systems with Oracle and SAP environments.

This project was successful. By scheduling automatic tasks which involved cloning, backupand re-charge of production databases in test systems; and by using scheduler tools, naviclicommands, and database scripting, we made it easy to execute one script to recover a wholedatabase information system. And, we did it twice a day.

Implementing the method.The process is simple. Every eight hours, three groups of clones for each environment (AIX orLinux, SLES) synchronize and fracture automatically. The fractured one is assigned to a backupserver then restored to a test server. This paper will provide detail on the methodology andconsideration of the sequencing of events.

While developing this method, we had to consider the implementation and integration of severaltools. These included crontab, navicli commands, SAP and Oracle scripts in order to suspend andput in special mode databases of different versions, sync, consistent fracture, resume data-base, assign, backup to a disk library, de-assign clones, restore data, and start instances intest servers without impacting production systems. This method allows us to do all thismechanically and automatically with only one click.


How CLARiiON Helped our Exchange Organization

Todd Simmons, Senior ConsultantCitizens Bank

When storage capacity and I/O demands increased, our organization quickly realized that wehad outgrown our direct-attached storage (DAS) environment. Plagued by poor performance,the inability to expand, and server sprawl, we decided it was time to consider an enterprisestorage solution for our Exchange environment.

Exchange is considered a mission-critical application for our organization. Our environmentsupports over 27,000 mailboxes and processes an average of 1.1 million internal messages daily.Performance, capacity, and expandability are absolute requirements.

In addition to the absolute requirements we also hoped to remedy some existing pain pointsby installing an enterprise storage solution. As a result, ease-of-use, dynamic reconfiguration,backup and restore, disaster recovery capability, and support for Exchange Server 2007 wereall added to the list.

The EMC CLARiiON SAN was the only solution we found that met all of our requirements.

This paper details how we implemented the CLARiiON SAN.


Choosing the Right CLARiiON Data Replication Method: A Performance-Based Approach

Andre Rossouw, Advisory Technology Solutions Educational ConsultantEMC Corporation

CLARiiON storage systems offer a variety of methods to replicate data. Local data replicationmay be performed with SnapView™ Snapshots, SnapView Clones, and SAN Copy™. Remotedata replication may make use of SAN Copy, MirrorView™/A, or MirrorView/S. Replication isdefined as making copies without destroying the original data; as a result, logical unit number(LUN) migration is not included in this paper.

Each replication product has its own advantages and disadvantages, depending on uniquecustomer requirements. Choosing a replication product is even more difficult when methodsare combined, for example MirrorView/S with Snapshots, or SAN Copy with Clones. In somecases, copies of the data are required only at a remote location, while in others the dataneeds to be copied locally and remotely.

Customers require data backups with minimal disruption; they require their data to be protectedand secured. This paper reviews the various ways that CLARiiON replication software may beused to meet specific business needs, and makes recommendations based on customerrequirements and the characteristics of the solution. This approach ensures the least impacton scheduled business activities.

We will use Navisphere® Analyzer and Analyzer archive files captured from storage systemsrunning representative data access patterns to illustrate and support our conclusions.


CLARiiON Performance Monitoring Scripting

Derek Yu, Senior ConsultantBell ICT Solutions

CLARiiON Navisphere Analyzer is a great performance monitoring tool for the CLARiiON array.It gathers storage system performance statistics and presents them visually in various typesof charts. It can help you to identify bottlenecks in the disk storage component of a computersystem, but you have to access it through Web-based Navisphere Manager and view eachCLARiiON array separately.

Based on large enterprise customers’ requests, we crafted a scripted approach that has beenimplemented and well accepted. This CLARiiON performance monitoring solution is based onNavisphere Analyzer and performs three major functions:

• Retrieves CLARiiON performance raw data,

• Extracts specific SP/LUN/DISK (storage processor/logical unit number/disk) performancemetrics,

• Generates daily CLARiiON performance reports.

This paper provides average and maximum values of all selected CLARiiON performance metricsfor a quick overview. Daily CLARiiON performance reports are maintained indefinitely to conductperformance trending analyses. The raw performance data (NAR files) can be kept for the longterm in the event that further investigation or reference to a specific time frame is required.

This is a centralized monitoring solution, running on a single monitoring server. It can be easilyscaled to include multiple CLARiiON arrays at the same or different locations. It can also beexpended to be application aware, i.e., SQL Server database, Exchange storage groups, andOracle databases.


Best Practices for Deploying FCIP and iFCP Solutions UsingConnectrix Multi-Protocol Routers

Venugopal Reddy, Senior Engineer, Problem Resolution & EscalationEMC Corporation

Extending Fibre Channel (FC) storage area networks (SANs) over medium to wide area distancesutilizing Internet Protocol (IP) networks is becoming increasingly prevalent as IP networks areubiquitously available and larger IP bandwidth capacities are a fraction of the cost of Fibre channel.

FCIP (Fibre Channel over IP) and iFCP (Internet Fibre Channel Protocol) are the two protocolsthat are widely used to implement these extensions of geographically spread Fibre Channelnetworks. Synchronous and asynchronous data replication for data protection and remotereplication, remote tape consolidation, and remote storage pools are some of the applicationsof these IP-based SAN extension solutions. Multi-protocol routers that convert Fibre Channeltraffic to IP traffic for transport are used in deploying these solutions. Currently Brocade, Cisco,and McDATA are three of the prominent vendors that offer these IP-based multi-protocol routers.

However, Fibre Channel storage traffic spikes and then drops, affecting the IP-SAN solutionimplementations. Traditional TCP/IP stacks tend to overreact to spikes of traffic, resulting inexcessive slow starts and retransmissions. In order to flatten the “burst” of the FC traffic andto sustain high throughput, vendors implement features such as storage-optimized TransmissionControl Protocol (TCP) stacks, Fast Write, and tape pipelining in their solutions.

This paper compares and contrasts the features of storage-optimized TCP solutions by threevendors (Brocade, Cisco, and McDATA) and reviews best practices to deploy these solutions.The discussion examines the following aspects of implementing an IP-based SAN solutionusing multi-protocol routers:

• How do we size the solution based on required I/O throughput and available bandwidth?

• How do we design a solution that ensures reliability, availability, and serviceability?

• How do we secure an IP-based SAN solution?

• How do we deploy an IP-based SAN solution?

• How do we ensure sustained application performance?

Due to the interdisciplinary nature of IP-based SAN solutions, the design and deployment ofthese solutions tends to be complex and the vendor documentation often tends to be scatteredand limited to product features. This paper bridges the gap by defining the characteristics of anIP-based SAN solution, contrasting the features among the products of the three vendors,and detailing best practices for implementation.


Brocade Fibre Channel Routing (FCR) Technology Overviewand Fundamentals

Joe Holbrook, ConsultantBrocade Solutions

Designing a storage area network (SAN) fabric requires a concise understanding of the customer’scurrent and future requirements. SAN fabrics in most large environments have exceeded orsoon will be exceeding the current scalability limits of the SAN solution.

The rapid growth and increasing complexity of SANs has been the driving force behind theadoption of multi-protocol SAN routers. Brocade has developed routing services that increaseSAN functionality, scalability, and flexibility. These services are a significant evolution for storagenetworks.

Merging SAN fabrics is complex and time-consuming for SAN administrators and SAN engineers.Brocade SAN fabrics can be expanded without merging fabrics via Fibre Channel Routing (FCR)protocols. In this article, we present both the fundamentals of Fibre Channel Routing (FCR) andBrocade best practices in meta-SAN design. Best practices are highlighted and presented in acase study format, making them easy to understand and to apply in the work environment.


The Importance of Being Earnest

Alastair Adamson, SAN Architect

As SANs grow with more servers and disks, and gain complexity with the implementation ofdisaster recovery and meta-SANs, it is important to maintain control and to fully understandthe implemented architecture. This requires proactively ensuring coherence and consistencyrather than just setting up some management and monitoring tools and reactively addressingproblems as they occur. A few judiciously written scripts, based on a solid rule set, can greatlyhelp the administrator by providing information that is not readily available elsewhere.

While there are many powerful vendor tools available, such as EMC ControlCenter® or Brocade’sFabric Manager, they are not sufficient to affirm the SAN’s cleanliness. Additional tools arerequired to ease the administrator’s burden and increase his/her efficiency. With these tools,the answer to questions such as, “to which array(s) does this server have access,” “how manyunused aliases are there in the active zoning,” or “how much disk has been assigned to thiscluster,” can easily be answered. Often, these tools are Shell or Perl scripts. However, thesescripts are dependent on the clarity of the administrative rules.

Accurate documentation and status reports can only be built on a foundation of ground rules,conventions, best practices and procedures. For example, naming conventions should bedefined. The definition of best practices, based on vendor recommendations or in-houserequirements, should be agreed upon and documented. Whenever the SAN physicallychanges, the fabric spreadsheet must be updated. This is one example of a procedure thatensures a maintainable and manageable SAN.

When these rules are well-defined, writing administrative tools is greatly simplified. The tools willbe more effective because they will automate tasks and check the consistency of SAN components.Tools can maintain a server-based copy of the current zone configuration, for example. This in turncan verify that zoning conforms to the naming convention. It can also provide the WWNs (worldwide names) of a server, required when masking LUNs from an EMC Symmetrix® system.

Other scripts could automatically generate LUN (logical unit number) maps using navicli andsymcli commands, to show LUN capacities, owners, RAID (Redundant Array of IndependentDisks) information, as well as a cumulative disk usage per server or cluster, array front-portusage, and total used and free capacities per array or RAID group. In turn, the LUN maps canbe cross-referenced with the zoning information to ensure servers are not zoned to arrays onwhich they have no provisioned space.

This paper focuses on defining logical and meaningful conventions, documenting best practices,and developing procedures for SAN administration. A serious and active approach to adminis-tration and automation makes it far easier to control the SAN and optimize workload execution.Additionally, it provides you with the opportunity to keep your manager’s confidence by reducingthe potential for problems.



Real-Life Challenges in Today’s Storage World

Kiran Ghag, Senior Systems AdministratorHSBC

This paper is targeted primarily at storage architects and administrators as it presents real-life challenges faced while implementing SAN solutions.

Storage implementations are growing faster than ever. The information world is booming andthe technology is evolving to keep pace. Users view SAN as a panacea that is going to solveall their data storage, performance, and protection requirements. The architects and admin-istrators have to work diligently to satisfy end users’ needs and provide a design that willaddress their requirements.

SAN works well to meet these needs, but many practical hurdles prevent businesses fromachieving optimal results. Every organization faces these challenges on a different scale.Numerous best practices, “How To” documents, and user manuals present technical prob-lems and ways to solve them. But there are few papers that talk about worst practices.

This paper goes beyond the technical to identify the human error and root causes behindmany SAN issues. It adopts a vendor-neutral approach; hence it is applicable to a larger num-ber of setups.

With this paper, you will be able to identify the risks/issues in your existing or planned setup.This will prepare you to mitigate them and optimize performance.

How to Deploy a Celerra iSCSI Solution

John Shubeck, Technical Business ConsultantEMC Corporation

iSCSI (Internet Small Computer Storage Interface) is a transport protocol for sending SCSIpackets over TCP/IP networks. iSCSI initiators (clients) and iSCSI targets (servers) are the keycomponents in an iSCSI architecture. These iSCSI initiators and targets are the devices whichtransfer SCSI information over an IP network. The term “IP SAN” has often been used todescribe an iSCSI network.

In addition to traditional file sharing protocols Common Internet File System (CIFS) and NetworkFile System (NFS), the EMC Celerra® Network Server supports the iSCSI protocol for hostaccess. Although Celerra’s capability has existed for over three years, many customers haveyet to explore iSCSI as an alternative to traditional SAN or NAS connectivity.

In some cases, lack of awareness has prevented customers from exploring iSCSI capabilityand its potential value. As a result, a viable alternative to traditional host connectivity whichcould result in cost savings cannot be achieved. I would argue that education is a keyapproach that can raise awareness and, in turn, lead to evaluation and adoption of iSCSI as ahost connectivity solution for application and database servers.

This article establishes a baseline of understanding about iSCSI and discusses the key ben-efits and indicators when considering an iSCSI storage solution. In addition, the articledescribes a step-by-step process for implementing a Celerra iSCSI design which will includedetails about how to set up both the Celerra target and the Windows iSCSI initiator hosts. Weemphasize performance and high availability considerations, specifically Celerra trunking andfailsafe networking as well as Microsoft Multipathing Support for iSCSI (MPIO). Finally, a specificfield experience will be used as a case study to illustrate planning considerations and decisionpoints throughout the implementation project.



Setting Up an Invista Environment

Adam Jones, Senior Technology ConsultantEMC Corporation

Since the EMC Invista® Instance configuration is new to most individuals, I wanted to share acomplete end-to-end guide to outline the procedures for setting up an Invista environmentfrom the ground up utilizing Brocade 7420 multi-protocol routers. This paper details all ofthe steps necessary to cable and configure the CPCs, IP switches, and Brocade 7420 multi-protocol routers (DPCs) to integrate into a Symmetrix and CLARiiON storage environment.

In addition to covering the standard configuration tasks, I have included the procedures tobuild out the CPCs from scratch with the Invista .mif file and also how to recover the Brocade7420 multi-protocol routers from the recovery kernel.

The equipment used for this procedure:

• Two Invista CPCs running Code Level 1.0—SP2

• Two Allied Telesyn AT-8948 IP Switches running Code Level 2.7.3-00

• Two Brocade 7420 Multi-Protocol Routers running Code Level 7.4.1 and SAS Code Level 2.1.3h

• One Symmetrix DMX800 running Microcode Release 5671.54.59

• One CLARiiON CX 600 running FLARE® Code Level 2.19.600.5.007

• One Windows 2003 Server (SP1) with two QLogic QLA2342 HBAsrunning Code Level 9.1.4.15 (Driver), 1.52 (BIOS), and 3.03.21 (Firmware)

Deploying an SQL 2005 Cluster in a Virtualized SANEnvironment

Bartley Corbin, Implementation SpecialistEMC Corporation

This article was inspired by a deployment team from the EMC Federal West, Solutions EngineeringGroup. We rewrote two of Microsoft’s Knowledge Base articles and are doing something withVMware® that no one thought could be done. During the course of this project, we disprovedseveral myths about VMware environments utilizing clustering in SANs.

This solution is not supported by any of the major vendors including EMC, VMware, orMicrosoft. Although VMware has documentation on segments of the process, they explicitlystate that certain things will not work. This article is intended to remove the guesswork.

Although we are beginning to see some white papers, it is simply too new for any of the vendorsto announce that they are willing to support this. For instance, EMC PowerPath® cannot beused in a VMware host, so how do you control failover paths?

This article contributes a single repository for anyone wanting to deploy an SQL 2005 clusterin a virtualized SAN environment.


Backing Up a Large Oracle Database with EMC NetWorkerand EMC Business Continuity Solutions

Maciej Mianowski, Regional Software SpecialistEMC Corporation

There are many articles describing the Oracle database backup, but none clearly describe thebackup of a large database. EMC provides many solutions which could be used to fill this gap.

The most common definition of a “very large database” (VLDB) is a database that occupies morethan one terabyte or contains several billion rows. Typically, these are decision-support systemsor data warehouses. Recently, transaction processing applications serving large numbers ofusers also fit into this definition.

The storage architect’s challenge is to design a backup solution that achieves the following:

• The backup operation should have no impact on the production process.

• The backup window should not be exceeded and the backup solution should be scalable.

• The backup solution should be resistant to any type of failure, including whole system failure.

• The recovery of the Oracle database should be fast and provide recovery at any point in time.

• The backup solution should satisfy all incomplete recovery scenarios supported by Oracle.

• The majority of the backup/restore operations should be automated and provide user-friendlyadministration and reporting tools.

• The solution should be fully supported by Oracle and EMC.

This article provides a guideline on how to use EMC NetWorker® and EMC business continuitysolutions such as EMC TimeFinder® or Open Replicator and describes how they support theabove mentioned principles.

First, the Oracle database backup strategies are discussed and applied to the large databasebackup. Some misconceptions about the Oracle hot-backup mode will be presented.

Then, the paper describes EMC’s business continuity solutions to illustrate how this technologyinteracts with the Oracle backup/recovery mechanisms, e.g., how EMC consistency technologymay be used in Oracle database environments. EMC TimeFinder/Mirror/Clone/Snap andremote EMC SRDF® and OpenReplicator solutions are introduced and compared.

We discuss EMC NetWorker software including the EMC NetWorker Module for Oracle andEMC PowerSnap™ Module and their integration with the Oracle database backup mechanisms.The differences between the conventional and proxy Oracle backup are outlined.


Finally, a few examples of the advantages and limitations of backup/recovery solutions aredescribed. The EMC NetWorker PowerSnap image backup is included.

Many of the topics discussed in this article require comprehensive coverage, so additionalreading will be recommended.


Designing and Implementing a Backup, Recovery, andArchiving Solution (BURA) in a Pharmaceutical Company

Carmen Marcano, Solutions ArchitectEMC Corporation

This paper explores the processes and practices used to design and implement a backup,recovery, and archiving solution in a pharmaceutical company. The customer’s primary businessobjective was to optimize the overall information management practices that were based onan obsolete storage infrastructure, inefficient data safeguard practices, and ad hoc informationmanagement processes.

The solution involved a whole new architecture of EMC hardware and software integratedcomponents. The customer adopted an information lifecycle management (ILM) model toachieve cost-effective storage, data resilience, and more-effective information management.

We divided the project into seven major phases to accommodate customer needs and existingprocesses. Due to the nature of the pharmaceutical business, proper care was taken to fulfillthe regulated systems’ validation processes. During each phase, we were challenged to over-come the inherent difficulties in a regulated environment.

Each phase began with a design based on customer needs. Since we had to minimize downtimeduring the transition, we focused on the migration strategy from the old to the new storageinfrastructure, with data integrity and compliance always in mind.

The architectural components were based on several infrastructure building blocks. Theyincluded CAS and SAN storage technologies, information availability, and storage managementcomponents such as EMC Legato® software, and archiving, backup, restore, and replication.All were seamlessly integrated in a resilient BURA architecture.

The optimized platforms were ERP based on SAP technology, and Microsoft File Server technology.The messaging platform was based on IBM Lotus Domino technology and the ChromatographyData System was also based on Microsoft technology.

Our efforts optimized customer backup, restore, and archiving processes. Data remained avail-able, and we collaboratively achieved the IT objective to eliminate backup windows, reallocatedata, and integrate information management. The full article details our experience and whatwe learned.


NetWorker Best Practices—Designing for Performance

Matt Steinberg, Senior Solutions ArchitectCambridge Computer Services Inc.

This paper explores three distinct areas of NetWorker performance. The first section addresseshow to define the business and technical issues in a NetWorker backup environment, includinga discussion of recovery-point objectives (RPOs) and recovery-time objectives (RTOs).

As the amount of data continues to increase, we must meet backup objectives within prescribedbackup windows. RPO and RTO are important measurement criteria to align performance withbusiness objectives. They support goal-setting, identifying needs, implementing solutions,and reconciling those solutions to the available budget.

The second section will identify three bottlenecks in NetWorker backup environments:

• host, or client side

• I/O of the NetWorker server

• tape drive

The third section reviews strategies to eliminate bottlenecks using NetWorker tools and softwareincluding NetWorker Storage Node, Dedicated Storage Node, SnapImage, and PowerSnapsoftware modules.

This paper also addresses the type and number of tape drives, and utilizing backup-to-disk.Non-NetWorker tools, like EMC’s RecoverPoint and RepliStor® software for continuous dataprotection are included in the discussion.

The final section presents findings and conclusions.


Integrating the EMC Disk Library with Veritas Netbackup

Adam Jones, Senior Technology ConsultantEMC Corporation

This paper outlines the procedures for integrating the EMC Disk Library platforms with VeritasNetbackup 5.0.

The equipment used in this procedure:

• One MDS 9509 running Fabric OS 3.0 (2a)

• One DL310 running Code Release 2.2 and 1 Windows 2003 Server (SP 1) with two QLogic QLA2342 HBAs running Code Release 9.1.2.16 (Driver), 1.47 (BIOS), and 3.0.3.19(Firmware)

The EMC Disk Library is emulating one ADIC i2000 tape library with five Quantum Super DLT1tape drives.


EMC NetWorker: Wearing Belts and Suspenders

Suggestions for Improving Security, Performance, and Life-Span usingEMC NetWorker

Tor Eikanger, Senior Systems EngineerEmentor Norge AS

The article presents a scenario where built-in functions and customized scripts enhance thefunctionality of EMC NetWorker.

It presents issues including:

• Using cloning and scripts to maintain the clones. By doing so, you obtain enhanced stagingfunctionality. All save sets go to an adv_file device and are automatically cloned to tape.When the adv_file device is full, a script deletes the oldest instances on disk, keeping theclones on tape. Fresh data is kept in two locations; and older data only on tape.

• Using groups and cloning pools for maintaining differentiated retention time. By implementingthis practice, you can keep daily backups for one month, weekly backups for the next sixmonths, and monthly backups for a decade. This effectively utilizes your storage and reflectsmost users’ need for restores.

• Customizing schedules using nsradmin to achieve functionality beyond what is possible inthe NetWorker Administrator GUI (graphical user interface).

• Using WORM (write once, read many) media to comply with regulations.


Utilizing EMC Replication Technologies to Help Save TexasElectricity Consumers Billions of Dollars

Michael Solari, Manager, Storage EngineerElectric Reliability Council of Texas

The mission of the Electric Reliability Council of Texas (ERCOT) is to direct and ensure reliableand cost-effective operation of the electric grid and to enable fair and efficient market-drivensolutions to meet customers’ growing electric service needs.

In 1999, the 76th Texas Legislature passed Senate Bill 7 requiring the creation of a competitiveretail electricity market, and ERCOT was named as “central registration agent” for retail choice.

Since 1999, the total retail electricity market in the ERCOT region has grown from an estimated$17 billion annually to an estimated $23.5 billion in 2007. Total generation capacity has grownto approximately 70,000 megawatts to meet peak demands that have grown from 54,980 MWin 1999 to estimated peak requirements of 63,000MW in 2007. The ERCOT region has alsoadded 3,000 MW of renewable energy-generation capacity, while retiring older, more-polluting,less-efficient generators.

The ERCOT region has seen much greater expansion of transmission infrastructure in recentyears than any other North American region and has been rated as the #1 competitive electricmarket in North America.

In 2000, EMC was chosen to meet the retail deregulation requirements. The solutions haveexpanded from an initial EMC Symmetrix 8430 in 2000 with 1 TB of capacity, to multiple DMX-3arrays with 600 TB of usable space in 2007. ERCOT utilizes Symmetrix Remote Data Facility fordisaster recovery replication and migrations; TimeFinder/Mirror, TimeFinder/Clone, andTimeFinder/Snap for effective replication of critical development projects, fast backup andrecovery solutions, and recently, tiering solutions to meet information lifecycle requirements,that, by protocol, mandate ERCOT to retain data for seven years.

In 2006, ERCOT was chartered to implement systems to support a more competitive wholesaleelectricity market; the goal is to save consumers even more money. These critical systemsmust be operational by the end of 2008. EMC replication technologies are critical to the successof the project, which by some estimates could grow to five times the current size of productionin terms of capacity, and 70 times the current size of processing requirements. All of this mustbe achieved without hiring more ERCOT staff, and in the face of data center power, space, andcooling constraints.

This article shares the ERCOT solution. It reviews how to manage storage growth in uncertaintimes to meet critical project timelines with very limited resources.


Implementing Replication Manager/SE for Exchange

Carl Granfelt, Storage Implementation ConsultantPosetiv Ltd.

This article describes best practices associated with implementing Replication Manager/SEfor Exchange.

It reviews and details the following topics:

• Exchange best practices

• CLARiiON LUN design best practices for Exchange

• RM/SE prerequisite software

• Configuration Checker

This best-practice document assembles otherwise dispersed industry best practices forimplementing RM/SE specifically in Exchange environments.


Symmetrix Local Replication from A–Z: All the Choices and Which to Choose

Donald Fried-Tanzer, Education Services ConsultantEMC Corporation

EMC offers many different ways to replicate data on a Symmetrix array. Few are aware of allthe options and even fewer know how to select the best option for a particular situation. Inthe case of a Symmetrix storage array, the replication unit discussed in this paper is the SymmetrixLogical Volume (LV) which appears as a hard disk to the host.

EMC also offers additional products for remote replication, file or directory-level replication,and automating and managing replication creation and restoration. These additional productsare discussed when their use in combination with local replication may either limit or affectthe choice of the best local replication method.

The key EMC local replication methods discussed in this paper include the TimeFinder family:

• TimeFinder/Mirror

• TimeFinder/Clone

• TimeFinder/Snap

Symmetrix back-end replication (RAID 1, RAID 5, and RAID 6) is discussed to provide back-ground for the unique capabilities of TimeFinder/Mirror and also the impact on LV mirrorpositions which may limit local replication options.

EMC Open Migrator is presented as an example of a host migration product with different per-formance impacts and features. In particular, it is critical to understand how TimeFinder/Mirrorand TimeFinder/Clone differ and what circumstances might prompt you to add on the TimeFinder/Mirror feature above the base TimeFinder/Clone product.

LV replication serves many functions: data protection, backup, restore, secondary applications,migration, and upgrade testing. Both the primary and secondary use of the data impact thedecision about which type of replication to deploy.

Among the factors that may affect your decision:

• number of copies

• ability to make copies of copies

• backup functionality

• restore functionality


• how soon the copy is available

• performance impact of the copy on both the primary and secondary use

This paper includes information on all of the latest features available with EMC Enginuity™

level 5772 and Solutions Enabler 6.4.

We begin by defining basic concepts, such as mirror and copy. Then, we move onto implementationalternatives for achieving the mirror or copy with particular attention to the performance effects andfeature availability. We discuss the specific implementation and features of currently available EMCSymmetrix local replication methods. Then, we explore how we can achieve customer applicationneeds with different local replication solutions. Finally, the paper concludes with recommendationsabout choosing the best local replication solution to meet any particular situation.


Mainframe SRDF/A and MSC Best Practices

Michael Smialek, Solutions ArchitectEMC Corporation

Implementing SRDF/A and Multi-Session Consistency (MSC) in a mainframe environment is abalancing act between key resources such as cache, disk drives, Redundant Array of IndependentDisks (RAID) protection schemes, and network bandwidth. Properly configuring these resourcescan guarantee a smooth SRDF/A implementation.

This best-practices document provides specific recommendations for configuring the Symmetrixhardware, SRDF/A and MSC software, and network equipment. Storage administrators willlearn to build a solid production and disaster recovery environment using the approaches tooperational and recovery procedures in this article.


Backup-to-Disk for Mainframe using the Mainframe Disk Library

Doug Morris, Senior Technical ConsultantEMC Corporation

EMC’s mainframe Disk Library (MDL) is an emulation gateway providing either ESCON (EnterpriseSystems) or FICON (Fibre) connectivity to the mainframe host with a shareable, highly available,high-performing storage backstore to contain the mainframe tape data. The MDL’s biggestadvantage is that it allows organizations to eliminate tape in their mainframe environments.

Many mainframe environments suffer from:

• aging, unsupported tape infrastructure

• immense floorspace requirements

• high tape-failure rates

• lack of available tape drives during peak backups

• tape handling by employees that can lead to loss of the physical tape containing importantfinancial data

The MDL corrects these problems by emulating IBM tape drives. From a mainframe perspective,the MDL looks, acts, and feels like a “real” tape drive. Only a handful of floor tiles arerequired to deploy it, greatly reducing the footprint. There are no single points of failure(SPOFs). The base configuration comes with 512 virtual tape drives. So, there’s no waiting forresources. Best of all, replication is built in and easily configured, thus requiring no tapehandling by employees.

This article discusses what the MDL is, what questions an organization needs to ask in order tosize it for both throughput and capacity, and how to migrate to the device once it is deployed.

Numerous MDL deployments, large and small, have been made. The convergence of 500 GB diskdrives and mainframe tape emulation has made backup to disk for the mainframe a reality.


Stars of EMC

David Pena, Technology ConsultantEMC Corporation

My paper introduces two “star” configurations that we are offering a stock exchange customerin Madrid, Spain. It is particularly noteworthy since there is no similar solution offered in Spain.

The first one is an SRDF/Star configuration for mainframe and open systems environmentswith AutoSwap™ for Mainframe (general availability in February) and AutoStart™ for OpenSystems. In the mainframe environment, this customer has DB2 as a database solution andOracle/SQL in the open systems environment. They are very interested in having three sitesfor disaster recovery in three different areas inside Spain.

The second is a star configuration for EMC Centera®. This customer is also very interested inpurchasing Documentum® with EMC Centera, and we are offering three systems for three different sites in a unique “star” configuration similar to SRDF/Star and Symmetrix. Documentumwill be used to store, manage, and organize business-critical information.

With these two solutions, we are offering two NS40G replicated with SRDF/S and six Ciscodirectors 9506 (two in each site) for SAN connectivity, SAN Extension, IP replication, and FC/IProuting. We are also offering to integrate EmailXtender® with EMC Centera and Documentum.

Both “star” configurations, Cisco directors and NAS, will be managed with EMC ControlCenterproviding one single point of control.

This project supports the “ONE EMC” initiative, and we are happy to offer it as a valuable bestpractice.


An International Mainframe Consolidation Project: Strategy and Technology

Michael Zimmermann, Account Technology ConsultantEMC Corporation

Richard Herbst, Technical Business ConsultantEMC Corporation

One of the largest outsourcing customers in Germany was planning an ambitious project toconsolidate all of their existing mainframes and storage into one central location. This was asignificant opportunity for EMC to demonstrate our service value.

The customer is an international technology services company with annual revenues of morethan EUR 5.4 billion; employing more than 50,000 people in 40 countries. This was a hugeopportunity that resulted in a ‘win’ for EMC.

This paper describes the processes that we used to achieve this client’s requirements. Beginning with the analysis of the existing systems landscape, we generated performancereports from each of the company’s systems. Using project management techniques, we collab-oratively identified milestones that were particularly useful since the migration includedeight steps and each step included at least two tests to ensure migration security.

The paper details the processes we used to achieve:

• Tape migration

• Data migration

• Migration of standard volumes

• Migration of R1 volumes

• Migration of R2 volumes

• Migration of BCV volumes

• Data migration tests using SRDF

This paper illustrates how collaboration and partnership with a customer can yield excellentresults.


StorageScope Validates Storage Area Network beforeMigration to New SAN

Barry Nelson, Solutions ArchitectEMC Corporation

A leading health insurance provider planned a SAN technology refresh that affected 80 hosts,12 storage arrays, and 10 switches in two data centers. The plan was ambitious; there wereover a hundred systems undergoing change on the same day. The business ownersdemanded minimal application downtime. This window was a few hours for some hosts and16 hours for other less-critical hosts.

Months of planning were required to minimize the risk that a host would move to the new SANand miss just one volume that would prevent it from returning to service. Nevertheless, theproject team was concerned that the change control process could validate the design, butthere was no assurance that there would be zero implementation errors.

There were over 12,000 volumes in the plan. If the execution followed the design to an accuracyof 99.9 percent (an ambitious goal), there would be 12 volumes missing in the new SAN. Inthe worst case, these 12 volumes would mean 12 hosts would not be available when the customerneeded them.

There were also over 800 zones that needed to be checked. The team decided to use softwareto validate the implementation against the requirements since it was unreasonable to expectan individual to find an error in 12,000 records and 800 zones.

EMC ControlCenter StorageScope™ is well-suited to address this problem since its repositorycontains information on what is actually implemented. Prior to the migration, we connectedhosts with ControlCenter agents to the new SAN to collect all the configuration informationabout the storage arrays and switches. Then, using custom reports on the StorageScopetables, we compared the existing host device allocation to the new SAN device allocation.

As expected we discovered missing volumes, masking errors, mapping errors, and errors inzones. It was relatively easy to correct these errors before the migration event. Had these errorsoccurred during migration, they could have damaged our relationship with the customer.

The migration was a success because the team did not lose time fixing SAN execution errors.Change control examines the design and plan, but has not traditionally reviewed the imple-mentation. When it is possible to perform implementation steps in advance of a data migration,it is prudent to verify those activities as well.

This paper shares our experience.


Global Storage Resource Management

Rich Ayala, VP Senior ArchitectA Leading Financial Institution

As the lead technical architect designing and implementing the world’s largest storage resourcemanagement (SRM) system for a large financial institution, I have a unique opportunity to reflecton the experience.

During this project, we made many decisions based on the storage technology base, size of theorganization, existing tools, past experiences with storage resource management (SRM), corpo-rate storage priorities, as well as vendors’ tools. With 15 PB sitting on 450 arrays, served to over8,000 servers, connected to over 50,000 switch ports, residing in over 60 data centers world-wide, we believe that this SRM implementation is the largest to date in terms of total storage andserver assets discovered, size, and distributed nature of the environment.

Some of the bank’s internally developed tools were mature in areas such as storage requestand reservation capability. However, no one tool could satisfy the immediate need to managea global storage infrastructure that is growing 60 percent annually; and to put that utilizationinformation into the hands of the user/customer, the bank’s lines of business.

The overall goal of the global SRM project (GSRM) was to provide one approach to collect anddistribute storage capacity, utilization, and configuration information from several perspectives,including the array, switch, server, database; and to provide roll-up summaries as well as drill-down capability by geographic location, owning customer organization, and storage tier.

This article discusses the following:

• GSRM (global storage resource management) solution requirements

• How the solution enables a strategy for storage/data center consolidation and applicationre-tiering

• Past and current toolsets and how they applied or did not apply to the solution

• Toolsets and technical architecture of this developed solution (EMC and third-party products)

• EMC ControlCenter as the foundation and source for our global SRM data

• The combination and compilation of EMC ControlCenter data to provide a single reportrepository for all global storage assets

• How one common GSRM report repository enables end users to meet corporate storagestandards

• The specific metrics used to measure customer compliance to standard guidelines


• How the GSRM deployment yielded ancillary benefits of standardized performance reportingand provisioning using EMC ControlCenter

• The challenges of deploying and supporting a global SRM solution


Taming the Data Tiger

John Bowling, Data ArchitectBusata Systems

IntroductionStorage management has become more than inserting monolithic subsystems and carving outlogical unit numbers (LUNs) largely due to the onslaught of data storage requirements and theaccompanying resource burden placed upon many organizations. The practice of storage man-agement has evolved into an art form.

While working for a fairly large insurance company, I’ve experienced many of these challenges.Due to regulatory and internal mandates, we have witnessed triple-digit growth during the pastthree years. We have grown from a couple of terabytes to a couple-hundred terabytes in veryshort order—with no relief in sight.

In order to absorb the increasing demands placed upon our data systems, we took a freshand systematic approach to managing the ever-increasing data storage requirements.

This is how EMC helped us:

Subsystem InfrastructureWe implemented a more flexible infrastructure that sustains exponential growth and performance.In the past, we procured just enough to handle our immediate demands. This led to wasted time,money, and effort implementing smaller systems that didn’t necessarily integrate well with oneanother.

To combat this, we implemented a Symmetrix DMX-3 subsystem which we are confident willmeet our long-term strategic storage needs. This system easily scales as our data requirementsincrease. In addition, the DMX-3 provides the ability to tier and consolidate many of our agingsubsystems within a single box. It also provides enhanced optimization, notification, and alertingwith enterprise-class reliability.

Fabric InfrastructureIn order to handle the additional connections to our storage systems, we implemented a dualcore-edge fabric utilizing McDATA i10K directors and McDATA departmental switches. Thisapproach provides enterprise-class reliability along with scalability ensuring no single pointsof failure within the SAN fabric.

Critical systems are dual-attached and remain online in the event of a host bus adapter (HBA),cable, switch, fabric port, or storage port failure(s).


Backup InfrastructureTaming the storage infrastructure is only part of the solution. Many organizations face challengesrelated to backup and recovery due to additional data capacities.

In order to deal with this issue, we chose to implement an EMC Disk Library (CDL) in a disk-disk-tape backup architecture.

With CDL replication, we eliminated the majority (96 percent) of our tape requirements whileenhancing backup reliability and total throughput.

VirtualizationServer virtualization utilizing VMware reduced infrastructure-related costs while enhancingdisaster recovery (DR) capabilities.

Information Lifecycle Management (ILM)A key component to our approach was to reduce the costs associated with explosive growthon our enterprise subsystems. ILM alleviates this issue by archiving static and underutilizede-mail and unstructured files to lower-cost storage platforms.

We chose the EMC Centera product for this purpose because it was easy to manage and it easilyscales in the hundreds of terabytes. Due to its compliance options, EMC Centera also meetsHIPAA, Sarbanes Oxley, as well as other governmental and internal mandates.

The full article presents lessons learned and best practices implemented to help us tame thetiger without getting bitten.


Automation of Customized and Localized Reporting

SungWook Hyung, Senior Technology ConsultantEMC Corporation

This article focuses on capacity management. Each customer has unique requirements. Someconsider storage management part of a larger system without providing a separate storagemanagement area, or think of storage as a black-box. In either case, we need to provide customerswith storage management guidance and education.

EMC ControlCenter StorageScope is playing a major role in automating capacity manage-ment. The Basic Customize Feature with a default requirement column, or the Custom FieldFeature with a defining and reporting column, can generate a customer’s Capacity Report. Butcustomers want more than these features.

Our customer wanted the storage management report to show which host is consuming howmuch of the volume, and how the file system or the database is being utilized. And, theywanted all of this in one view. They wanted an end-to-end capacity report, including configurationinformation, beyond separate storage, host, database, or SAN switch volume information. And,they wanted it in Korean.

This required a different method, the StorageScope Customer Report for Korea. Officiallycalled Korea Customized EMC ControlCenter StorageScope Report (or Korea Customized STS),it started by considering the customer’s needs.

Using StorageScope, each agent collects data in a repository in real time and saves it in XMLformat. This was a good approach to resolve the double-byte issue as well as customizing thereport form that Korean customers wanted.

Term definition and calculation are prerequisites for executing this program. Reports aremeaningful only when they are created in a user’s language and use the customer’s data andcalculations. Most of the pre-work consisted of converting the terms and structure of differentproducts—Symmetrix, CLARi (CLARiiON for Korea), Celerra, EMC Centera, or Connectrix—to fitthe customer.

I wouldn’t have been interested in this type of work, but the EMC Proven Professional ProgramSpecialist and Expert courses certainly have helped me develop my expertise. Customers withlarge-scale storage infrastructures are more satisfied with capacity management in Control-Center and provided EMC with more than 10 references regarding the best practice of effectivemanagement reports.

We were able to provide a real end-to-end service that automatically collects and processes dataand creates a report that can be used to manage the customer’s business. In conclusion, the local-ization of software is not about language, but is about resolving cultural differences. Unlikehardware that is mass produced, software is, after all, a reflection of a country and its culture.


Data Gathering and Analysis for Migration, Disaster Recovery,and Business Continuance in Symmetrix Environments: The Solution Architect’s Role

Michael Schwartz, Senior Solutions ArchitectEMC Corporation

There are many ways to gather the requisite data for planning and implementing migrationsand/or disaster recovery (DR). This article presents processes and methodologies that I havesuccessfully used to accelerate and improve data gathering and analysis.

This paper describes the steps to install Solutions Enabler on your laptop and gather the followinginformation from the customer:

Common• Symmaskdb list database

• Copy of SYMAPI_DB.BIN file

• Get DG/CG from customer

• Symmetrix BIN file(s)

• GRABs

• Switch reports

DR/BC• RPO/RTO

• Intended bandwidth

• Connectivity topology

With this information, Solutions Enabler has the ability to create xml output of most commandsby simply adding a “-output xml” to the command. Xml structure allows for easy importing intoExcel, as well as simplified Perl scripting.

This paper fully explores this topic. By loading the customer’s symapi_db.bin file on your laptop,you will be able to execute many show, list, and query commands. This will ease the discovery ofdevice info, SRDF/TF relationships, device groups/composite groups, and more.

Once all of the details are captured in your Excel document, it is easy to sort/filter the currentinformation and to plan your migration/replication implementation.


Outline of analysis procedures included in the paper1. Know your team members

2. Gathering, aggregating, and qualifying data

3. Determining which data is pertinent for analysis

4. Analysis steps for migration planning

5. Analysis steps for replication planning

6. Finalizing the design with the customer

7. Successful handoff to implementation personnel

8. Keys to success for customer test and acceptance

9. Project completion


Migrating Data from DMX1000 to DMX-3

Henry Zhang, Senior Infrastructure SpecialistEDS

This article introduces EDS Canada’s best practice on migrating data from EMC DMX1000arrays to EMC DMX-3 arrays using EMC Open Replicator. It reviews all stages of our successfulproject including migration planning, pre-implementation, implementation, and verification.

This project took approximately three months to complete and we migrated nearly 100 serversincluding Windows, Solaris, AIX, HP-UX base, as well as most popular cluster environmentslike Veritas Cluster, Sun Cluster, and Microsoft Cluster.

The article introduces an EDS-developed utility, symcli scripts, to enable faster migrations.


Migration of File Servers to NAS and Multi-Tiered Storage

Bryan Horton, Systems EngineerA Leading Healthcare Provider

The proper software running within a robust hardware infrastructure, coupled with enter-prise-class best practices, can produce a healthy, resilient, multi-tiered environment for datastorage. This article describes the journey of migrating Windows and UNIX file servers frommany servers using a single tier of storage to a NAS-based solution utilizing a multi-tieredenvironment.

The EMC hardware platforms included the Symmetrix, CLARiiON, Celerra, EMC Centera, EMCDisk Library, and EMC Connectrix®. We’ll review the associated EMC software including CelerraSnapSure™, EMC DiskXtender® for NAS, SnapView, and TimeFinder.

Starting with design considerations, and moving to current use and future plans, this articleexplores technology selections and the criteria on which they are based. We also discuss thetrials and errors we experienced on our journey to find the optimal solution.


ISL Security Monitoring within EMC MirrorView/SRDF

Thomas Mitrovits, Global Development Business Manager—Storage NetworkingADVA Optical Networking AG

In today’s environment, the security of data transmission is critical. Fibre intrusion and degra-dation monitoring is sometimes necessary to ensure that the lines between data centers aresecure and healthy. When a failure occurs, the data path should switch automatically to anothermore secure line. Many times, temporal changes in fibre performance are difficult to detect. Ifnot monitored in real time, data may be manipulated/stolen faster than you can react.

With the use of an ADVA FSP2000 with an Optical Line Monitoring module (OLM) and the inte-gration into MirrorView, SRDF via a Management Server, or EMC ControlCenter, we can preventthis problem.

This article reviews and discusses:

• Fibre intrusion monitoring

• Fibre degradation monitoring

• Fibre cut monitoring (optional—because MV/SRDF are aware of it)

It details the steps taken to implement a solution and describes additional components.


EMC Security Initiatives: A Market Differentiator

Jenny Beazley, Sr. Project ManagerEMC Corporation

A recent RSA® survey revealed that EMC customers fear auditors more than hackers. In thewake of Enron, the Sarbanes-Oxley law imposes severe penalties on publicly traded companiesfor exposure or tainting of financial data. There are a growing number of regulations and standardscompanies must adhere to, including the California Senate Bill 1386, Gramm-Leach-Bliley Act,and the EU’s Directive 95/46/EC.

In 2005, EMC conducted a security assessment of its products and subsequently initiated projectsincluding two-factor or two-pass authentication to storage arrays and connectivity devices,removing static passwords from array management software, and creating audit trails.

With such a complex product range, changes cannot be expected overnight. However, thereare steps that all EMC employees can take to promote storage management security for EMCand its customers. It is our responsibility as EMC Proven Professionals to blaze the trail andencourage colleagues to follow best practices to ensure a more secure environment for bothEMC and our customers.

The full paper briefly describes EMC security initiatives and offers suggestions for securely managingstorage arrays. One suggestion is for customers to implement the ESRS Gateway for secure remoteaccess, securely erasing failed disk drives, and setting secure passwords and access control.

Initiatives• Symmetrix Service Credentials, secured by RSA

• Service Credentials for other storage arrays

• Data Erasure (both single-disk and rack-mounted units for Symmetrix, CLARiiON, andeventually EMC Centera)

• ESRS Gateway

• Alert Server

• Tools Server


Security Best Practices• Setting Secure Passwords

• Access Control

• Secure Transmission

• Confidential Information

Customer-Facing Security• Top-five storage array customer questions from the Customer Security Management Office


Challenges and Best Practices in the Deployment andManagement of IPTV Networks

Paul Brant, Senior Advisory Technology ConsultantEMC Corporation

Reliability and quality of service are the greatest challenges that Internet Protocol Television(IPTV) operators face as they deploy IPTV and other broadband services. These complex serv-ices must be extremely resilient. If consumers experience less than optimal service levels,both customers and providers are negatively impacted.

It is challenging to integrate video-over-IP equipment into existing metro and access net-works. So, how can service providers be sure that those networks are capable of deliveringquality service as they grow from thousands to millions of customers?

This paper reviews the video-stream and integrated triple-play/multicast video solutionsavailable and examines how they work. Video service delivery for example, places high band-width demands on its network and related applications as the provider integrates storage,delivery, and access to the consumer. There are enormous scalability requirements that caninclude thousands of servers with back-end storage in the petabyte range. This will challengeany deployed solution.

Networks rely on multiple layered protocols. Since the layers are independent, a problem ina lower protocol can be masked and/or spread to the other protocols. This type of lower-levelprotocol disruption can be easily hidden and hard to diagnose. A timely diagnosis and quickresolution are critical.

The Next-Generation Network Architecture (NGNA) is the cable industry’s umbrella “vision”for its network of the future—ultimately a move to IP. Parts of NGNA can be found in CableLabs specifications, including DOCSIS 3.0, PacketCable, OpenCable, and CableHome. Thistechnology also has scalability and quality of service issues.

The EMC Smarts® family of solutions, including support for IPTV, helps service providers createa high availability and high-performance environment. Smarts’ powerful modeling, cross-domain correlation, analysis plus a scalable and distributed architecture make EMC Smartscapable of supporting and managing large complex environments. This helps to isolate anyproblem with a high degree of accuracy.

This paper discusses the unique management challenges posed by next-generation networks(NGN) and how the EMC Smarts architecture is uniquely suited to address them.


Project Delivery Approach: Pre-work or Re-work?

Lalit Mohan, Senior Solutions ArchitectEMC Corporation

Project delivery engagements, whether large or small, require a quick progression from “initiation”to “close.” These undeniable pressures emanate from tight deadlines, cost pressures, shortopportunity windows, and many other factors.

Under such pressure, it is easy to ignore pre-work; the creation of the charter, scope, task lists,schedule, and the many supporting plans required for the delivery of the project.

Ignoring or minimizing pre-work almost always results in late discovery of critical requirements,unrestrained stakeholder influence, and use of unsuited deployment methods. Ultimately, itresults in extensive re-work leading to runaway costs.

This article reinforces the theory that pre-work and re-work are inversely related. Conductingthe appropriate amount of pre-work has the potential to reduce or even eliminate re-work.Conversely, paying less attention to the pre-work almost certainly increases the amount of re-work.

Helping stakeholders understand the linked relationship will help them to overcome theirresistance to spending time on pre-work and balance the pressure to bypass it. This wouldminimize the total cost of service delivery.


Business Information Management Reengineering (BIMR)

Eugene Demigillo, Technical Development ConsultantEMC Corporation

We have delivered various solutions (platforms and software) and services (consolidation,continuity, compliance, comprehensive BURA, content management, and classification) thatbenefit our customers. But there is another facet of our customers’ business that we need toaddress; we need to help them re-engineer their information management processes andprocedures.

It can take between six and nine months for customers to align their processes with our solutions.As they focus on that alignment, they tend to delay other projects with us.

Offering BIMR consulting to customers helps them to more quickly adapt their processes. Thismay be a bit outside our comfort zone, but as the leading provider of information managementand infrastructure solutions, it is essential for us to deliver this valuable service to customers.

This paper reviews the following topics:

• Understanding business process reengineering

• Understanding the value of information management/infrastructure

• Why the need for BIMR? (Who needs a BIMR?)

• Executing BIMR (a methodology)

• Rewards of a successful BIMR exercise


EMC Proven Professional Program

The EMC Proven Professional program is the leading, most comprehensive training and certi-fication program in the information and storage management industry.

Tracks/Roles• EMC Proven Professional Storage Technologist (EMCST)

• EMC Proven Professional Storage Administrator (EMCSA)

• EMC Proven Professional Technology Architect (EMCTA)

• EMC Proven Professional Implementation Engineer (EMCIE)

• EMC Proven Professional Customer Engineer (EMCCE)

• EMC Proven Professional Application Developer (EMCApD)

• EMC Proven Professional Product/Technology Specific

Specializations• Symmetrix Business Continuity

• CLARiiON Solutions

• Networked Storage—SAN

• Networked Storage—NAS

• Networked Storage—CAS

• Storage Management

• Backup and Recovery

• Mainframe

• Availability

• EmailXtender and EmailXaminer


EMC’s Proven Professional Framework

Our unique framework is a consistent, measurable means to build and maintain technicalknowledge and skills. Our “closed-loop” process allows participants to enjoy the full rangeof our offering—from practice tests to distribution of updated content in your specialty areaand, of course, to knowledge sharing.

Special thanks to all of our certified individuals who contributed to this publication.



EMC Corporation, Hopkinton, Massachusetts 01748-9103, 1-508-435-1000, In North America 1-866-464-7381

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 WARRANTIESOF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY 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, CLARiiON, Documentum, and where information lives are registered trademarks and EMC Proven is a trademark ofEMC Corporation. VMware is a registered trademark of VMware, Inc. All other trademarks used herein are the property of theirrespective owners. © Copyright 2007 EMC Corporation. All rights reserved. Published in the USA. 05/07 Handbook H2771.2

Documents

EMC Proven Professional Knowledge Sharingeducation.emc.com/main/common/documents/ks_articles/knowledg… · Thomas Mitrovits , Global Development ... sync, consistent fracture, resume