View
156
Download
6
Category
Tags:
Preview:
DESCRIPTION
IBM® Edge2013 - Introduction to SVC and Storwize V7000
Citation preview
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000: Virtualization, Compression and Business Continuity
Jack Arnold - IT Management Consultant
29 May 2013
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
2
SVC Purpose
� Combine disk subsystems into a single reservoir of capacity
� Manage from a single interface
� Insulate applications from storage changes
� Enable tiered storage
� Provide replication within and between storage subsystems
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
3
SVC - Logical View
Server
SAN
IBM EMC HDS
Server
SAN
IBM EMC HDS
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
4
SVC - Logical View
To the server, it looks like a storage controller
To the storage controllers, it looks like a server!
Server
SAN
IBM EMC HDS
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
5
SVC - Physical View and Zoning
Server
SAN
IBM EMC HDSSVC
The SVC is attached and zoned into the SAN
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
6
SAN
Multipathing Drivers� Only one device driver
–Multipathing, failover/failback, load-balancing
–Server only sees SVC
–Adding a new storage system requires no additional maintenance to servers
� Choice is yours, per server
–IBM SDD (System Device Driver)
–MPIO (Window, AIX)
–MPxIO (Solaris)
–PVLinks (HP-UX)
–DM-MP (Linux)
–Symantec DMP
SAN
Volume Controller
VirtualDisk
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
SVC Node History
7
http://en.wikipedia.org/wiki/IBM_SAN_Volume_Controller#Terminology (updated 21 May
2013 by Jack G. Arnold)
Type-model Cache [GB]FC speed
[Gb/s]
iSCSI
Speed
[Gb/s]
Based upon Announced
2145-4F2 4 2 n/a x335 2 June 2003
2145-8F2 8 2 1 x336 25 October 2005
2145-8F4 8 4 1 x336 23 May 2006
2145-8G4 8 4 1 x3550 22 May 2007
2145-8A4 8 4 1 x3250 28 October 2008
2145-CF8 24 8 1 x3550M2 20 October 2009
2145-CG8 24 8
1 (10
Gbit/s
optional)
x3550M3 9 May 2011
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
8
20032145-4F24 node
1.1 1.2 2.1 3.1 4.1 4.2 4.3 5.1 6.1
SVC release history is a continuous evolution
6.2
20048 nodes
20042145-8F2VSSGDS
2006
Global Mirror
Multi-target
FlashCopy
2008
Thin provisioning
vDisk Mirroring
SVC Entry Edition
2010Storwize V7000New GUIEasy Tier
20052145-8F4
2007
2145-8G4
FlashCopy
enhancements
2009
2145-CF8
SSD support
3 site Mirror
> 2TB VDisk
Split cluster
iSCSI
Zero detect
2011
2145-CG8
VAAI
>2 TB MDisk
Performance
monitor
Flash Copy
enhancements
6.2 6.4
2012
Real-time
Compression
Non-disruptive
volume move
FCoE
4 way Storwize
V7000 clustering
6.3
2011
Storwize V7000
Unified
Mixed Replication
Longer distance
split cluster
Native LDAP
New Global Mirror
option
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
9
Migration to a SAN Volume ControllerCurrent Image Mode Virtualized
A B C
MDG1
AB
MDG2
C
MDG1
A
MDG2
B
C C
Va Vb Vc Va Vb Vc
Non-Disruptive
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
10
SAN SAN
SAN Volume Controller
Improved Application Availability
Traditional SAN1. Stop the application
2. Move data
3. Re-establish host connections
4. Restart application
SAN Volume Controller1. Move data
2. Host systems and applications are not affected.
Volume
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
11
SAN SAN
SAN Volume Controller
Improved Application Availability
Traditional SAN1. Stop the application
2. Move data
3. Re-establish host connections
4. Restart application
SAN Volume Controller1. Move data
2. Host systems and applications are not affected.
Volume
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
12
Replication Services
Traditional SAN
� Replication API’s differ by vendor
� Lower-cost disks offer primitive, or no replication services
SAN Volume Controller
� Common replication API, SAN-wide, that does not change as storage hardware changes
� Replication targets can be on lower-cost disks
SAN SAN
SAN Volume Controller
IBM
ESSIBM
ESS
EMC
Sym
EMC
Sym
FlashCopy
PPRC
TimeFinder
SRDF
IBM
ESSIBMSATA
EMC
Sym
HP
MA
SVC
IBMDS4000
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
13
Remote Copy
MDG1
MDG2
Source
MDG3
MDG4
Destination
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
14
IBM SAN Volume Controller - FlashCopy
Up to 256 targets
Source vdisk
FlashCopy relationships
FlashCopy:Volume level point-in-time copywith any mix of SEVand fully-allocated
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
15
IBM SAN Volume Controller - FlashCopy
Start incremental FlashCopy
Data copied as normal
Some data changed by apps
Start incremental FlashCopy
Only changed data copiedby background copy
Later …
Incremental FlashCopy:Volume level
point-in-time copy
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
16
IBM SAN Volume Controller - FlashCopy
Disk0Source
Map 1 Map 2
Map 4
Disk1FlashCopy
target of Disk0
Disk2FlashCopytarget of Disk1
Disk4FlashCopytarget of Disk3
Disk3FlashCopy
target of Disk1
Cascaded FlashCopy:Copy the copies
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
17
� SVC maintains a primary and secondary copy
� If primary one copy fails, SVC reads from secondary
– Copies are automatically resynchronized after repair
� Intended to protect critical data against failure of a disk system
� Copies can be split
� Either or both copies may be space-efficient (SEV)
� Reads come from only 1, writes go to both
Virtual Disk Mirroring
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
18
-mirrorwritepriority latency | redundancy
SVC/V7000 6.3 code release
Return successful completion as soon as one copy has completed
Wait until both copies are written before returning success
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
19
Reclaiming Unused Disk Space
� Reclaim unused allocated disk space (zeros)
when converting a fully allocated VDisk to a
Space-Efficient Virtual Disk (SEV) using VDiskMirroring
� Using Vdisk Mirroring, move from full to SEV
SAN
Volume Controller
data
data
zeros
zeros
data
Reclaimed disk space
fully allocated space-efficient
VDisk
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
20
Scale-Out Implementation
Add SVC I/O Groups to scale throughput and add capacity
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
21
Easy Tier
� Automatic storage hierarchy
–Mixed storage pool with 2 tiers
• Internal or External SSD and spinning disks
� Volumes belong to a single pool
� I/O Monitor keeps access history for each virtualisation extent
–Extent sizes 16MB to 8GB
–Default is 256 MB extent size
SSD HDD
Host Volumes & Extents
Mixed storage pool
Host Host Host
Automatic extent migration
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
22
Stretched Cluster and Remote Replication
Stretched Cluster can be combined with Global Mirror to third location
–Up to 8000 km away
Stretched Cluster does not protect against all unplanned outages
–Regional disasters could affect both data centers
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
2323 This proprietary educational material is intended for IBM and IBM Business Partner staff only.
It is not intended for distribution to customers or other third parties.
SVC 2145-CF8 Storage Engine
� New SVC engine based on IBM System x3550 M2 server (1U)– Intel® Xeon® 5500 (Westmere) 2.40 GHz hex-core processor – 24GB of cache per node– Four 8Gbps FC ports per node
� Solid State Drive support (up to four per SVC node) enabling scale-out high performance SSD support with SVC
� 10 Gb Ethernet support for 10 Gb iSCSI host attachment and future FCoEsupport
– Providing this will require a decision of either SAS-attached SSD or 10 GbE for each node
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
Storwize V7000Announced = 07 OCT 2010Available = 12 NOV 2010
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
Storwize V7000
- Midrange storage controller
- Virtualization from SVC
- Functionality from SVC
- Reports as 2145 (SVC)
- RAID from DS8000 (+ more)
- GUI from XIV
- Classic controller head + expansion drawers
- IBM designed and developed (at Hursley in the U.K.)
- Optional compression from Storwize acquisition
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
Storwize V7000 Overview
Enclosure Front View – 12 Drive Bays2076-112/212/312
Enclosure Front View – 24 Drive Bays2076-124/224/324
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
Scale the Storwize V7000 to Meet Your Needs
� Scale-up
– Add non-disruptively
Exp
and
Cluster
Control EnclosureControl Enclosure
Expansion
Enclosures
� Scale-out
– Cluster up to 4 frames and 40 enclosures
– Add non-disruptively
Expansion
Enclosures
Expansion
Enclosures
Expansion
Enclosures
Control Enclosure Control Enclosure
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
User Interface
© 2010 IBM Corporation
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
Storwize V7000 Unified
V7000 Unified
V7000 Unified
Single four Core Intel® Xeon E5620 at 2.4GHz(12MB L3 cache, 80W)
1 x Intel Jasper Forest quad core 64-bit CPU (2.1GHz) per controller(8MB L3 cache, 65W)
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
Storwize V7000 Unified
� Unified block and files storage system
–Tightly integrated management console
–NFS / CIFS / FTP / HTTPS / SCP in addition to block functions
� IBM Active Cloud Engine™
–File based ILM
–File based asynchronous replication
–File based snapshots
–Quotas
V7000
Unified
V7000 Unified
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
Status Indicators
ExtensiveHelp
Intuitive Function IconsSimplify Storage Management
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
Connecting Storwize V7000 Unified
IBM Storwize V7000 File module (2U)
IBM Storwize V7000 File module (2U)
IBM Storwize V7000
2 x 8 GbFibre Channel
2 x 8 Gb Fibre Channel
4 x 8 Gb Fibre Channel
SAN
4 x 10 Gb Ethernet
4 x 1 Gb Ethernet
2 x 1 Gb Ethernet
2 x 10 Gb Ethernet
2 x 1 Gb Ethernet
iSCSI
iSCSI,MGMT
NFS, CIFS, FTP, HTTP, SCP, management
6 Gb/s SAS toexpansion trays
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
File Placement
� Rule 'Data rule 1' set pool 'tier1' where UPPER(NAME) like '%.DOC'
� Rule 'Data rule 2' set pool 'tier2' where UPPER(NAME) like '%.PPT'
� Rule 'Data rule 3' set pool 'tier3' where UPPER(NAME) like '%.MP3'
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
File Management
RULE 'mig1' MIGRATE FROM POOL 'pool_1' THRESHOLD(90,70) WEIGHT(KB_ALLOCATED) TO POOL 'pool_2'
RULE 'del1' DELETE FROM POOL 'pool_1' WHERE (DAYS(CURRENT_TIMESTAMP) - DAYS(ACCESS_TIME) > 30) AND (lower(NAME) LIKE '%.tmp' OR PATH_NAME LIKE '%/tmp/%')
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
IBM Active Cloud Engine with TSM
� Migrating data to TSM could place it on lower cost tape
� Leaves stub behind
TSM
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
Dedicated CPU Resources, V7000 and SVC CF8
Create first compressed volume
Delete last compressed volume
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
Dedicated CPU Resources, SVC CG8
Create first compressed volume
Delete last compressed volume
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
Dedicated Cache Resources, SVC CF8, CG8
Create first compressed volume
Delete last compressed volume
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
� All copy services will interoperate with compressed Volumes
� New property introduced
– Uncompressed capacity
Real-time Compression
Clients
Front End
Remote Copy
Cache
Flash Copy
Mirroring
Thin Provisioning
Virtualization
Storage
Back End
Random Access
Compression
Engine™
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
Advantages Compared with other Technologies
� IBM Real-time Compression can be used with active primary data
� IBM Real-time Compression operates immediately and is easy to manage
–No need to schedule periods to run post-process compression
–Eliminates need to reserve space for uncompressed data waiting post-processing
� IBM Real-time Compression supports all Storwize storage
–Internal or externally virtualized storage
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
Expected Compression Rates
� IBM Comprestimator tool should be used to evaluate expected compression benefits in existing environments
Databases 50-80%
Server Virtualization 45-70%
Collaboration Data 30-75%
Engineering Data 50-80%
E-mail 30-60%
© 2013 IBM Corporation
Session 1031 Introduction to SVC and Storwize V7000:
Compression Implementation Guidelines
� Good for compression
–Databases – DB2, Oracle, MS-SQL, etc.
–Applications based on databases – SAP, Oracle Applications, etc.
–Server Virtualization – KVM, VMware, Hyper-V, etc.
–Other compressible workloads – engineering, seismic, collaboration
� Bad for compression
–Workloads using pre-compressed data types such as video, images, audio
–Workloads using encrypted data
–Heavy sequential write oriented workloads
© 2013 IBM Corporation
The End
43
Session 1031 Introduction to SVC and Storwize V7000: Virtualization, Compression and Business Continuity
© 2013 IBM Corporation
For more from Jack:
https://www.ibm.com/developerworks/mydeveloperworks/blogs/IBMStorage
or Google search “IBM blog Jack Arnold”
Recommended