CTI Group- Blue power technology storwize technical training for customer - published

Storwize v7000 – Technical Training
Optimized, Virtualized, & Consolidated

© Blue Power Technology 2012

IBM System Storage: Optimized systems. Optimal innovation.

Agenda

Concept & Architecture
Overview

NAS at a glance

Demo Session



Smarter Systems Are Creating an Information Explosion

Zettabytes  Storage requirements growing 20% - 40% per year
 Information doubling every 18 - 24 months Instrumented.
Interconnected.
 Storage budgets up 1% - 5% in 2010
Intelligent.
Exabytes  Storage utilization remains <50%

Petabytes +
The information explosion
meets budget reality
Terabytes
+
Gigabytes
2000 2005 2010 2015
3 © Blue Power Technology 2012


IBM Storage Platform Portfolio

Centralized, Heterogeneous Backup, Recovery, &
Storage Management De-duplication Services
Tivoli Productivity Center Tivoli Storage Manager

Virtualized Storage Services Shared File Services ProtecTIER
Consistent Presentation
Local Duplication SoNAS
Remote Replication N-Series

SAN Volume Controller Storage Area
& iSCSI
Networks

IBM Non-IBM

DS8000
EMC
IBM Tape
DS5000 XIV HP
V7000
HDS

DS3000 Others

Local & Offsite
Tiered Storage Autonomic Storage Other Storage Backup



Optimized for z/OS and IBM i
IBM Disk Portfolio Optimized for ‘open systems’

Block File
DS8000 XIV SONAS
For clients requiring: For clients requiring: For clients requiring:
 Advanced disaster recovery  Breakthrough ease of use and  Massive I/O, backup, or
with 3-way mirroring and management restores
System z GDPS support  High utilization with automated  Consolidation, or scale large
Enterprise  Continuous availability, no performance (“hot spot”) numbers of clusters
downtime for upgrades management
 Best-in-class response time for  Virtually unlimited snapshots
OLTP or transaction  Advanced self-healing
workloads, flash optimization architecture
 Single system capacity
scalable to the PB range
N series
Storwize V7000
For clients requiring: For clients requiring:
 10s of TB of rack-mounted storage with sophisticated software  NAS storage
functions  Simple two-site high availability
 Breakthrough ease of use and management
Midrange  Non-disruptive migration from, or virtualization of, existing disk
V7000 unified
For clients requiring:
 NAS storage
 Add-on SAN storage
 Cluster File Module

V3700 For clients requiring:
 SMBs or branch office locations; cost sensitive; start at as small as
Entry 100s GB, up to low TB capacity

SVC, Easy Tier, ProtecTIER, Information Archive, Real Time Compression
Storage Optimizers For clients requiring optimization of storage costs:
 Storage technologies that add function, performance, ease of use, or efficiency to new or existing storage



Storage Virtualization Overview



Modular Hardware Building Blocks

Software inherited from prior Offerings plus Enhancements
Software inherited from SVC and DS8000 RAID New and enhanced Software functions
 RAID 0, 1, 5, 6, 10  New GUI (Easy-to-use, web based, XIV like)
 Storage Virtualization (Internal and external disks)  Easy TierTM SSD exploitation
 Non-disruptive Data Migration  RAID & enclosure RAS services and diagnostics
 Global & Metro Mirror (Multi-site)  Additional scalability improvements
 FlashCopy (256 targets,cascaded,incremental,Space Eff.)  Enhanced Host, Controller and ISV interoperability
 Thin Provisioning  Integration with IBM Systems Director
 Scalable cluster up to 4 control enclosure (s/w 6.4)  Enhancements to TPC, FCM and TSM support


Hardware Overview
 SBB 2.0 (Storage Bridge Bay Working Group) compliant 2U form factor
– Specification that defines mechanical, electrical and low-level enclosure management
requirements
– www.sbbwg.org
 Base for all four Control / Expansion models
 No controls on the enclosure itself
 Rear of the Enclosure:
– Two power supply slots
● One on the extreme left and one on extreme right each taking up the full 2U height
● The left hand slot is for power supply 1
● The right hand slot is for power supply 2
● The power supplies are identical for a given enclosure
– Two canister slots
● One above the other in the middle of the chassis
● The top slot is for canister 1 and the bottom slot is for canister 2
● The canisters are identical for a given enclosure



Hardware Overview
 Intel Jasper Forest quad core 64-bit CPU at 2.1 Ghz
 8 GB Cache using 2 x 4GB DIMM’s
– Mirrored and battery protected
 Four 2/4/8 Gbps Fibre Channel ports
– PMC Sierra Tachyon based Fibre Channel cards (same as 2145-CF8 nodes)
– Usage optional
● For external storage
● And/or for server attachment
● And/Or Remote Copy/Mirroring

 Two USB 2.0 ports
 Two 10/100/1000 Mbps Ethernet ports
– Port 1 usage required
– Port 2 usage optional
 Two 6 Gbps SAS ports
– SPC SAS protocol chip (same as 2145-CF8 & 2145-CG8 for its connection to internal SSD drives)
– Usage optional for expansion enclosures
 On models 312 & 324, two 10Gbps Ethernet ports
– On models 112 & 124, the adapter is blanked out


Control Enclosure Rear View - 2076-112/124

Top node canister

Four 2/4/8Gbps Fibre Two USB2 ports Two 1Gbps Two 6Gbps SAS ports
Channel ports Ethernet ports (connections to expansions)

Power Supply Unit (PSU) Power Supply Unit (PSU)
Power Cooling Module (PCM) Power Cooling Module (PCM)
& Battery & Battery
Note: identical but installed upside
down Bottom node
canister
Note: identical but
installed upside down



Control Enclosure Rear View - 2076-312/324

Top node canister

Two 6Gbps SAS ports
(connections to expansions)
Four 2/4/8Gbps Fibre Two USB2 ports Two 1Gbps Two 10Gbps
Channel ports Ethernet ports Ethernet ports

& Battery & Battery
Note: identical but installed upside
down Bottom node
canister
Note: identical but

Existing V7000 systems can be upgraded by replacing both node canisters in the existing control enclosure
11


Node Canister Internals

 SBB interface connects to midplane of enclosure chassis
 Intel “Jasper Forest” quad core CPU running at 2.1 GHz
 8GB cache using two 4GB DIMMs
 32GB internal flash drive for Linux and Storwize V7000 software

12


Expansion Enclosure Rear View - 2076-212/224
Top expansion
canister

6Gbps SAS connection 6Gbps SAS connection to lower
to Top node or upper enclosure enclosure (top canister)
(top canister)

Note: identical but installed 6Gbps SAS connection to lower 6Gbps SAS connection
upside down enclosure (bottom canister) to Bottom node or upper
enclosure (bottom canister)
Bottom expansion
canister
Note: identical but



Expansion Canister Internals

 SBB interface connects to enclosure chassis midplane
 Single SAS Expander per canister with redundant SAS chain access



Enclosure Front View

 2076-112/212/312
– 12 x 3.5” LFF Drive Bays
– Four columns of three horizontally mounted drive carriers
– Drive slots are numbered 1 to 12 starting top left and going left to right and top to bottom

 2076-124/224/324
– 24 x 2.5” SFF Drive Bays
– One row of 24 vertically mounted drive carriers
– The drive slots are numbered 1 to 24 from left to right



Drive Options

Drive Type Vendor Drive Name Drive Sizes
SSD STEC Hikari
200 & 400GB New!
(eMLC) Hitachi Ralston Peak
SAS
Seagate Hornet 146 & 300GB
Model 124/224 15K RPM
2.5” Small Form Factor
SAS Firefly 300GB
(SFF) Seagate
10K RPM Firestorm 450 & 600GB
NL-SAS
Seagate 1TB
7.2K RPM
Model 112/212
NL-SAS
3.5” Large Form Factor Seagate Muskie 2 & 3TB
7.2K RPM
(LFF) New!



SAS 1.0 and 2.0 Chipset
Support Pure
3Gb/s 3Gb/s 6Gb/s
Serviceability Feature 4Gb/s
SAS SAS SAS
FC 2.0
1.0 2.0
 Most mainstream vendors are comfortable using
SAS 1.0 in smaller SMB environments where Drive Channel Health Monitoring YES YES YES YES

fewer than fifty drives are involved Collect All Port Statistics YES YES YES YES

 SAS 1.0 is attractive due to it’s lower price, but Retrieve Drive Diagnostic Data YES YES YES YES

that price is achieved by excluding some of the Cabling Error Mis-Wire Detection
YES YES YES YES
important features found in more robust FC drives and Notification

 Some vendors are starting to promote SAS 2.0 Degraded Wide Port Notification N/A YES YES YES

drives in an effort to make their systems appear to Automatically Disable Faulty Port YES YES YES YES
be SAS 2.0-Ready but aren’t fully compliant
Drive Channel Initialization Storm
 Other storage vendors are waiting on more than Protection
YES NO NO YES

just SAS 2.0 drives and are waiting on SAS 2.0 Maintain History of Port Statistics YES NO NO YES
chipsets before implementing SAS in the Proactive Drive Health Monitoring YES NO NO YES
midrange and enterprise systems
SATA Drive SMART Event Polling YES NO NO YES
– SAS 2.0 chipsets bring the potential for true robustness &
fault tolerance, missing in SAS 1.0 chips Slow PHY Speed Detection YES NO NO YES
– SAS 2.0 chipsets bring full-featured error reporting & Drive Port Fault Protection YES NO NO YES
integrity checking which are missing in SAS 1.0 chips
Controller FRU Fault Isolation
 Storwize V7000 has a SAS 2.0 6Gb/s chipset Diagnostics
YES NO NO YES

and runs at 6Gbps only T10 PI and 520B Support with
Yes NO NO YES
Recovered Error Limits

Improved Redundant Drive Path
NO NO NO YES
Fault Tolerance

Controller to Controller Channel
NO NO NO YES
Fault Protection



SAS Controllers and Expanders

Chain 2 Chain 1

 A string of enclosures on a SAS chain are connected via two Strands
– Each Strand is an independent SAS domain (network) providing redundancy to the
enclosures and associated disk drives

 A SAS Expander is basically a switch with point to point connection to every drive in the
enclosure
 Two Expanders per enclosure
– One per canister allowing access to a given disk drive per a SAS chain by either node
canister for redundancy



SAS Ports and Cables

SAS SAS Phy
Physical SAS LEDs
Port Cable Port
Link
Phy Phy
Phy Phy
Phy Phy
Phy Phy

 A phy contains a transceiver (transmitter + receiver)
 A physical link connects two phys and contains a pair of wires for full duplex
transmission at 6 Gbps
 A SAS port on the Storwize V7000 contains four phys
 A SAS cable contains four physical links or lanes with total transmission bandwidth of
24 Gbps



SAS Ports and Cables

 SAS cables always connect from one top enclosure canister to
another top enclosure canister and from one bottom enclosure
canister to another bottom enclosure canister in a SAS Chain
– Never connect the top canister of one enclosure to the bottom
canister of another enclosure or vice versa
• Errors will be logged indicating the system is miss cabled
 Expansion Enclosure
– An expansion enclosure connects to only one SAS chain
– No restrictions on which SAS chain an enclosure connects to
• Can connect 5 enclosures to chain 1 before adding any to chain 2
Not recommended for RAID 10 as code tries to use drives from both chains for
enclosure loss protection and/or SAS chain failure protection
– Intermix of 12 or 24 drive enclosures on same chain supported



SAS Ports and Cabling

Drives in Control Enclosure are part of SAS Chain 2

SAS Chain 2 SAS Chain 1

Supported but now we would have 3 enclosures Since each SAS Chain currently has only
on SAS Chain 2 and only one on SAS Chain 1 one enclosure we could add this second
expansion enclosure to either Chain


Virtualisation Concepts & Limits

Hosts
Single Multipath driver • Up to 256/1024(2) Hosts
per IO group/cluster
Volumes • Up to 512/2048 (2) FC ports per IO group/cluster
• Up to 2,048/8,192(2) Volumes per IO group/cluster (SDD, MPIO)
• Up to 256/1024(2) iSCSI ports per IO group/cluster
• Max. Volume size of 256TiB
iSCSI or FCP
• Image Mode = Native Mode
Host Mapping
• Managed Mode = Virtualized Mode LAN SAN

Storwize
V7000
SSD SAS NL-SAS

Storage Pools
• Up to 128 MDisks per
Pool 1
Vol2
Vol1 Pool 2 Pool 3 Pool 4 Pool 5
Vol3 Vol7
Vol4 Vol5 Vol6 Storage Pool
• Up to 128 storage pools
per cluster

Internal Storage External Storage

Internal Storage External Storage
1 to 8/16 drives (HDD) to form an Array Up to 4,096 MDisks Max. External MDisk Multiple Storage Subsystems
1 Array  Managed Disk (MD) Size of 2TiB 1 LUN  Managed Disk (MDdisks)
Or greater(1)
Enhanced! (1) Check Storwize V7000 interoperability website to obtain the list of Disk Subsystems supported with greater than 2TB MDisks
22 http://www-03.ibm.com/systems/storage/disk/storwize_v7000/interop.html
Round-robin port selection for back-end storage subsystems (2) available via RPQ, default support should be divided by 2


RAID arrays

Striped
RAID Drive Approximate Sparing Goal
Description Redundancy Width Goal
Level Count Array Capacity (With Preset)
(with Preset)

0 Striped with no protection 1-8 DC * DS None 0

1 Mirrored 2 DS 1 2 1

5 Striped with parity 3 – 16 (DC – 1) * DS 1 8 1

6 Striped with dual parity 5 – 16 < ((DC – 2) * DS) 2 12 1
2 – 16
10 Mirrored then striped (DC/2) * DS 1 – DC/2 8 1
(even only)
DS = Drive Size - DC = Drive Count
 Strip Size
– 128KB and 256KB (default) are available. There is no obvious use case for
utilising smaller strip size
 Arrays are instantly available once they have been created
– Initialization is performed as a background task
 All arrays in the system can be rebuilding at the same time
 RAID limits can be seen in the table below
– Some of these configurations are only available through the CLI


Anatomy of a Managed Disk

MDisk001
32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB 32KiB


 A block on a MDisk has a 512Bytes size

 A MDisk is divided into multiple tracks
– A track on a MDisk has a 32KiB size
16MB


• Made of 64 blocks
Extent


 When a MDisk is added to a Pool, it is divided into

extents

– Each extent is made of multiple tracks

• ie. 512 tracks for a 16MiB extent, 1024
tracks for a 32MiB extent, etc.
 Each node in the cluster shares a mapping table


of each given extent from each Pool


– This common table size is therefore a cluster


limitation = up to 4,194,304 extents














Extents & blocks
 An extent is a multiple integer of 512Bytes blocks Extent Maximum cluster
Size (MB) capacity (TB)
 An extent size range from 16MiB to 8,192MiB 16 64
– The larger is the extent size, the more capacity can be 32 128
managed in a cluster 64 256

 A cluster can manage up to 4,194,304 extents (222) 128 512
256 1,024
 The extent size is defined at a Storage Pool level
512 2,048
 The maximum number of extents per Volume is 217 1,024 4,096
(which is 131,072) 2,048 8,192
– With extent size of 16MiB, maximum Volume size is 2 TB 4,096 16,384
– With extent size of 2GiB, maximum Volume size is 256TB 8,192 32,768

 Volume “stripping”
– Given the size of an extent, it is contributing to a distribution of the capacity among all
or a least a large number of MDisks
– By distributing the 1st extent of Volumes on different MDisks, the workload is more
likely to be distributed on a maximum number of spindles



Striped Volume



Sequential Volume



Image Mode Volume



 Cache partitioning  Snapshot-FlashCopy (Point-In-Time copy)
 Easy to use GUI – Up to 256 target per source
– Real Time Performance – Full (with background copy = clone)
Statistics – Partial (no background copy)
Up to 256

 Embedded SMI-S agent – Space Efficient Vol0
Source
Vol1
FlashCopy
target of Vol0
Vol2
FlashCopy
target of Vol1

 E-mail, SNMP trap & Syslog error event logging – Incremental Map 1 Map 2

 Authentication service for Single Sign-On & LDAP – Cascaded
Map 4

 Virtualise data without data-loss – Consistency Groups
Vol3 Vol4

– External storage virtualization (optional) – Reverse FlashCopy
target of Vol1
FlashCopy
target of Vol3

 Expand or shrink Volumes on-line  Microsoft Virtual Disk Service & Volume Shadow
 Thin-provisioned Volumes Copy Services hardware provider
– Reclaim Zero-write space  Remote Copy (optional)
– Thick to thin, thin to thick & thin to Volume
– Synchronous & asynchronous remote replication with
thin migration Storwize V7000
Consistency groups Storwize V7000 Storwize V7000

 On-line Volume Migration
Volume MDisk MDisk
Source Target
MM or GM Consolidated MM or GM
Storwize V7000 Relationship
Relationship DR Site
 Volume Mirroring Storwize V7000
Volume Volume
copy 1 copy 2

MM or GM Relationship
 EasyTier: Automatic relocation of hot and cold
extents SSDs HDDs SSDs HDDs  VMware
Automatic
Storwize V7000
Relocation
– Storage Replication Adaptor for Site Recovery
Manager
29 Hot-spots Optimized performance and throughput
– VAAI support & vCenter Server management plug-in


User Interface
Based on the well-received XIV interface

System
recommendations

Visual task flow
guidance

Integrated video
instruction

System status
always available Link to more
information if
needed


Hot-spots Optimized performance and throughput
IBM Easy Tier Transparent
reorganization

 What is Easy Tier?
– A function that dynamically re- distributes active data across multiple tiers of storage class based on workload
characteristics  Automatic storage hierarchy
● Hybrid storage pool with 2 tiers = Solid-State Drives & Hard Disk Drives
● I/O Monitor keeps access history for each virtualisation extent (16MiB to 2GiB per extent) every 5 minutes
● Data Placement Adviser analyses history every 24 hours
● Data Migration Planner invokes data migration  Promote hot extents or demote inactive extents
– The goal being to reduce response time
– Users have automatic and semi-automatic extent based placement and migration management
SSDs HDDs SSDs HDDs

Automatic
Relocation

 Why it matters? Optimized performance and throughput
Hot-spots
– Solid State Storage has orders of magnitude better throughput and response time with random reads
– Full volume allocation to SSD only benefits a small number of volumes or portions of volumes, and use cases
– Allowing dynamic movement of the hottest extents to be transferred to the highest performance storage
enables a small number of SSD to benefit the entire infrastructure
31 – Works with Thin-provisioned Volumes © Blue Power Technology 2012


Use Easy Tier on Storwize V7000 1/2

 By default, a Storage Pool mixing both Tiers “Hard Disk Drive” and “Solid-State
Drive” is Easy Tier Active. Easy Tier can be disabled using CLI
– svctask chmdiskgrp –easytier off <Storage Pool/Mdisk Group ID or name>
• On, off & auto supported



Use Easy Tier on Storwize V7000 2/2

 By default a new Volume created in this pool is Easy Tier Active. Easy Tier can
be disabled using CLI
– svctask chvdisk –easytier off <Volume/VDisk ID or name>
33
● On and off supported © Blue Power Technology 2012


Thin-provisioning

 Traditional (“fully allocated”) virtual disks use physical disk capacity for the entire
capacity of a virtual disk even if it is not used
 With thin-provisioning, Storwize V7000 allocates and uses physical disk capacity
when data is written
Dynamic
growth

Without thin provisioning, pre-allocated space is With thin provisioning, applications can grow
reserved whether the application uses it or not dynamically, but only consume space they are
actually using
 Available at no additional charge with base virtualization license
 Support all hosts supported with traditional volumes and all advanced features
(EasyTier, FlashCopy, etc.)
 Reclaiming Unused Disk Space
– When using Volume Mirroring to copy from a fully-allocated volume to a thin-
provisioned volume, Storwize V7000 will not copy blocks that are all zeroes
– When processing a write request, Storwize V7000 detects if all zeroes are being
written and does not allocate disk space for such requests in the thin-provisioned
volumes
• Helps avoid space utilization concerns when formatting Volumes
 Done at Grain Level (32/64/128/256KiB)  If grain contains all zeros don’t write



Anatomy of Thin-provisioned Volumes
... Let’s assume Volume Vol2 is Thin-provisioned
POOL

Logical View
Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain





MD1 MD2 MD3 MD4 Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain



All grains of Vol2 are accessed via the meta-data Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain


• Some grains are only logical, and logically filled with zeros Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain

• Some grains are also physical and physically filled with zeros and ones

Virtual Capacity

– SVC 5.1 with CF8 nodes as well as Storwize V7000 can track any assigned grain that can be Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain

reclaimed because full of zeros  joins the pool of free grains Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain


Extent 1 – MD4/4 Meta-data (stored in real capacity) Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain

Grains used


Extent 2 – MD1/5

Real Capacity

with data

Extent 3 – MD2/5 Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain



Extent 4 – MD3/5
Free grains

Extent 5 – MD4/5


Physical View Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain
Grain

Grain

3 mapping examples to show that physical grains are assigned when Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain Grain

needed and not based on their logical location


Non-disruptive Data Migration

Traditional SAN Storwize V7000
1. Stop applications 1. Move data
2. Move data  Host systems and applications are not affected
3. Re-establish host connections  In both cases, if it is with a new back-end external storage, you need to…
– Cabling,
4. Restart applications
– Change the SAN zoning,
– Create arrays & create LUNs in the arrays,
– Assign those LUNs to the server or Storwize V7000
Once Managed Disk Groups are created using the assigned LUNs, Volumes will be migrated between
MDG with just one command/click

 Migration scenarios:
– Image mode to image mode
– Image mode to managed mode
– Managed mode to managed mode
SAN – Managed mode to image mode

SAN
Storwize V7000

Migrate on-line to decommission, up-Tier, down-Tier, re-Tier…
Image mode = Native mode
Managed mode = Virtual mode
vSphere Storage VMotion can migrate virtual machines between VMFS volumes
Storwize V7000 & SVC can migrate VMFS volumes as well as Raw Device Mappings
36 Don’t use migration wizard to migrate cluster host or SAN boot images, otherwise migrate outside wizard Blue Power Technology 2012
©


Volume Mirroring
Back-end high availability & migration
Enhanced!

Storwize V7000

 Storwize V7000 stores two copies of a Volume R W

– It maintains both copies in sync, reads primary copy and writes to both copies
 If disk supporting one copy fails, Storwize V7000 provides continuous
data access by using other copy
– Copies are automatically resynchronized after repair Copy 1
 Intended to protect critical data against failure of a disk system or disk array Copy 0
– A local high availability function, not a disaster recovery function
 Copies can be split
– Either copy can continue as production copy
 Either or both copies may be thin-provisioned
– Can be used to convert fully allocated to thin-provisioned volume
• Thick to thin migration
– May be used to convert thin-provisioned to fully allocated
• Thin to thick migration
 Mirrored Volumes use twice physical capacity of un-mirrored Volumes
– Base virtualization licensed capacity must include required physical capacity



Business Continuity with Storwize V7000

Traditional SAN Storwize V7000
 Replication APIs differ by vendor  Common replication API, SAN-wide, that
 Replication destination must be the does not change as storage hardware
same as the source changes
 Different multipath drivers for each  Common multipath driver for all arrays
array  Replication targets can be on lower-cost
 Lower-cost disks offer primitive, or no disks, reducing the overall cost of
replication services exploiting replication services

FlashCopy® TimeFinder
Metro/Global Mirror SRDF
SAN
SAN Storwize V7000 Storwize V7000

IBM IBM EMC EMC
DS5000 DS5000 Clariion Clariion HDS Internal HP EMC Internal
AMS EVA Clariion

Copy Services with Storwize V7000

Volume Mirroring FlashCopy Metro Mirror Global Mirror
 Volume Mirroring  Point-in-Time Copy  Synchronous Mirror  Consistent Asynchronous Mirror
“outside the box” “outside the box” – Write IO response time – Limited impact on write IO response
2 close sites (<10Km) 2 close sites (<10Km) doubled + distance latency time
Warning, there is no consistency Warning, this is not real time – No data loss – Data loss
group replication 2 close sites (<300 Km) – All write IOs are sent to the remote
Warning, production performance impact if site in the same order they were
inter-site links are unavailable, during received on source volumes
microcode upgrades, etc. – Only 1 source and 1 target volumes
2 remote sites (>300 Km)

Vol0 Vol0’
R W
Vol0’

Storwize Storwize
V7000 V7000

Internal Storage External Storage Internal Storage

Source and target can have different characteristics and be from different vendors
Source and target can be in the same cluster


FlashCopy® Function

 Volume-level local replication function
– Within or between Storage Pools
 Designed to create copies for backup, parallel processing, test, cloning (i.e. boot
drives)…
 Copy available almost immediately for use
 Background copy operation or “copy on 1st write”
 Up to 4096 FlashCopy mappings
 Up to 256 copies of a single source volume
 Up to 127 FlashCopy Consistency Group Up to 256

 Up to 512 Volumes per FlashCopy Consistency Group
 Source and target volumes may be on internal drives and/or
any supported external disk systems



Technology Integration Continues
…IBM brings you the IBM Storwize V7000 Unified Storage System
Innovative GUI
Snapshots

SAN Easy Tier

Virtualization RAID

V7000
Unified

V7000
Unified

IBM Storwize V7000 Unified

IBM Active
Clustered File
Cloud
Engine™ Systems Support


IBM Storwize V7000 Unified

What this is
 Unified block and file storage system
with a tightly integrated management
console
V7000 Unified

 Support for NFS/CIFS/FTP/HTTP/SCP
file protocols in addition to existing block 6U V7000 Unified

functions
 File replication and file level snapshots
for business continuity and disaster
recovery

Why It Matters
 Provides greater flexibility for provisioning of storage resources and improves overall
capacity utilization
 Unified console simplifies storage administration with a single user interface and
common CLI
 Enables deployment of a broad set of applications from within a single storage system,
especially in shared storage environments



Benefits to You - IBM Storwize V7000 Unified
 Modular, midrange disk storage that grows as your needs grow
– Unified model scales to 240 HDDs (ten 24 bay control enclosures) Expand Easily
– Base model scales to 480 HDDs (twenty 24 bay control enclosures)
 Support for 10Gbps iSCSI server attach
– Up to 7x improvement in iSCSI throughput vs. 1Gbps iSCSI
– Upgradable from existing Storwize V7000 systems
 Enterprise class capabilities in a midrange offering
– Virtualization, thin provisioning, FlashCopy, Easy Tier all built in
– Sophisticated local and remote mirroring
 High Performance in a Midrange Disk System
– Up to almost 1M IOPS
– Up to 82,000 IOPS for “database-like” 70/30 R/W workload
 Easy to set up and manage
– Innovative, intuitive GUI eliminates complexity
– Non-disruptive data migration included, unique in a product of this class
 Ushering in a new era in storage efficiency
– Save up to 75% of space using space efficient FlashCopy
– Increase disk utilization up to 30%
 Investment protection
– Virtualize external storage arrays and extend asset life Start Small
 IBM Active Cloud EngineTM with V7000 Unified
– Cloud Storage is an attractive means of delivering storage services
while saving both time and cost


Storwize V7000 Unified User Interface

Storage pools may be
File management shared between block and
integrated into file workloads
navigation

File storage management
completely integrated



What’s an Active Cloud
Engine™? Think of it as a very
smart, very fast robot – that
never sleeps – keeping your
cloud storage neat, tidy, and
running smoothly…



Understanding IBM Active Cloud Engine
Terminology
• A fileset is a logical subtree of the file
system namespace and provides a way to
partition the namespace into smaller, more
manageable units

• Multiple levels of rules (policies) can be
applied because the complete policy rule set
is evaluated for each file when the policy
File System
engine executes
Filesets
• Storage pools allow you to group multiple
Policy Engine physical storage devices within a file system
(SAS, NL-SAS, external storage)
Storage Pools

External
Pool 1 Pool 2
Pool Interface
File Data

External Storage
Management Application

TSM/HSM



File Example Using Active Cloud Engine

File creation
30 days

EasyTier
SSD / SAS
180 days
60 days (deduplicate)

NL-SAS SATA

Externally Virtualized HP EVA Backup
(For files accessed by NFS only) catalog

Intelligent Backup offers
(deduplicate) Better efficiency: Progressive incremental, deduplication
Tighter control: File-level policy control
Faster recovery: Backup catalog
vs NDMP


IBM Tivoli Storage FlashCopy Manager
For Storwize Rapid Application Storage Manager and Storwize Rapid Application Backup

 Online, near instant snapshot
backups and near instant restore
FlashCopy Manager
Local
 Simplifies deployment and Snapshot
management of advanced, Application
Application Versions
System
application-aware data protection Data
Snapshot
for IBM storage systems Backup
 Improves backup and recovery
times from hours to a few minutes Snapshot
Restore
 Improves productivity by simplifying Storage manager
management and automating 6

routine administrative tasks
 Leverages existing investments With
Optional TSM
in IBM storage systems
IBM Storwize V7000 Backup
Integration
 Integrated with IBM
Storage Hardware



Increase Storage Utilization

Do you know how much of your disk capacity you are actually using?
Could you benefit by increasing your disk utilization by 30% or more?

*Virtualization
Virtualized volumes are
Used Used mapped to physical devices
Used Less physical storage
Used Used Used Used Used can be used

Thin Provisioning
Dynamic
growth More productive use
of available storage

Without thin provisioning, With thin provisioning, applications can Across all supported
pre-allocated space is reserved grow dynamically, but only consume host platforms
whether the application uses it or not space they are actually using

Create instant application copies
FlashCopy
for backup or application testing
Make better use of space
Up to 256 with incremental or thin
Copies provisioned snapshots
Reduce space required for
*Storwize Rapid Application Storage Manager ONLY copies by 75% or more


Improve Administrator Productivity

Would you like to free up your storage administrators from basic managements
tasks to focus on more strategic projects?
Are you confident administrators can handle the anticipated growth in storage requirements
over the next two or three years without impacting service levels or responsiveness?

Storwize Rapid Application Storage
helps storage administrators:
Create Storage
Provision storage Pool
Breakthrough ease of use allows storage to be
provisioned in seconds rather than hours

Migrate data
Online data migration moves data with ease, reducing Create Volumes
application downtime from days to minutes

Protect data
Automated application aware backups and restores
reduce application downtime from hours to minutes

Tune performance
Real-time performance monitoring improves
performance analysis time by 25%


Increase Application Performance

Could your users benefit from 60% better response time?
Are you meeting your service levels consistently?
Can you identify and resolve storage related performance issues quickly?

Performance Optimization
Transparent Analyze system performance and
reorganization throughput
Transparently rearrange the data to
eliminate hot-spots and improve
performance
Hot-spots due to poor Optimized performance
data layout and throughput

IBM Easy Tier SSD Management
Busiest data is identified and
SSDs HDDs SSDs HDDs
automatically relocated to highest
Automatic performing Solid-state Disks
Relocation
Easy Tier can Increase
performance by 300% moving only
10% of data to SSD
Hot-spots due to poor Optimized performance
data layout and throughput


Increase Application Availability

Would you like to shorten your backup windows?
Are you confident you can restore your data quickly if necessary?
Do you know how much data would have to be recreated after a data restore operation?

Application Aware Backups
Integrated, instant copy virtually eliminates
backup windows
Rapidly create clones for application testing
View inventory of application copies
and instantly restore
Up to 256 Improve data protection by 95%
Copies
with hourly backups

*Transparent - Online Application
Data Movement server
Transparently move application data from
legacy disk arrays to the new system
Reduce migration elapsed time from weeks
or months to days
Network
Legacy

*Storwize Rapid Application Storage Manager ONLY



Increase Data Availability
Mirroring. Automated Failover

Local Mirror
For ultra-high availability applications,
synchronously mirror application data between
two separate disk enclosures attached to the
same system.

Mirror data off-site  Synchronously over Metro distances.
 Asynchronously over Global distances.

Network
 Application-level consistency groups.

Practice recovery procedures  For critical application consistency groups,
freeze the Mirror and take a
consistent FlashCopy.
Recovery
practice  Practice application recovery procedures
Network volume from the FlashCopy.

Automatically respond to disasters  Detect mirroring failure and automate failover
to Recovery volume.
 Execute practiced application
Recovery recovery procedures.
volume
Network
 Automate fail-back after repair.


Thank you for your time today.

For more information:
 http://publib.boulder.ibm.com/infocenter/storwize/ic/index.jsp
 http://www-03.ibm.com/systems/storage/disk/storwize_v7000/resources.html
 http://www.redbooks.ibm.com/abstracts/sg247938.html

Contact:
 marketing@bluepower-tech.com



Trademarks and notes

 IBM, the IBM logo and ibm.com are registered trademarks, and other company, product
or service names may be trademarks or service marks of International Business
Machines Corporation in the United States, other countries, or both. A current list of IBM
trademarks is available on the Web at “Copyright and trademark information” at
www.ibm.com/legal/copytrade.shtml
 Adobe, the Adobe logo, PostScript, the PostScript logo, Cell Broadband Engine, Intel,
the Intel logo, Intel Inside, the Intel Inside logo, Intel Centrino, the Intel Centrino logo,
Celeron, Intel Xeon, Intel SpeedStep, Itanium, IT Infrastructure Library, ITIL, Java and
all Java-based trademarks, Linux, Microsoft, Windows, Windows NT, the Windows logo,
and UNIX are trademarks or service marks of others as described under “Special
attributions” at: http://www.ibm.com/legal/copytrade.shtml#section-special
 Other company, product and service names may be trademarks or service marks of
others.
 References in this publication to IBM products or services do not imply that IBM intends
to make them available in all countries in which IBM operates.



Hindi
Hebrew

Simplified

Russian
Chinese

Gracias
Th kYo Obrigado
an u English
Spanish

Arabic Brazilian Portuguese

Danke
Grazie German
Italian
Korean Merci
French

Japanese
Tamil
Thai
Traditional Chinese



Notices and Disclaimers

Copyright © 2011 by International Business Machines Corporation. All rights reserved.

No part of this document may be reproduced or transmitted in any form without written permission from IBM Corporation.

Product data has been reviewed for accuracy as of the date of initial publication. Product data is subject to change without notice. This document could
include technical inaccuracies or typographical errors. IBM may make improvements and/or changes in the product(s) and/or program(s) described
herein at any time without notice. Any statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and
represent goals and objectives only. References in this document to IBM products, programs, or services does not imply that IBM intends to make such
products, programs or services available in all countries in which IBM operates or does business. Any reference to an IBM Program Product in this
document is not intended to state or imply that only that program product may be used. Any functionally equivalent program, that does not infringe IBM's
intellectually property rights, may be used instead.

THE INFORMATION PROVIDED IN THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER OR IMPLIED. IBM LY
DISCLAIMS ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IBM shall have no
responsibility to update this information. IBM products are warranted, if at all, according to the terms and conditions of the agreements (e.g., IBM
Customer Agreement, Statement of Limited Warranty, International Program License Agreement, etc.) under which they are provided. Information
concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources.
IBM has not tested those products in connection with this publication and cannot confirm the accuracy of performance, compatibility or any other claims
related to non-IBM products. IBM makes no representations or warranties, ed or implied, regarding non-IBM products and services.

The provision of the information contained herein is not intended to, and does not, grant any right or license under any IBM patents or copyrights.
Inquiries regarding patent or copyright licenses should be made, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 1 0504- 785
U.S.A.



Special Notices

 This document was developed for IBM offerings in the United States as of the date of publication. IBM may not make these offerings available in other
countries, and the information is subject to change without notice. Consult your local IBM business contact for information on the IBM offerings
available in your area.
 Information in this document concerning non-IBM products was obtained from the suppliers of these products or other public sources. Questions on
the capabilities of non-IBM products should be addressed to the suppliers of those products.
 IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you
any license to these patents. Send license inquires, in writing, to IBM Director of Licensing, IBM Corporation, New Castle Drive, Armonk, NY 10504-
1785 USA.
 All statements regarding IBM future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.
 The information contained in this document has not been submitted to any formal IBM test and is provided "AS IS" with no warranties or guarantees
either expressed or implied.
 All examples cited or described in this document are presented as illustrations of the manner in which some IBM products can be used and the
results that may be achieved. Actual environmental costs and performance characteristics will vary depending on individual client configurations and
conditions.
 IBM Global Financing offerings are provided through IBM Credit Corporation in the United States and other IBM subsidiaries and divisions worldwide
to qualified commercial and government clients. Rates are based on a client's credit rating, financing terms, offering type, equipment type and
options, and may vary by country. Other restrictions may apply. Rates and offerings are subject to change, extension or withdrawal without notice.
 IBM is not responsible for printing errors in this document that result in pricing or information inaccuracies.
 All prices shown are IBM's United States suggested list prices and are subject to change without notice; reseller prices may vary.
 IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms apply.
 Any performance data contained in this document was determined in a controlled environment. Actual results may vary significantly and are
dependent on many factors including system hardware configuration and software design and configuration. Some measurements quoted in this
document may have been made on development-level systems. There is no guarantee these measurements will be the same on generally-available
systems. Some measurements quoted in this document may have been estimated through extrapolation. Users of this document should verify the
applicable data for their specific environment.


CTI Group- Blue power technology storwize technical training for customer - published

More Related Content

What's hot

Viewers also liked

Similar to CTI Group- Blue power technology storwize technical training for customer - published

Recently uploaded

CTI Group- Blue power technology storwize technical training for customer - published