Virtual Users Group

SVC Architecture Overview

Bill Wiegand Advanced Technical Support

Innovation that matters

2009 IBM Corporation

IBM Systems

IBM System StorageTM

Agenda
Todays Storage Challenges SVC Architecture SVC Migration SVC Copy Services Space-Efficient VDisks

VDisk Mirroring

2009 IBM Corporation

IBM System StorageTM

Static relationship between

servers and storage systems Inefficient use of storage resources Migration of data disruptive and time consuming Copy Services

Storage Challenges Today

Out of SDD Drivers Space Out
of SDD Drivers Space

Proprietary, non-interoperable
No common storage
management interface

HDS Drivers

HDS Drivers

RDAC Drivers

FC Switch Management Application

Monolithic, potentially expensive

storage devices Pay for functionality when really just need capacity Use SVC and TPC to address
Out of Space

Flashcopy ?

Free capacity

DS8K

Remote Copy ?

HDS
010101010101010101 Data Migration 010010101101001000

DS5000

DS8K Specialist
3

HDS Mgmt. Application

DS5K Storage Manager

2009 2008 IBM Corporation

IBM System StorageTM

What is the IBM SAN Volume Controller (SVC)?

A SAN-based in-band storage virtualization product
Appears as a disk controller providing LUNs to servers These can be thin provisioned

Virtualizes IBM and non-IBM storage (over 175 systems from EMC, Dell, HP, HDS, NetApp, Sun, Pillar, & STK)

Provides non-disruptive data migrations between different storage

systems/different storage tiers

Provides copy services between different storage systems

A stable and proven product with 4,500 clients, 50PB of data managed, and
an install base of 14,000 SVC nodes and growing

And its fast, as measured by the Storage Performance Council

www.storageperformance.org

2009 IBM Corporation

IBM System StorageTM

IBM SAN Volume Controller

Hosts still see SCSI The SAN Volume SCSI LUNs are still to LUNs mapped Controller mapped to what they The SVC controls them that they insulates the host believe are hosts, but the mapping of believe are physical systems from the are really SVC nodes. Virtual to disks, but are really effects ofDisks changes SVCVirtual discovers the Disks Disks, aLUNs set inManaged the physical as Managed Disks. into preserves the ofand pointers are collected environment so disk - 4096 MDisks Max metadata in every basically, that are Managed Disk subsystems can be nodes cache and created with Groups to the moved in and out. on aservices quorum disk. capacity and quality facilitate different Copy can oftiers service required of storage span dissimilar by the application. capacity. subsystems as well. - 8196 Max - 128 VDisks MDGs Max - 128 MDisks per MDG Max

VD 1 VD 2 VD 3

VD 4

VD 5

VD 6

Virtual disks

Virtual-to-physical Mapping High Perf

MD 1 MD 2 MD 3 MD 4 MD 5

Low Cost
MD 6 MD 7 LUN 1 MD 8 LUN 2 LUN 3

Managed disks
LUN 1 LUN 2

LUN 3

LUN 4

VD 7

SCSI LUNs

IBM

EMC

LUN 4

2009 2008 IBM Corporation

IBM System StorageTM

SVC - Clustering
Designed to be a redundant, modular, scalable, solution
The pool of managed disks is controlled by a cluster of managed nodes (up to 4 pairs, scaling higher in the future)

Storage Network
Virtual Disks Virtual Disks Virtual Disks

VDisk I/Os are owned by a pair of nodes and host writes are mirrored between those nodes
Virtual Disks

Node

Node

Node

Node

Node

Node

Node

Node

Managed Disks

Each node is an xSeries eServer with 8GB of cache providing a total of 16GB of Read/Write cache per node pair

2009 IBM Corporation

IBM System StorageTM

SVC - Virtual Disk Modes

Image Mode: Virtual Disk = Physical LUN Used to bring existing data under SVC Sequential Mode: Virtual Disk mapped sequentially to a contiguous portion of one managed disk - It cannot span more then one managed disk Striped Mode: Virtual Disk striped across multiple managed disks in a MDG

A B C
I/O Group A I/O Group B

MDG1

MDG3

C
MDG2

2009 2008 IBM Corporation

IBM System StorageTM

SVC Hardware
Base Offering
Dual Storage Engine Clustered System
- Up To Four Engine Pairs Supported

UPS (Required with the SVC)

- 1U Form Factor

Why specify the engine?

Minimize complexity
Appliance mentality Easily scale performance Non-disruptive hardware upgrades Concurrent software code loads
Model 2145-8G4 Cache 8GB FC Adapters One 4 Port HBA

Each Engine Contains: - Modified xSeries x3550 Serve

- 1U 19" Rack Mounted Enclosure - One quad-core Intel Xeon processor at 2.33GHz - Front side bus 1333Mhz - 8GB of cache - Single 160GB SATA disk drive - Dual 10/100/1000 Ethernet Ports - PCIe/Express 8 lane bus for HBA - Single 4 Port, 4Gbs fibre HBA - Management Module - Heart Beat Timer - Control for VFD Display/Keypad - Power button intercept - Secondary Flashboot Device - Front Bezel - VFD Display - 5 Button Keypad
8

2009 2008 IBM Corporation

IBM System StorageTM

SVC Performance

Cache
8GB per node cache means that many reads are handled by SVC directly All writes are cached, means write to same block is handled by SVC directly without destage
SAN

Striping
Striping spreads I/O workload across many disks, even across disk controllers

Can greatly reduce hot spots as I/O from different applications are spread across multiple disks
2009 2008 IBM Corporation

SPC-1 Benchmark Results: 275K I/Os for an 8 node cluster

9

IBM System StorageTM

Understanding Host to SVC I/O

Master Console
W2K3 W2K NVL AIX Linux SUN HP VMWare

Host I/O

GUI/CLI

SCSI initiator

Fabric 1

Fabric 2

4 FC ports per SVC

SVC Node 1 SVC Node 2

SCSI target

SVC
SCSI initiator

DS Family EMC

SCSI target
10

2009 2008 IBM Corporation

IBM System StorageTM

I/O Group and Write I/O Distributed Cache

Write I/O request 1 I/O Group1 V1
Preferred node

V2
Alternative node

UPS1

SVC node1 Cache

SVC node2 Cache

UPS2

3
RED1 200 GB RED2 200 GB RED3 200 GB

11

2009 2008 IBM Corporation

IBM System StorageTM

I/O Group - Node Failover

1

Write I/O request 1 I/O Group1 V1

2 Alternative
node path

V2

UPS1

SVC node1

SVC node2 Cache

UPS2

Cache

3
RED1 200 GB RED2 200 GB RED3 200 GB

12

2009 2008 IBM Corporation

IBM System StorageTM

AIX1 VDisk1 Preferred Node and Paths

AIX1-A1 Zone (21,1;11,1;11,2)
AIX1

A1 A2 V1 1 A2

AIX1-A2 Zone (22,1;12,1;12,2)

1 A1
Fabric 1

ID 21

ID 22

1 2 11 21 14 24 D1 E1
Preferred paths

ID 11

1 2 13 23 12 22 D2 E2

Fabric 2
ID 12

Alternate paths

11 12 13 14 I/O driven only to paths on SVC1 V preferred node Preferred node 1

13

21 2 2 23 24
SVC2

I/O Group

Alternate node ESS

2009 2008 IBM Corporation

IBM System StorageTM

AIX1 VDisk2 Preferred Node and Paths

AIX1-A1 Zone (21,1;11,1;11,2)
AIX1

A1 A2 V2 1 A2

AIX1-A2 Zone (22,1;12,1;12,2)

1 A1
Fabric 1

ID 21

ID 22

1 2 11 21 14 24 D1 E1
Alternate paths

ID 11

1 2 13 23 12 22 D2 E2

Fabric 2
ID 12

11 1 2 13 1 4
SVC1

21 22 23 24
V2
SVC2

Preferred paths I/O driven only to paths on preferred node

Alternate node
14

I/O Group

Preferred node ESS

2009 2008 IBM Corporation

IBM System StorageTM

Understanding SVC to Disk Controller I/OHost I/O

Master Console
W2K3 W2K NVL AIX Linux SUN HP VMWare

GUI/CLI

SCSI initiator

Fabric 1

Fabric 2

4 FC ports per SVC

SVC Node 1 SVC Node 2

SCSI target

SVC
SCSI initiator

DS Family EMC

SCSI target
15

2009 2008 IBM Corporation

IBM System StorageTM

SVC to Disk Controller I/O

Multipathing from SVC to disk controller built into SVC software

No need for Powerpath, RDAC or SDD to talk to disk controllers Otherwise degraded mode on controller and/or MDisks

All SVC nodes must see same set of LUNs from disk controller

All SVC ports zoned to controller ports must see same set of LUNs

Otherwise degraded mode on controller and/or MDisks

16

2009 2008 IBM Corporation

IBM System StorageTM

SVC to Disk Controller I/O

All SVC nodes direct I/O to a specific LUN via a single disk controller port

Doesnt load balance I/Os to a specific LUN over multiple ports on the disk controller For example:
Six fibre ports on DS8K zoned with 4 node SVC cluster Sixteen 8 packs in DS8K each configured as one big LUN SVC discovers 16 LUNs/MDisks as MDisk 1-16 SVC cluster accesses MDisks 1,7 and 13 via DS8K port 1 SVC cluster accesses MDisks 2,8 and 14 via DS8K port 2 SVC cluster accesses MDisks 3,9 and 15 via DS8K port 3 SVC cluster accesses MDisks 4,10 and16 via DS8K port 4 SVC cluster accesses MDisks 5 and11 via DS8K port 5 SVC cluster accesses MDisks 6 and 12 via DS8K port 6

17

2009 2008 IBM Corporation

IBM System StorageTM

Server 1

Server 2
A B

Best Practice

SVC Cabling and Zoning

SAN Fabric B
SVC CLUSTER ZONING
Create one zone in the RED fabric with all the SVC node ports cabled to Fabric A and create one zone in the BLUE fabric with all the SVC node ports cabled to Fabric B. Example:
All odd (RED) SVC node ports in one zone and all even (BLUE) SVC node ports in one zone. Note: For a cluster to be created and to operate correctly all node ports must be zoned together.

SAN Fabric A
HOST ZONING
Create a SVC/Host zone for each server that receives storage from the SVC cluster. Example:
Zone Server 1 port A (RED) with all SVC node port 1's. Zone Server 1 port B (BLUE) with all SVC node port 2's. Zone Server 2 port A (RED) with all SVC node port 3's. Zone Server 2 port B (BLUE) with all SVC node port 4's. *** NOTE *** SVC supports a maximum of 256 host objects per I/O group thus a maximum of 1024 per cluster. The above host zoning results in each server being seen by every I/O group and the default host object creation behavior results in each host object counting as one towards this 256 maximum. To create more then 256 host objects in the cluster you must zone a host to a subset of the I/O groups, you must assign the host object at host creation time to that same subset of I/O groups and then you must assign that hosts VDisks to one of those I/O groups in that same subset.

I/O G-0 1 Node 1 3 1 Node 2 3 4 4 2 3 1 2 1

I/O G-1 2 Node 3 4 2 Node 4 4

SVC Cluster

MDisk Group 1 / DS5K_1 VDisk 1 Cntrl A Channels 2 and 4 Channels 1 and 3 VDisk 2

STORAGE ZONING
Create a SVC/Storage zone for each storage subsystem virtualized by the SVC cluster. Example:
Zone DS5K_1 controller A and B daughter card channel ports 1 and 3 with all SVC node ports 1 and 3 in the RED fabric. Zone DS5K_1 controller A and B daughter card channel ports 2 and 4 with all SVC node ports 2 and 4 in the BLUE fabric.

MDisk10 / Array10

MDisk11 / Array11

MDisk12 / Array12

MDisk13 / Array13

MDisk1 / Array1

MDisk2 / Array2

MDisk3 / Array3

MDisk4 / Array4

MDisk5 / Array5

MDisk6 / Array6

MDisk7 / Array7

MDisk8 / Array8

MDisk9 / Array9

VDisk 3 Cntrl B Channels 1 and 3 Channels 2 and 4 VDisk 4

18

2009 2008 IBM Corporation

IBM System StorageTM

Common Platform for Advanced Functions

Single point for copy services
Asynchronous remote copy/Global Mirror
Synchronous remote copy/Metro Mirror Point-in-time copy/FlashCopy Data Migration

Use to meet business needs

Disaster recovery up to 8000KM

Business Continuance less then 300KM

LAN/Server free backup, DB clones Tiered storage, disk replacement

Storage Network
Virtual LUNs Virtual LUNs Virtual LUNs Virtual LUNs Virtual LUNs Virtual LUNs VISC VISC VISC VISC VISC VISC VISC VISC VISC VISC VISC VISC

Storage Network
Virtual LUNs Virtual LUNs VISC VISC VISC VISC

Managed Disks

Managed Disks

19

2009 2008 IBM Corporation

IBM System StorageTM

SVC Remote Copy Services

SAN Volume Controller

SAN Volume Controller

LUN 1

LUN 2

LUN 3

LUN 4

LUN 1

LUN 2

LUN 3

LUN 4

LUN 1

LUN 2

LUN 3

LUN 4

LUN 1

LUN 2

LUN 3

DS8K

EMC

XIV

HDS

Cross-device consistency groups

20

2009 2008 IBM Corporation

LUN 4

IBM System StorageTM

Remote Copy Services

Source volume may be spread across multiple disk subsystems

Target volume may be to one or more disk subsystems, different than the source
Two SVC clusters connected to each other over a fibre channel fabric 10km Fibre distance supported with LW SFPs Extended distance support using FC "Extenders/Routers/DWDM" hardware One-to-one volume relationship Source and Target virtual disk must be the same size Suspend/Resume support Failover/Failback support Consistency Group support Up to 256 groups Invoked via Web User Interface, CLI or scripts Licensed independently of base virtualization software and FlashCopy License includes both sync and async replication capability Support for Intra-cluster remote copy allows for testing within one cluster
21

2009 2008 IBM Corporation

IBM System StorageTM

Common Platform for Advanced Functions

Single point for copy services
Asynchronous remote copy/Global Mirror

Use to meet business needs

Disaster recovery up to 10,000KM

Synchronous remote copy/Metro Mirror

Point-in-time copy/FlashCopy

Disaster recovery less then 300KM

LAN/Server free backup, DB clones

Data Migration

Tiered storage, disk replacement

Storage Network
Virtual LUNs Virtual LUNs Virtual LUNs Virtual LUNs Virtual LUNs Virtual LUNs VISC VISC VISC VISC VISC VISC VISC VISC VISC VISC VISC VISC

Storage Network
Virtual LUNs Virtual LUNs VISC VISC VISC VISC

Managed Disks

Managed Disks

22

2009 2008 IBM Corporation

IBM System StorageTM

SVC FlashCopy Overview

SAN Volume Controller

SAN Volume Controller

LUN 1

LUN 2

LUN 3

LUN 4

LUN 1

LUN 2

LUN 3

LUN 4

LUN 1

LUN 2

LUN 3

LUN 4

LUN 1

LUN 2

LUN 3

DS8K

EMC

XIV

HDS

SAN FlashCopy outside the box

23

Cannot FlashCopy across SVC clusters

2009 2008 IBM Corporation

LUN 4

IBM System StorageTM

SVC FlashCopy Overview

SAN Volume Controller

LUN 1

LUN 2

LUN 3

LUN 1

LUN 2

LUN 3

LUN 4

LUN 1

LUN 2

LUN 3

DS8K

EMC

LUN 4

XIV

Cross-device consistency groups

LUN 4

24

2009 2008 IBM Corporation

IBM System StorageTM

SVC FlashCopy Overview

Source volume may be spread across multiple disk subsystems

Target volume may be to one or more disk subsystems, different than the source

Create up to 256 copies of a source volume

Support for full, incremental, cascaded, space-efficient and nocopy mappings Copy is accessible almost immediately Copy may be updated independently of the source Background Copy Rate establishes copy rate goal Value of 0 has a "No Copy" effect Data rate 128 KB/s to 64 MB/s per vDisk Support for 128 Consistency Groups Up to 4096 Source/Target volume relationships Invoked via Web User Interface, CLI or scripts Licensed independently of base virtualization software and Metro/Global Mirror

Priced per TB for source VDisks only

25

2009 2008 IBM Corporation

IBM System StorageTM

Common Platform for Advanced Functions

Single point for copy services
Asynchronous remote copy/Global Mirror

Use to meet business needs

Disaster recovery up to 10,000KM

Synchronous remote copy/Metro Mirror

Point-in-time copy/FlashCopy

Disaster recovery less then 300KM

LAN/Server free backup, DB clones

Data Migration

Tiered storage, disk replacement

Storage Network
Virtual LUNs Virtual LUNs Virtual LUNs Virtual LUNs Virtual LUNs Virtual LUNs VISC VISC VISC VISC VISC VISC VISC VISC VISC VISC VISC VISC

Storage Network
Virtual LUNs Virtual LUNs VISC VISC VISC VISC

Managed Disks

Managed Disks

26

2009 2008 IBM Corporation

IBM System StorageTM

Data Migration Existing Environment

Evolutionary steps Install SAN Volume Controller Stop host I/O to LUNs chosen for migration

Update HBA BIOS/Firmware and change multipath drivers as needed

BlockBlock virtualization virtualization

Map existing LUNs to SVC using Image mode Reassign Image mode VDisks from SVC to host Restart applications No data movement required Arrays now managed as a virtualized pool Data moved, striped, rebalanced Application servers unaware of physical changes Evolve rest of the SAN in the same manner At already planned downtime

SAN

Array 1 Array 2 Array 3 Array 4

27

As fast or slow as needed Future changes under SVC now transparent

2009 2008 IBM Corporation

IBM System StorageTM

Non-virtualized: Existing Data Unchanged But Under SVC

Image Mode VDisk
BLUDATA 16 GB
Extent 5a Extent 5b

Image Mode MDisk Is EMC LUN with Existing Data

BLUDATA 16 GB

Extent 5c Extent 5d
Extent 5e Extent 5f Extent 5g

Partial extent

ImageMode_MDG

BLUDATA 16 GB

Image Mode MDisk

28

2009 2008 IBM Corporation

IBM System StorageTM

Virtualized: Existing Data Migrated And Now Native To SVC

Image Mode VDisk
BLUDATA 16 GB
Extent 1a Extent 1b

Image Mode MDisk Is EMC LUN with Existing Data

BLUDATA 16 GB

Extent 5c 1c Extent 1d
Extent 1e Extent 1f Extent 1g

Partial extent

BlueData_MDG
BLUDATA2 4 GB BLUDATA1
4 GB Extent 1a Extent 2a Extent 5c 3a Extent 4a Extent 1b Extent 2b Extent 3b Extent 4b

Migrate extents
Migrate

BLUDATA3 4 GB

Virtualized

BLUDATA 16 GB

BLUDATA4 4 GB

Striped VDisk
29

Managed Mode MDisks From Any Supported Subsystem (i.e. HDS-IBM)

2009 2008 IBM Corporation

IBM System StorageTM

Non-virtualized: Migrate Virtualized Data Back To Remove SVC

Image Mode VDisk
BLUDATA 16 GB
Extent 1a Extent 1b

Image Mode MDisk Is EMC LUN with Existing Data again

BLUDATA 16 GB

Extent 5c 1c Extent 1d
Extent 1e Extent 1f Extent 1g

Partial extent

BlueData_MDG
BLUDATA2 4 GB BLUDATA1
4 GB Extent 1a Extent 2a Extent 5c 3a Extent 4a Extent 1b Extent 2b Extent 3b Extent 4b

Migrate extents
Migrate

BLUDATA3 4 GB

Virtualized

BLUDATA 16 GB

BLUDATA4 4 GB

Striped VDisk
30

Managed Mode MDisks From Any Supported Subsystem

2009 2008 IBM Corporation

IBM System StorageTM

Migrate extents
Server1
Application Access

Virtual Disk

Segregating data access from storage infrastructure management

MDiskGroupB MDiskGroupA

MDisks

R5

R5

R5

R5

R5

R5

Migrate VDisk
SCSI LUNs
R5 LUN R1 LUN R5 LUN R5 LUN R5 LUN R5 LUN

Disk Drives Migration

RAID Controller

RAID Controller

73 GB Drives
31

300 GB Drives
2009 2008 IBM Corporation

IBM System StorageTM

Migrate extents
Server1
Application Access

Virtual Disk

Segregating data access from storage infrastructure management

MDiskGroupB MDiskGroupA

MDisks

R5

R5

R5

R5

R5

R5

Migrate VDisk
SCSI LUNs
R5 LUN R1 LUN R5 LUN R5 LUN R5 LUN R5 LUN

Decommission
RAID Controller

Storage Subsystem Migration

RAID Controller

Storage SubsystemA
32

Storage SubsystemB
2009 2008 IBM Corporation

IBM System StorageTM

Extent 1a Extent 2a Extent 3a Extent 1b Extent 2b Extent 3b Extent 1c Extent 2c Extent 3c

Migrate extents

Extent 1a Extent 2a Extent 1f Extent 1b

Virtual Disk

Extent 2b Extent 2g Extent 1c Extent 2c Extent 1e

Managed Disk Group

Extent 1a Extent 1b
Extent 1c

Extent 2a Extent 2b
Extent 2c

Extent 3a Extent 3b
Extent 3c

Extent 1d Extent 1e
Extent 1f

Extent 2d
Extent 2e

Extent 3d Extent 3e
Extent 3f

Remove Redeploy

Extent 2f

Extent 1g

Extent 2g

Extent 3g

Managed Disks
33

2009 2008 IBM Corporation

IBM System StorageTM

New Core Functions in SVC

Space-Efficient VDisk - SEV
Used to implement thin provisioning/overallocation

SCSI Front-end Remote Copy Cache FlashCopy VDM SEV Virtualization SCSI Back-end
2009 IBM Corporation

Used to implement Space-Efficient FlashCopy

No real change to FlashCopy itself

VDisk Mirroring - VDM

Allows creation of a single VDisk with pointers to two sets of MDisk extents Copies can be in different MDGs on different disk controllers

Implemented as independent components between

FlashCopy and Virtualization in the SVC I/O stack
Below Cache for best performance SEV below FlashCopy to allow Space-Efficient FC

VDM above SEV to allow different structures per copy

VDM and SEV included in base SVC license

34

IBM System StorageTM

SEV Conceptual View

Users can create VDisks that have different Real and Virtual Capacities
Real Capacity defines how much disk space is actually allocated to a VDisk

Virtual Capacity defines how large the VDisk appears to the host

A directory maps the virtual address space to the real address space
Implemented as a B-Tree and stored on backend disk Directory and User data share the Real Capacity

Space-Efficient VDisk
Host Server Virtual Capacity Directory Real Capacity Managed Disk Group Controller

35

2009 IBM Corporation

IBM System StorageTM

SEV Virtual and Real Capacity

Specify Virtual and Real Capacities at VDisk creation VDisk appears to have Virtual Capacity to hosts VDisk is allocated enough extents to make up the Real Capacity

Virtual LBA 0

Virtual Capacity 2GB Virtual LBA Max

Real Capacity 1GB Real LBA 0

36

Real LBA Max

2009 IBM Corporation

IBM System StorageTM

SEV Used and Free Capacity

Host writes I/Os to the VDisk at any LBA which increases the Used
Capacity of the Space-Efficient VDisk

Allocation Unit for Real Capacity is called Grain Size: 32 KB, 64 KB, 128
KB or 256 KB. When writing to grain unused space formatted with zeros

SVC consumes <1% of the Used Capacity to store metadata describing

the Virtual-to-Real mapping
Virtual Capacity 2GB

Real Capacity 1GB Used Capacity 200MB Free Capacity 800MB

37

2009 IBM Corporation

IBM System StorageTM

SEV Managing Unused Capacity

If the Used Capacity reaches the Real Capacity then the VDisk will go
offline and application I/Os will fail

User must provision more storage to expand the Real Capacity to get
the VDisk back online

SVC helps you to avoid exhausting the Real Capacity allowing for alerts
to be sent to admins to provide space or by increasing Real Capacity automatically
Virtual Capacity 2GB Used Capacity 600MB Real Capacity 1GB Warning Capacity 800MB
38

2009 IBM Corporation

IBM System StorageTM

VDisk Mirroring (VDM)

VDM allows creation of VDisk with two copies of
MDisk extents
Copies can be in different MDisk groups Copies can be of completely different structures
Image, striped, sequential, space-efficient VDisk

Minimal impact to VDisk availability if one set of MDisks (a disk array) goes offline
Automatic incremental resync

SAN Volume Controller

SAN
MDisk copy 2

VDM sits below the cache and copy services

FlashCopy, Metro Mirror, Global Mirror have no awareness that a VDisk is mirrored
Anything that can be done today with a VDisk can be done with a mirrored VDisk including migration, expand/shrink, etc.

View to list VDisks affected by disk controller shutdown/failure

Allows user to verify that all mirrored VDisks will remain accessible if a controller is taken offline planned or unplanned Lists any VDisks that will go offline due to disk controller shutdown/failure
svcinfo lscontrollerdependentvdisks
39

2009 IBM Corporation

IBM System StorageTM

VDM Using For Migration

Migrate VDisk between MDisk Groups with different extent sizes
Add a copy in the new MDisk Group Wait for synchronization to complete Remove copy in original MDisk Group

Migrate from space-efficient to fully-allocated VDisk Migrate from image/striped/sequential mode to a sequential VDisk Can control copy rate of migration and even suspend/cancel migration
Same controls as FlashCopy Default copy rate setting is 50 which is 2MB/s

Can control how extents are ordered/striped

If laid out originally so all VDisks start on different MDisk can preserve this configuration If issue is all start on same MDisk you can change on second copy

Can split off a copy and create a new independent VDisk

40

2009 IBM Corporation

IBM System StorageTM

SAN Volume Controller Version 4.3.1

Supported Environments
IBM z/VSE
Novell NetWare

VMware SRM

Microsoft Windows Hyper-V

IBM AIX i5 V6R1 via VIOS

Sun Solaris

HP-UX 11i Tru64 OpenVMS

Linux

SGI

(Intel/Power/zLinux) RHEL Apple IRIX SUSE Mac OS

IBM N series Gateway NetApp V-Series IBM TS7650G

IBM BladeCenter

1024 Hosts

New

New
iSCSI to hosts Via Cisco IPS

New New

Point-in-time Copy Full volume, Copy on write 256 targets, Incremental, Cascaded Space-Efficient
Entry Edition software

SAN with 4/8Gbps fabrics

Continuous Copy Metro Mirror Global Mirror

SAN

New

SAN Volume Controller

Space-Efficient Virtual Disks

SAN Volume Controller

New
IBM ESS, FAStT IBM DS
DS3K/4K DS5000 DS6000 DS8000

New
IBM IBM XIV N series

New

Virtual Disk Mirroring

HP Hitachi EMC Sun NetApp MA, EMA Lightning CLARiiON StorageTek FAS MSA, EVA 4400 Thunder Symmetrix TagmaStore XP 24000/20000 AMS, WMS, USP

NEC Fujitsu Pillar Bull iStorage Eternus Axiom StoreWay 300, 500

For the most current, and more detailed, information please visit ibm.com/storage/svc and click on Interoperability.

41

2009 IBM Corporation

IBM System StorageTM

What Makes SVC Special?

Scalable

Performance

Buy nodes if you need performance Buy disk if you need capacity
Simplified

Management Efficient Storage Utilization

Tiered Storage Thin Provisioned Volumes VDisk Mirroring
Exploits
VD 1 VD 2 VD 3 VD 4 VD 6 MD 6 MD 5

Virtual Disks Managed Disk Groups Managed Disks

LUN 2
LUN 1

Virtual-to-physical Mapping

heterogeneous environment

High Perf Low Cost

MD 2
MD 3 MD 1 MD 4 MD 7 LUN 1 MD 8 LUN 2 LUN 3 LUN 4

LUN 3

SCSI LUNs

Non-disruptive

SVC HW/SW upgrades Non-disruptive data migration between heterogeneous devices

Easy technology refreshes Easy tiering of data
Free

LUN 4

Copy services between dissimilar storage systems Eliminates Copy Services licenses on each disk subsystems

VD 5

IBM

multi-path driver support

2009 2008 IBM Corporation

SDD
42

VD 7

EMC

IBM System StorageTM

Reference Materials
Websites for marketing and support information
http://www.ibm.com/storage/software/virtualization

http://www.ibm.com/storage/support/2145

Publications
http://www.ibm.com/shop/publications/order Planning Guide GA32-0551

Hardware Installation Guide GC27-2132

Software Installation/Configuration Guide SC23-6628 Host Attachment Guide SC26-7905 Service Guide SC26-7901 Command-Line Interface Users Guide SC26-7903

Redbooks
http://www.ibm.com/redbooks
Search on SAN Volume Controller
43

2009 IBM Corporation

IBM System StorageTM

Question and Answer Time

innovation that matters

44

2009 IBM Corporation

IBM System StorageTM

Disclaimers
Copyright 2006 by International Business Machines Corporation. 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 information
could include technical inaccuracies or typographical errors. IBM may make improvements and/or changes in the product(s) and/or programs(s) at any time without notice.

Unless otherwise note, the performance data contained herein was obtained in a controlled, isolated environment. Actual results that may be

obtained in other operating environments may vary significantly. While IBM has reviewed each item for accuracy in a specific situation, there is no guarantee that the same or similar results will be obtained elsewhere. Other data may have been obtained from publicly available documents or sources. In such cases, IBM has endeavored to provide comparable measurements for systems being compared.

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 IBMs intellectually property rights, may be used instead. It is the users responsibility to evaluate and verify the operation of any non -IBM product, program or service.

The information provided in this document is distributed "AS IS" without any warranty, either express or implied. IBM EXPRESSLY 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 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. IBM is not responsible for the performance or interoperability of any non-IBM products discussed herein.

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. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. Inquiries regarding patent or copyright licenses should be made, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. 45

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.

2009 IBM Corporation

IBM System StorageTM

Trademarks
The following terms are trademarks or registered trademarks of the IBM Corporation in either the United States, other countries or both.

IBM, S/390, ES/3090, ES/9000, AS/400, RS/6000, MVS/ESA, OS/390, VM/ESA, VSE, TPF, OS/2, OS/400,
AIX,, FlashCopy, z/VM, z/OS, POWER5, POWER5+, DB2, Universal Database

DFSMS/MVS, DFSMS/VM, , DFSMSdfp, DFSMSdss, DFSMShsm, DFSMSrmm, BladeCenter, FICON, ESCON, TotalStorage, Enterprise Storage Server, iSeries, pSeries, xSeries, zSeries, System z,
System z9, System i, System i5, System p, System p5, System x, System Storage Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others.
46

2009 IBM Corporation