IBM Systems and Technology Group © 2008 IBM Corporation IBM System Storage Introduction This...

IBM Systems and Technology Group

© 2008 IBM Corporation

IBM System Storage Introduction

This document is for IBM and IBM Business Partner use only. It is not intended for customer distribution or use with customers.


© 2008 IBM Corporation2 Sales Conference

Agenda

Class Objectives

Administration

Introductions

Test Profile

Course Agenda

Primer – Storage basics



Class Objectives

Understand the IT and storage environment today

Define the solutions, the storage strategy and the unique value add of IBM storage to meet customer needs

Learn the product features and functions both hardware and software

Understand the key competition’s products and strategies.



Class Objectives

Identify IBM Systems Storage opportunities in the marketplace

Recognize key selling strategies in the storage marketplace

Learn IBM System Storage products, solutions, and strategies to prepare for the IBM Certification Test 960 Storage Sales Version 9.



Class Administration

Schedule

Materials

Facilities

Introductions

Roster

Evaluations



Student Introduction

Here’s what we like to know:

– Name

– Company

– Location

– What is your role?

– How much experience with IBM System Storage?



Detailed Objectives

Section 1 - Customer Business Needs Assessment (10%)

Determine the customer's business needs.

Identify the customer's business direction including future growth plans (i.e., new applications, new locations, new employees, etc.).

Identify the customer's business challenges as they relate to storage and the IBM on demand strategy, and describe how IBM System Storage solutions help customers achieve an on demand environment.

Identify customer pain points.

Understand customer environment (i.e. resource, budget, risk-exposure, organizational issues, ease of use, etc.).

Obtain strategic enterprise IT plan and storage requirements (e.g., identify links between customer's future growth plan, IT plans, and storage plans to insure a match) and work with the customer to develop a storage plan.

Determine the customer's hardware, software and service requirements.



Detailed Objectives

Section 2 - Sales Process, Tools, and Resources (19%)

Identify target markets and opportunities for IBM storage solutions.

Qualify opportunity (identify decision makers, identify competition, etc.).

Position the enterprise storage solution to meet the customer's storage needs.

Prepare sales proposals and presentations tailored to the customer's business requirements.

Coordinate appropriate presentation resources (e.g., specialists).

Prepare business justification (TCO/ROI).

Understand the value and leverage System Storage Executive Briefing Center, System Storage Interoperability Center, System Storage Solution Center or Business Partner Innovation Center (BPIC).

Identify contact resources to get information regarding .IBM’s Information Infrastructure strategy – Virtualization, Archive and retention, and Security

Locate and use appropriate sales tools, sales resources, and IBM contacts to create and design storage solutions that meet customer needs.



Detailed ObjectivesSection 3 - System Storage Portfolio (38%)

Describe the IBM System Storage strategy and build a storage strategy with the customer.

Describe the storage hierarchy as it relates to price, performance and business requirements and as it supports life cycle management and storage orchestration.

Describe the benefits and differentiating features of IBM disk solutions (e.g., DS family,,N series, Network Attached Storage, iSCSI, SATA, EXP Plus).

Describe the benefits and differentiating features of IBM tape solutions (e.g., Enterprise tape drives and libraries, Virtual Tape Server, LTO, WORM tape and encryption).

Describe the benefits and differentiating features of the IBM virtualization family (e.g., SAN Volume Controller and virtual tape).

Describe the benefits and differentiating features of IBM Storage Management Software (e.g., IBM Tivoli Storage Manager, IBM TotalStorage Productivity Center, DFSMS).

Describe the benefits and differentiating features of IBM's Archive and Retention solutions.

Describe the benefits and differentiating features of IBM storage networking components (e.g., gateways, switches, hubs, routers, directors).



Detailed ObjectivesSection 3 - System Storage Portfolio – continued (38%)

Describe the benefits and differentiating features of IBM managed storage services (e.g., migration, installation planning, assessment).

Describe the business benefits and how network topologies affect the storage environment (e.g., switched fabric, ATM).

Understand the differences in interface technology (e.g., SCSI, Fibre Channel (FC), SATA, ESCON, FICON, FCIP, iFCP, iSCSI, SAS).

Understand the implications of different IBM and non-IBM host hardware and operating system platforms for storage solutions.

Describe how RAID levels, dynamic sparing and cache affect performance and availability.

Understand the concept of storage virtualization).

Understand how tape automation reduces TCO – multipla platforn connectivity, high availability, scalability, etc

.



Detailed Objectives

Section 4 - Solution Design and Implementation (17%)

Identify how IBM System Storage solutions meet the following storage-related business needs: – Disaster Recovery - Risk Assessment – Disaster Recovery - Business Continuance – Disaster Recovery - Tiers – Disaster Recovery - High Availability; Geographically dispersed

systems – On Demand Solutions, including Archive and Retention – Data Sharing – Performance – Enterprise Storage Resource Management - Capacity Planning – Energy Efficiency



Detailed Objectives

Section 5 - Competition (16%)

Identify current primary competitors of the IBM System Storage portfolio.

Determine the competitor's value proposition, pricing, selling strategies and solution strengths/weaknesses.

Determine the competitive features and benefits of:

– Tape - Quantum, HP, Sun

– Archive and Data Retention - EMC

– Disk - EMC, HDS, Sun, HP

– Network Attached Storage - EMC, HP, Sun

– Storage Software – EMC, HP, Symantec, Veritas, CommVault

– Storage Virtualization - EMC, HP, Sun



Agenda Day 1

Introduction

Information Storage Sales and Strategy

IBM System Storage Product Overview

IBM Disk Storage - Entry and Midrange

IBM Disk Storage – Enterprise Systems



Agenda Day 2

IBM System Storage - N series

IBM Archive and Data Retention Solutions

IBM Tape Storage

IBM System Storage SAN Fabric

IBM System Storage - Software



Primer - Storage Basics

– Fibre Channel ?– Partitioning– SAN Fabric?– What is a SAN ?– What is NAS ?– SAN and NAS Differentiating Factors– What is SATA?– What is SCSI?– What is RAID?– Advance Copy Services?



What is Fibre Channel?

A serial data transfer architecture developed by a consortium of computer and mass storage device manufacturers and now being standardized by ANSI.

Serial computer bus intended for connecting high-speed storage devices to computers.

Standard connection type for storage area networks (SAN) in enterprise storage.

Fibre Channel signaling can run on both twisted-pair copper wire and fiber optic cables



Optical VS Copper

Copper Optical

10 Gbpseconomical

Cable lengths under 30-100m

Adapters generally UTPHSSDC; HSSDC2

Connectors; SFP Module

10 Gbps Maxexpensive

SMF longwave up to10km MMF shortwave up to 500m

LC Connectors; SFP Modules

Less/not susceptible to EMI Immune to electronic tapping

Lighter, thinnermore durable



Scales from GBs to TBs

Preloaded file system that provides heterogeneous file sharing

Windows (CIFS), UNIX (NFS), Web (HTTP), Novell, FTP, AppleTalk, and so forth

Installation software

Requires minimum IT skills to maintain / install

Management software

Manage and Setup from remote location

Diagnostic software

PFA, LPD, Alerts

Fault Tolerant Features

Dual, Redundant, Hot Swap Components

Data Protection Technology

Data Protection with RAID, and Backup to Disk and Tape

Storage appliance directly attached to IP networks:

Optimized for high performance

File Serving services using file system protocols

Independent of multipurpose servers

Heterogeneous environment independent of Server or Client File System platform

LAN

Novell

WindowsUnixMac Apple

Network Layer (TCP/IP)

File systemCIFS/NFS/HTTP

Diagnostics

Storage Array(SCSI or FC disks )

RAID Controller

Management Fibre Channel PCI Port

Network Layer (TCP/IP)

File systemCIFS/NFS/HTTP

Diagnostics

Storage Array(SCSI or FC disks )

RAID Controller

Management

SAN / FCStorage

RAID Controller

IntegratedNAS

GatewayNAS

What Is Network Attached Storage (NAS)?



Basic Hardware Terminology

Disks – “Spindles” – Each disk can handle a set number of I/Os per second

Fibre Channel Disks can spin at 10K RPM or 15K RPM

*Can get more IOPS from a 15K RPM disk

Serial ATA (SATA) Disks spin at 7.2K RPM

Disks available today: 18, 36, 73, 146 GB (15K RPM - FC)36, 73, 146, 300 GB (10K RPM - FC)400 GB (7200 RPM – SATA)

JBOD – “Just a Bunch Of Disks” – No availability or performance benefit

*Old/most simplistic way of provisioning storage (like desktop computers)

*All I/O to 1 disk at a time



Block I/O In the beginning, applications

read and write blocks of data

Block = unit of I/O for SCSI commands

Fixed Block Architecture

– All blocks same size

– Typically 512, 1024, 2048 or 4096 bytes in size

– Blocks numbered 0 to nnnn

Application

Block I/O

Block 0 Block 1 Block 2





Partitioning Partitioning creates one or more logical volumes from a block device

– Logical blocks mapped to physical blocks

Each logical volume is treated separately

– Block 0 to nnnn each

Application

Block I/O

Block 0

Block 2

Block 4

Block 0

Block 1

Block 2

Block 1

Block 3

Block 5

Block Device



RAID Vocabulary

LUN – Logical Unit Number – (z/OS calls it a Unit Control Block – UCB)Term for a logical disk – Storage that is actually seen by the connecting server

Array – Group of disks formatted according to a certain RAID level

RAID – “Redundant Array of Independent Disks” – Method of formatting disks to achieve a desired level of availability and/or performance

RAID 0 / JBOD stripe

Data stripedNo parity protectionImproves performance (more spindles)

RAID 10 = 3+3

M M M

Data striped and mirroredMirrored pair protectionBest performance Cost ineffective!

RAID 5 = 4+P

Data striped w/ parityCost effective Good performanceMost popular implementation

Parity

4+P

RAID 5

4+P

RAID 5

*Ex: 388 GB usable array

*Ex: 100 GB LUN*100 GB LUN/388 GB array



Direct-Attached Storage (DAS) to Storage Area Networks (SAN)

DS4800 DS4700

DS4200

System x System x System p

SAN

Needs storage



Server-to-Storage Data Flow

Storage

Host Bus Adapter (HBA)

Used to format data to FibreChannel for transmission via FC or FC-SAN

Gigabit Interface Converter (GBIC)

Server’s PCI busCPU, Cache, PCI Bus, etc.

Converts electrical signals to optical (FC)

8-port SAN SwitchContains 8 GBICsAny-to-any connectivity



Fibre Channel Cables

Optical cable*Allows high-speed, longer distance data transmission of SCSI traffic

*2 Gb version called SFP (small-form factor pluggable)

SAN



Storage Protocol’s In the past:

– SCSI IO protocol commands over SCSI media (www.T10.org)• Drawbacks to this design

– Distance– Scalability

In the now:– Encapsulate SCSI commands in a protocol’s frames / packets… But why? (www.T11.org)

• High speed / Longer Distances / Highly Scalable

1001101001101011101…..Data

Fibre Channel Protocol Packet

1001101001101011101…..DataSCSIProtocol

SCSII/O commands

FCPProtocol

SCSII/O commands

SCSI Protocol Packet

1001101001101011101…..Data

iSCSI Protocol Packet

IPProtocol

SCSII/O commands



IP SAN

File-based I/O Block-based I/O

File System

File System

Server

Storage

Server

Storage

App App

(NAS) (FCP, iSCSI)

Could be Fibre Channel SAN or IP SAN

FCP vs. NAS vs. iSCSI

FCP – Fibre Channel Protocol

NAS – Network Attached Storage (ex. CIFS (Windows), NFS (AIX)

iSCSI – Internet SCSI

Block-based I/OFile-based I/O

File System - A file system is the way in which an application organizes data and manages user access (Required for all applications)

“Think of it as “sifting for gold (data that your app understands).

You have to use the sifter at some point, it’s just a question of where….”



IP / WAN Network

Cluster / WAFL File System

NAS Gateway

FCP / SAN

File-level I/O

Block-level I/O

To the end-user client, it looks like File-level I/O!

Gateway will act kind of like a server using block-level access to external storage

System n Gateway



Methods to increase availability

Global Copy

Remote Volume Mirroring

Metro Mirror

Global Mirror

FlashCopyQuick point-in-time copy of a logical volume

Can serve as backup; Reduce downtime (only secs)

Can be offloaded to tape afterwards Copy

RAID arraysAvailability of arrays by allowing loss of physical disks

Ex. RAID-5

Redundant Components

HBAs, SANs, Paths, Controllers, Fans, Power Supplies, etc.

(With multipath/load balancing driver)



Data Backup and Restore – Copy Functions

Backup and Restore is the most simple and basic solution to protect and recover data from failure by creating another copy of data from the production system

Second copy of data allows to restore data to the time of the data backup

– FlashCopy

– VolumeCopy

– Remote Mirror and Copy

– FlexVol and FlexClone

– Snap* services

– Volume Shadow Copy Services (VSS)



FlashCopy overview

The FlashCopy function enables point-in-time, full volume copies of data, with the copies immediately available for read or write access

– Use the copy with standard backup tools

Benefits

– Point-in-time copy is immediately available for use for backups

– Minimal application downtime.

– Target volume is available for read and write processing so it can be used for testing or backup purposes

Background process copies data

Time to complete depends on:

– The amount of data being copied

– The number of background copy processes that are occurring



VolumeCopy

Firmware-based mechanism for replicating logical drive data within a storage subsystem– Designed as a system management tool

Creates a complete physical replication of one logical drive (source) to another (target)– within the same storage subsystem

– exact copy or clone of the primary logical drive

full point-in-time replication– allows for analysis, mining, and testing without

degradation of primary logical drive performance

Improves backup and restore operations– Faster

– Eliminates I/O contention on primary logical drive



Remote Mirror and Copy The remote Mirror and Copy feature is a hardware solution that enables the mirroring

of data from one site (the local site) and its associated volumes (source volumes) to a second storage unit at another site (the recovery or remote site) and its volumes (target volumes)

Remote mirror and copy differs from FlashCopy®

– Source and target volumes can be on the same storage server or on separate storage servers that are located at some distance from each other

– Remote mirror and copy does not capture the state of the source volume at some point in time, but rather reflects all changes that were made on the source volume to the target volume

Modes of operation available:

– IBM System Storage Metro Mirror

– IBM System Storage Global Copy

– IBM System Storage Global Mirror

Note: Remote mirror and copy was referred to as Peer-to-Peer Remote Copy (PPRC) in earlier documentation for the IBM® System Storage® Enterprise Storage Server®. Currently, the remote mirror and copy feature name is used generically for all methods of synchronous and asynchronous methods.



Metro Mirror

Synchronous mirror updates

All updates performed on the target volume before operation completion is indicated.

Metro Mirroring maximum distance of 300 km (186 mi)

May have performance problems

High Protection



Global Copy Maintains remote mirror of data asynchronously

– Sends a periodic, incremental copy of updated tracks to the target volume instead of a constant stream of updates

– "fuzzy" copy, no data consistency• original order of updates is not strictly maintained

– All updates performed on target volume, but at a later time.

Virtually unlimited distances between sites

– longer distance than is possible with Metro Mirror.

High-performance

Cost-effective

Data migration

Backup



Global Mirror

Provides a two-site extended distance remote copy option for disaster recovery

– Based on existing Global Copy and FlashCopy

– Data that the host writes to the storage unit at the local site is asynchronously shadowed to the storage unit at the remote site

– Consistent copy of the data is then automatically maintained on the storage unit at the remote site

Global Mirroring for distances greater that 300 km (186 mi)

Or minimal performance impact



Microsoft Volume Shadow Copy Service (VSS)

VSS is a storage management interface for Microsoft Windows Server 2003.– enables storage array to interact with 3rd applications that use the VSS API.– VSS is included in the Windows Server 2003 installation– Falls under Tier 4 which is similar to products supporting FlashCopy services.– Used for a number of purposes such as:

• Creating consistent backups of open files and applications• Creating shadow copies for shared folders

Volume Shadow Copy service for ESS (ESS API)– enables users to perform ESS FlashCopy Services through VSS.– non-proprietary storage management client application that supports and enables Copy Services such as

FlashCopy with support for VSS.

Volume Shadow Copy Service for DS8000/DS6000/DS4000– Provide an integration with Microsoft VSS to produce consistent shadow copies– Enables creation of full volume copies of data in a storage unit.

Clone (Full Copy/Split Mirror) or Copy-on-Write (Differential Copy)



Review questions

• What is NAS?• Network Addressable System for sending encrypted messages• Ability to attach storage systems to fiber channel networks• Network Attached Storage attached via IP network processing file I/O• Network Attached Storage attached via IP protocol processing block I/O records

• How can we attach disk storage devices?• FC, SAN Fabric, iSCSI, SCSI, and NAS.• FC, GX bus, iSCSI, and NAS• I/O towers, I/O drawers, RIO cables, and EXP enclosures• All the above

• What is SAN Fabric?• The backplane that attaches the disk enclosures• Switches, directors, and routers• The software disk management program that performs replication• Cabling to attach FC San devices

• What is iSCSI?• Attachment interface that is used for high speed block I/O applications• Wireless protocol for disk tranmission• Attachment interface that is used for low cost low speed applications using IP packets• Internet Storage Connectivity System Interconnect


© 2008 IBM Corporation

IBM System Storage – Additional Information



Measurement Units of Data in Storage

Bit = “A binary digit” of 0 or 1 – The basic communication protocol of all things electrical (includes servers/storage/etc i.e. yes / no ; on / off)

Byte = 8 bits

Kilobyte = 1000 bytes

Megabyte = 1,000,000 bytes

Gigabyte = 1,000,000,000 bytes

Terabyte = 1,000,000,000,000 bytes

Availability – Ability of a particular storage setup to remain active and optimal*Indicates ability to withstand external forces (i.e drive failure, SAN switch failure, etc)

Performance – Ability of a storage server to serve an application effectively

2 methods of measuring performance:1) Input/Outputs per second (IOPS) – Databases (small-block random I/Os)2) Throughput per second (MB/sec) – Streaming media (large-block sequential)

1 GB = 1,000 MB = 106

1 TB = 1,000 GB = 109

Petabyte = 1,000,000,000,000,000 bytes 1 PB = 1,000 TB = 1015



Write Anywhere File Layout (WAFL)

WAFL Performance– Improves RAID performance by writing to multiple blocks in the same stripe– Reduces seek time by writing blocks to locations that are near each other on disk– WAFL reduces head-contention when reading large files by placing sequential blocks in a file on

a single disk in the RAID array– Part of Data ONTAP™, the microkernel that ships with every IBM System Storage N series

storage system.

A Snapshot copy is a locally retained point-in-time image of data– Snapshot is a "frozen," read-only view of a WAFL volume that provides easy access to old

versions of files, directory hierarchies, and/or LUNs (logical unit numbers).



Common Internet File System (CIFS) Basics

CIFS Protocol

– Based on Microsoft’s Server Message Block (SMB), but optimized for the internet

– Developed in early 1980s for DOS, Windows and OS/2

CIFS Server

– “Stateful” – Server maintains history of clients connected

– Exported directories are known as “Shares”

CIFS Client

– Files are locked from other clients while in use

– Other clients can attempt access “Read-Only”



Redundant Array of Independent Disks (RAID)

RAID 1 – simple mirror



Server’s PCI Bus

Host Bus Adapter (HBA) Structure

Best Practices:

Generally recommend 2 per server for 2 reasons:Performance – Allows load balancingAvailability – Allows for failover if 1 HBA fails

Problem: However, because there are 2 paths now to every logical disk (maybe more in some cases), the host now sees the SAME logical disk TWICE!

Solution: Servers use a multipath driver (software). This eliminates the “multipath” issue and ensures the server only sees one logical disk. It provides path failover and in some cases load balancing

Host Bus Adapters

GBICs (SFPs)

Server



IBM Multipath Drivers

Subsystem Device Driver (SDD) - Driver-Supports DS6000, DS8000, SVC

Redundant Disk Array Controller (RDAC) – DS4000

Both are *Free-of-charge / *Downloadable off the IBM website

Other vendors – support additional multipath drivers check IBM’s interoperability matrices for support

Host server

Storage

SAN Fabric

LUN #1 (second view)LUN #1 (first view)

LUN

RDAC or SDD

Multiple paths One LUN!

Please note: Mainframe equivalent

Is within the OS as DPC,DPR,DLSE



The need for Zoning and LUN Masking

Creating an any-to-any Heterogeneous SAN creates new challenges with

Security

File system corruption

Best Practices and Design pSeries

Zoning

WorldWide Port Names (WWPNs)

Each HBA has a unique WWPN

Zone’s are a group of ports that create a path thru the SAN fabric

Server gets a dedicated path and LUN

Storage Partition / MaskingCreates virtual RAID controllers



Protocols, protocols, protocols….

Q: What is a protocol?

A: Rules determining the format and transmission of data

Analogy…..

If I were talking to you, the “protocol” would be our language. Since we both understand English, we can communicate.

Q: What is physical media?

A: The actual tangible physical device through which data is being transferred through

Analogy…..

If I were talking to you, the physical media would be speaking through the air (or could be an email or text message)

Q: What is a command?

A: A signal that initiates an operation.Analogy…..

If I were talking to you, the command would be the meaning of what I say. For instance, “Give me two carrots now!”



What is a File System?

A file system is the means by which data stored on some physical storage medium is organized, managed and made available for manipulation by applications on local and remote computer systems.

Typically, a hierarchy of directories and files

“root” directory

directory

file



A:\

C:\

D:\

/

b a

c

“root”Microsoft Windows:Installable File System (IFS)

• Assigns a drive letter to each file system

UNIX and Linux:Virtual File System (VFS)

• Attaches file systems at directory mount points

Can I have multiple File Systems?



How Applications Access FilesFile I/O consists of:

–Create File

–Open File

–Extend File

–Read bytes

–Write bytes

–Close File

–Delete File

“root” directory

directory

file



Local File Systems “Local” file systems maps files to block devices and provides control Info

– Owner

– Who can access

– Where it is located

– Date last referenced

Can map file system onto

– Internal Memory

– Physical Disk

– Logical Partition / Volume

– RAID device

– Floppy Diskette

– CDrom / DVD

File System Driver

Block Device

Application

File I/O

Block I/O

HBA



Journaled File Systems

Solution: Journaling!

– File systems keep a log of updates to metadata

– If system crashes, takes less time to reconstruct consistent metadata

– Data itself might be lost!

– Examples:

• Windows 2003 NTFS• AIX JFS and JFS2• Linux EXT3, ReiserFS• SGI XFS

Problem

– If system crashes or is stopped unexpectedly, metadata could be corrupted

– Restart of system must check all file systems that were not shut down properly• CHKDSK - Windows• FSCK – Unix and Linux



Remote File Systems Remote File Systems convert file

I/O requests to TCP/IP using Network Attach Storage (NAS) protocols

– File Server

– NAS Gateway

– NAS Appliance

Uses Network Interface Card (NIC) instead of HBA

Performance Overhead in converting File I/O to TCP/IP

LAN

FileSystem

Application

NASGateway

File I/O

File System Driver

File I/O

NIC



Remote File Systems– NFS – Network File System

– CIFS – Common Internet File System



Server



Server’s PCI Bus

Random I/O Sequential I/O

Although there are many types of applications…

there are primarily 2 different types of I/O

•Small-block I/Os (ex. 4K)

•Geared around IOPS (Input/Outputs per second)

•Large-block I/Os (ex. 512K)

•Geared around MB/sec (Throughput)



Random I/O Sequential I/O

•Applications use many, small data commands

•IOPS = measured by # of chunks of data per unit time

•R1, R10 and some R5 configs

•Applications use fewer, large data commands

•Throughput (MB/sec) = measured in amount of data transferred per unit time

•Therefore, applications will use larger-block sizes to reduce impact of overhead

•R3, R5 configs

Examples of random usage:

•OLTP/Database applications (SAP, Oracle, Peoplesoft, Siebel, etc.)

•Microsoft Exchange

•Microsoft SQL

•IBM DB2

Examples of sequential usage:

•File/print servers

•Streaming Media (Audio/Video, etc.)

•Medical Imaging

•Data archiving

•Near-line storage (disk-to-disk backup)

IBM Systems and Technology Group © 2008 IBM Corporation IBM System Storage Introduction This...

Documents

Transcript of IBM Systems and Technology Group © 2008 IBM Corporation IBM System Storage Introduction This...