IBM V7000 SAN Storage: Thin Provisioned vs. Fully Allocated

Copyright IBM Corporation 2008
Do You Really Wanna be THIN and/or

is Doubling More Fun?
Sharon P. Wang
Session ID: SVC01
2008 IBM
Corporation
SVC v4.3 highlights (and agenda):
Space-efficient virtual disks (SEVs) and space-efficient FlashCopy
provides thin-provisioning and snapshot functionality
enhances utilization efficiency of physical disk capacity
available to all mDisk groups
available to ALL SVC supported storage subsystems
available at no additional charge with SVC base license
Multi-target FlashCopy - copies increased from 16 to 256
facilitates copy frequency and consumes less storage via SEVs
FlashCopy licensing based on source capacity only
Virtual disk mirroring (VDM) -- two sets of mDisk extents/vDisk
protects against storage subsystem hardware failures
expands data migration flexibility
Number of supported vDisks per I/O group doubles to 2048
SSPC replaces SVC Master Console for SVC Console
Extent 9
Extent 8
Extent 7
Extent 6
Extent 5
Extent 4
Extent 3
Extent 2
Extent 1
Extent 0
Extent 3
Extent 2
Extent 1
Extent 0
LBA0
LBA0
LBAn
LBAn
mDisk Group - example
extent size 512 MB
Host sees two
5 GB LUNs
(LBA0 LBAn)
2 GB
real capacity
Fully allocated vDisk -
entire LBA range
allocated at creation
Space-efficient vDisk -
LBA range allocated in
grain size increments
based on write activity
LBA0
LBAn
Additional real capacity acquired either:
o manually non-autoexpand (default)
o automatically - autoexpand
Fully allocated vs space-efficient vDisks (SEVs)
new parm
Warning threshold
for MDG free space
Virtual
Disk
5 GB
Virtual
Disk
5 GB
Virtual
Disk
LBA0
LBAn
5 GB
Directory (B-tree)
LBA800
LBA530
LBA0
Extents
LBA0-63 LBA768-831 LBA512-575
Write/Read
Activities:
Capacity
(size)
Real
capacity
(rsize=2GB)
Used capacity = sum of all
grains allocated
Free capacity = real capacity
minus used capacity
Space-efficient vDisks concepts & terms
autoexpand
= off*
vDisk goes offline if write
activity exceeds real capacity
Space allocated in grain size increments:
o default grain size = 32K
o grain size can be 32/64/128/256K
Warning threshold defaults to 80% of rsize
(Grain=32K*)
*=default
Virtual
Disk
LBA0
LBAn
5 GB
Directory (B-tree)
LBA1961
LBA0
Extents
LBA0-127 LBA1920-2047
Capacity
(size)
Real
capacity
Used capacity = sum of all
grains allocated
Free capacity = real capacity
minus used capacity
Space-efficient vDisks concepts & terms
Warning threshold defaults to 80% of size
Contingency
capacity
(rsize=2GB)
(Grain=64K)
autoexpand
= on
Write/Read
Activities:
Directory -- used by
read/write requests to
translate LBA#s to
grains within extents
Front End
Metro/Global
Mirror
Fast-write
Cache
FlashCopy
Virtualization
Back End
SVC Node
I
n
t
e
r
n
a
l
C
o
n
f
i
g
u
r
a
t
i
o
n

a
n
d

R
A
S
C
l
u
s
t
e
r

O
p
e
r
a
t
i
n
g

E
n
v
i
r
o
n
m
e
n
t
a
n
d

S
e
r
v
i
c
e
s
M
e
s
s
a
g
e
-
P
a
s
s
i
n
g

L
a
y
e
r
B
u
f
f
e
r

M
a
n
a
g
e
m
e
n
t
,

M
e
m
o
r
y

M
a
n
a
g
e
m
e
n
t
I
n
f
r
a
s
t
r
u
c
t
u
r
e

S
u
p
p
o
r
t
Space-efficient
Metadata directory
stored with vDisk data
on external disk.
Directory in SVC cache
based on vDisk
read/write activity
vDisks
extents
Directory (B-tree)
< 1 % of
vDisk capacity
Node I/O stack
SEV metadata management & SVC I/O stack
IBM_2145:REDCLUSTER:admin>svctask mkmdiskgrp -ext 512 -mdisk 6:7:8:9 -name REDGRP0
-warning 75%
MDisk Group, id [0], successfully created
IBM_2145:REDCLUSTER:admin>svcinfo lsmdiskgrp REDGRP0
id 0
name REDGRP0
status online
mdisk_count 4
vdisk_count 0
capacity 120.0GB
extent_size 512
free_capacity 120.0GB
virtual_capacity 0.00MB
used_capacity 0.00MB
real_capacity 0.00MB
overallocation 0
warning 75
IBM_2145:REDCLUSTER:admin>svctask mkvdisk -mdiskgrp 0 -iogrp 0 -size 5 -unit gb
-name V_FULL
Virtual Disk, id [6], successfully created
IBM_2145:REDCLUSTER:admin>svctask mkvdisk -mdiskgrp 0 -iogrp 0 -size 5 -unit gb
-name V_THIN -rsize 2
Virtual Disk, id [7], successfully created
Example vDisks: V_FULL and V_THIN
mdisk
mdisk
REDGRP0
mdisk
6
8 7
mdisk
9
V
6
V
7
IBM_2145:REDCLUSTER:admin>svcinfo lsmdiskgrp
REDGRP0
id 0
name REDGRP0
status online
mdisk_count 4
vdisk_count 2
capacity 120.0GB
extent_size 512
virtual_capacity 10.00GB
used_capacity 5.00GB
real_capacity 7.00GB
overallocation 8
warning 75
IBM_2145:REDCLUSTER:admin>svcinfo lsvdiskextent 6
id number_extents
6 3
7 2
8 2
9 3
id number_extents
6 1
7 1
8 1
9 1
mDisk group detail and vDisk extents
V
6
V
7
IBM_2145:REDCLUSTER:admin>svcinfo lsvdisk 6
id 6
name V_FULL
IO_group_id 0
IO_group_name IOGROUP0
status online
mdisk_grp_id 0
mdisk_grp_name REDGRP0
capacity 5.0GB
type striped
formatted no
mdisk_id
mdisk_name
FC_id
FC_name
RC_id
RC_name
vdisk_UID 60050768018A80285800000000000047
throttling 0
preferred_node_id 2
fast_write_state empty
cache readwrite
udid
fc_map_count 0
sync_rate 50
copy_count 1
copy_id 0
status online
sync yes
primary yes
mdisk_grp_id 0
type striped
mdisk_id
mdisk_name
free_capacity 0.00MB
overallocation 100
autoexpand
warning
grainsize
V_FULL lsvdisk detail (fully allocated)
V
6
IBM_2145:REDCLUSTER:admin>svcinfo lsvdisk 7
id 7
name V_THIN
IO_group_id 0
status online
mdisk_grp_id 0
capacity 5.0GB
type striped
formatted no
mdisk_id
mdisk_name
FC_id
FC_name
RC_id
RC_name
vdisk_UID 60050768018A8028580000000000004A
throttling 0
preferred_node_id 2
cache readwrite
udid
fc_map_count 0
sync_rate 50
copy_count 1
copy_id 0
status online
sync yes
primary yes
mdisk_grp_id 0
type striped
mdisk_id
mdisk_name
used_capacity 0.41MB
overallocation 250
autoexpand off
warning 31
grainsize 32
V_THIN lsvdisk detail autoexpand = off
(2GBx80%)/5GB=31%
5GB/2GB=250
V
7
GUI - create space-efficient vDisks (1 of 3)
Each grain is formatted
with zeros upon allocation
(Only updated Create VDisks
GUI views shown)
GUI - create space-efficient vDisks (2 of 3)
GUI create space-efficient vDisks (3 of 3)
id number_extents
6 1
7 1
8 2
9 1
V_THINex vDisk detail autoexpand = on
V
8
80% of 5GB
IBM_2145:REDCLUSTER:admin>svcinfo lsmdiskgrp 0
id 0
name REDGRP0
status online
mdisk_count 4
vdisk_count 3
capacity 120.0GB
extent_size 512
overallocation 12
warning 75
vDisks and mDisk group detail
(15GB/120GB)x100=12%
(virtual capacity/capacity)x100
Host view of these three 5 GB vDisks
SDD
vDisk UID
Host view after write activity on SEVs
vDisk capacity detail after write activity
5120MB x 31% = 1587MB
1843MB > 1587MB
Warning threshold exceeded
V
8
V
7
V_THIN capacity warning threshold - 986020
svctask chvdisk autoexpand
and/or
svctask expandvdisksize rsize
Notification options:
SVC log
SNMP trap
email
V
7
To do:
Host view write activity exceeds SEV capacity
V
7
V_THIN vDisk offline due to capacity depletion
V
7
Run Maintenance Procedure - error code 1865
V
7
Maintenance procedure and error log entries
IBM_2145:REDCLUSTER:admin>svctask chvdisk -autoexpand on V_THIN
IBM_2145:REDCLUSTER:admin>svcinfo lssevdiskcopy -delim , 7
vdisk_id,vdisk_name,copy_id,mdisk_grp_id,mdisk_grp_name,capacity,used_capacity,real_capacity,
free_capacity,overallocation,autoexpand,warning,grainsize
7,V_THIN,0,0,REDGRP0,5.0GB,2.00GB,2.00GB,0.06MB,250,on,31,32
IBM_2145:REDCLUSTER:admin>
vDisk V_THIN online after autoexpand = on
V
7
Error automatically marked as fixed
V_THIN detail after chvdisk autoexpand = on
V
7
SEVs require more I/Os because of directory accesses:
A SEV will require approximately one directory I/O for every user I/O - thus
performance may potentially be 50% of a fully allocated vDisk
SVC cache should mitigate this as B-tree directory will generally be in cache
SEV read I/O - about 1.25 times longer, e.g. 12-13 ms versus 10 ms
SEV write I/O about 1.5 times longer, e.g. 4-5 ms versus 3 ms
SEV requires more CPU processing so overall IOPS & MBPS may be lower
70/30 R/W workload likely to be about 85% of overall IOPS & MBPS capacity of fully
allocated
100% write I/O to I/O group with all SEVs approximates 50% of capacity versus fully
allocated
Avoid using SEVs where high performance is required
Avoid using SEVs if OS or application writes to entire LBA range
Use striping to spread SEVs across many spindles
Do not use SEVs to reduce the number of physical disks required - likely cause
performance issues
SEV performance and when to use
SEV interaction with other SVC functions
Virtualization
SEVs can be created using striped, sequential, or image
virtualization type as with any vDisk
Data
Migration
SEVs can be migrated as with any vDisk
vDisk Resize
Virtual capacity as well as real capacity can be resized via
expandvdisksize -- -size and -rsize
vDisk
Mirroring
(VDM)
Each copy of a mirrored vDisk can be space-efficient or fully
allocated.
VDM can be used to perform a non-disruptive migrations:
from space-efficient to fully allocated
from fully allocated to space-efficient (to take advantage of
space efficiency ensuing future size expansion)
Metro Mirror
and Global
Mirror
Viable if relationships are created without the initial synchronization
(e.g., both primary and secondary are initially already identical)
Not viable if a full resynchronization is required secondary
becomes fully allocated (e.g., existing mirror relationships).
Avoid using SEVs with GM potential performance issues due to
overhead to allocate space, format, then write the mirrored data.
May potentially back up processing at primary site causing GM to
suspend relationship(s)
FlashCopy v4.3 enhancements:
Space-efficient FlashCopy (SEFC)
256 targets per source (versus 16 targets)
Licensing based on source capacity only
FlashCopy and SEVs SEFC Support
Source Target
SEV SEV
Full SEV
SEV Full copyrate = 0
Use VDM
Note: FC bitmap space is based on virtual capacity
OK
OK
OK
Host view before FC two SEVs
V_THINex
V_THIN
5 GB
5 GB
Capacity detail before FlashCopy two SEVs
V_THIN
V_THINex
5 GB
5 GB
Perform FlashCopy: V_THINex to V_THIN
IBM_2145:REDCLUSTER:admin>svctask mkfcmap -source V_THINex -target
V_THIN -name FC_SEVs -copyrate 100
FlashCopy Mapping, id [3], successfully created
IBM_2145:REDCLUSTER:admin>svctask startfcmap -prep FC_SEVs
IBM_2145:REDCLUSTER:admin>svcinfo lsfcmap -delim , -filtervalue
name=FC_*
id,name,source_vdisk_id,source_vdisk_name,target_vdisk_id,target_vdisk_name,
group_id,group_name,status,progress,copy_rate,clean_progress,incremental
3,FC_SEVs,8,V_THINex,7,V_THIN,,,copying,57,100,100,off
name=FC_*
3,FC_SEVs,8,V_THINex,7,V_THIN,,,idle_or_copied,100,100,100,off
V_THINex V_THIN
5 GB 5 GB
Host view after FC two SEVs
V_THINex
V_THIN
5 GB
5 GB
Capacity detail after FC two SEVs
V_THINex
5 GB
V_THIN
5 GB
Host view before FC - full to SEV copyrate=0
V_FULL
5 GB
V_THIN
5 GB
Another example:
IBM_2145:REDCLUSTER:admin>svctask rmfcmap 3
IBM_2145:REDCLUSTER:admin>svctask mkfcmap -source V_FULL -target
V_THIN -name FC_F2SEV -copyrate 0 -grainsize 64
FlashCopy Mapping, id [3], successfully created
IBM_2145:REDCLUSTER:admin>svctask startfcmap -prep FC_F2SEV
IBM_2145:REDCLUSTER:admin>svcinfo lsfcmap 3
id 3
name FC_F2SEV
source_vdisk_id 6
source_vdisk_name V_FULL
target_vdisk_id 7
target_vdisk_name V_THIN
group_id
group_name
status copying
progress 0
copy_rate 0
start_time 080725174540
dependent_mappings 0
autodelete off
clean_progress 100
clean_rate 50
incremental off
difference 100
grain_size 64
IO_group_id 0
Perform FlashCopy: V_FULL to V_THIN
V_THIN
5 GB
V_FULL
5 GB
Only contains
copy-on-write blocks
copyrate=0
snapshot
Host view of FC full to SEV with copyrate 0
current data
on source vDisk
V_FULL
5 GB
V_THIN
5 GB
PiT data view
on target vDisk
Capacity detail of vDisks during FlashCopy
name=FC_F*
3,FC_F2SEV,6,V_FULL,7,V_THIN,,,copying,0,0,100,off
V_FULL
5 GB
V_THIN
5 GB
IBM_2145:REDCLUSTER:admin>svctask stopfcmap FC_F2SEV
IBM_2145:REDCLUSTER:admin>svcinfo lsfcmap -delim , -filtervalue name=FC_F*
id,name,source_vdisk_id,source_vdisk_name,target_vdisk_id,target_vdisk_name,group_id
,group_name,status,progress,copy_rate,clean_progress,incremental
3,FC_F2SEV,6,V_FULL,7,V_THIN,,,stopped,0,0,100,off
V_THIN
5 GB
Unable to access V_THIN after stopfcmap
?
?
Disk 3
No longer has access
to data on source
V_THIN
5 GB
V_THIN offline (fcmapstop & FC copyrate 0)
?
IBM_2145:REDCLUSTER:admin>svctask startfcmap -prep FC_F2SEV
IBM_2145:REDCLUSTER:admin>svcinfo lsfcmap -delim , -filtervalue name=FC_F*
id,name,source_vdisk_id,source_vdisk_name,target_vdisk_id,target_vdisk_name,group_id
,group_name,status,progress,copy_rate,clean_progress,incremental
3,FC_F2SEV,6,V_FULL,7,V_THIN,,,copying,0,0,100,off
Host view after FC restart and copyrate 0
V_THIN
5 GB
V_THIN online (fcmapstart & FC Copyrate 0)
V_THIN
5 GB
Mixture of FC targets for disaster/data corruption recovery:
Fully allocated source with:
Fully allocated target - refreshed daily
SEV targets with nocopy snapshots created hourly
Fully allocated target available for disaster recovery
SEV targets facilitates data corruption recovery
An hourly SEV target can cascade as source to
create fully allocated target for RPO and RTO
target
daily
target
hour1
target
hour3
target
hour2
FULL/IFC
SEV
SEV
SEV
Procedure:
1) Create nightly target - full copy with incremental on
2) Start hour1 SEV targets with copyrate=0 snapshot
3) Start hour 2 SEV target with copyrate=0, and so on
4) Repeat at end of day by:
a) Stop started hourly FC maps in chronological order
b) Go back to step 1)
source
SEFC more targets and using less storage
FULL/IFC full copy with incremental turned on
Extent 9
Extent 8
Extent 7
Extent 6
Extent 5
Extent 4
Extent 3
Extent 2
Extent 1
extent size
512 MB
Host sees ONE
5 GB LUN
(LBA0 LBAn)
vDisk Mirroring (VDM) two sets of extents
Extent 4
Extent 3
Extent 2
Extent 1
Extent 0
extent size
1024 MB
Extent 0
Copy 0
Copy 1
MDG
1
MDG
2
Copy created by:
o mvdisk
o addvdiskcopy
Virtual
Disk
5 GB
Copy has its own:
o mDisk group
o virtualization type
o fully allocated or SEV
Front End
Metro/Global
Mirror
Fast-write
Cache
FlashCopy
Virtualization
Back End
SVC Node I/O Stack
Space-efficient
vDisk Mirroring
MDG
1
MDG
2
Promotes high availability at local site
Expands data migration flexibility
Enables conversions SEV to fully allocated
Full to SEV if expandvdisksize planned
Virtual
Disk
extent s extent s
vDisk Mirroring (VDM) & SVC I/O processing
Pr i mar y c opy
Read/Write requests
reads
writes
writes
Oblivious
to VDM
Copy
Service
Grain Size
(KB)
1 MB
bitmap
space
20 MB
bitmap
space
512 MB
bitmap
space
FC 256
2 TB
target vDisk
capacity
40 TB
target vDisk
capacity
1024 TB
target vDisk
capacity
FC 64
512 GB
target vDisk
capacity
10 TB
target vDisk
capacity
256 TB
target vDisk
capacity
IFC 256
1 TB
target vDiks
capacity
20 TB
target vDisk
capacity
512 TB
target vDisk
capacity
IFC 64
256 GB
target vDisk
capacity
5 TB
target vDisk
capacity
128 TB
target vDisk
capacity
MM/GM 256
2 TB
vDisk
capacity
40 TB
vDisk
capacity
1024 TB
vDisk
capacity
FC=FlashCopy IFC=Incremental FlashCopy MM=Metro Mirror GM=Global Mirror VDM=vDisk Mirroring
Bitmap space and copy capacity (per iogroup)
VDM 256
2 TB
vDisk
capacity
40 TB
vDisk
capacity
1024 TB
vDisk
capacity
IBM_2145:REDCLUSTER:admin>svcinfo lsiogrp IOGROUP0
id 0
name IOGROUP0
node_count 2
vdisk_count 17
host_count 5
flash_copy_total_memory 20.0MB
flash_copy_free_memory 19.9MB
remote_copy_total_memory 20.0MB
remote_copy_free_memory 20.0MB
mirroring_total_memory 0.0MB
mirroring_free_memory 0.0MB
IBM_2145:REDCLUSTER:admin>svctask chiogrp
-feature mirror -size 10 IOGROUP0
IBM_2145:REDCLUSTER:admin>svcinfo lsiogrp 0
id 0
name IOGROUP0
node_count 2
vdisk_count 17
host_count 5
flash_copy_total_memory 20.0MB
flash_copy_free_memory 19.9MB
remote_copy_total_memory 20.0MB
remote_copy_free_memory 20.0MB
mirroring_total_memory 10.0MB
mirroring_free_memory 10.0MB
Allowing VDM set mirror bitmap space
Default = no VDM
20 TB VDM
capacity
SEV Overallocation indicator example
V
8
5120MB/3896MB x 100 = 131
Consider convert SEV to
fully allocated
SEV Overallocation capacity growth rate
V
8
5120MB/5133MB x 100 = 99
SEV size > fully allocated
Convert to fully allocated
SEV allocated capacity - not related to deletes
V
8
VDM addvdiskcopy to V_THINex example
IBM_2145:REDCLUSTER:admin>svctask addvdiskcopy -mdiskgrp 4 -syncrate 60 8
Vdisk [8] copy [1] successfully created
IBM_2145:REDCLUSTER:admin>svcinfo lsvdiskcopy -delim , 8
vdisk_id,vdisk_name,copy_id,status,sync,primary,mdisk_grp_id,mdisk_grp_name,capacity,type
8,V_THINex,0,online,yes,yes,0,REDGRP0,5.0GB,striped
8,V_THINex,1,online,no,no,4,REDGRP6K,5.0GB,striped
IBM_2145:REDCLUSTER:admin>svcinfo lsvdisksyncprogress -delim , 8
vdisk_id,vdisk_name,copy_id,progress,estimated_completion_time
8,V_THINex,0,100
8,V_THINex,1,8,080807232413
IBM_2145:REDCLUSTER:admin>svctask chvdisk -syncrate 100 8
IBM_2145:REDCLUSTER:admin>svcinfo lsvdisksyncprogress -delim ,
vdisk_id,vdisk_name,copy_id,progress,estimated_completion_time
8,V_THINex,1,26,080807230759
IBM_2145:REDCLUSTER:admin>svcinfo lsvdisksyncprogress -delim ,
8,V_THINex,0,online,yes,yes,0,REDGRP0,5.0GB,striped
8,V_THINex,1,online,yes,no,4,REDGRP6K,5.0GB,striped
MDG
1
MDG
2
V
8
Availability
Migration
Conversion
V
8
vDisk copy added for V_THINex
REDGRP6K
write
REDGRP0
read/write
\IBM_2145:REDCLUSTER:admin>svcinfo lsmdiskgrp REDGRP0
id 0
name REDGRP0
status online
mdisk_count 4
vdisk_count 10
capacity 120.0GB
extent_size 512
overallocation 60
warning 75
IBM_2145:REDCLUSTER:admin>svcinfo lsmdiskgrp REDGRP6K
id 4
name REDGRP6K
status online
mdisk_count 10
vdisk_count 2
capacity 10.0GB
extent_size 1024
free_capacity 3.0GB
overallocation 70
warning 0
V
8 Storage
Box A
REDGRP0
read/write
Storage
Box B
REDGRP6K
write
Higher availability and more migration flexibility
IBM_2145:REDCLUSTER:admin>svctask chvdisk -primary 1 8
IBM_2145:REDCLUSTER:admin>
V
8
REDGRP6K
read/write
REDGRP0
write
Change vDisk access set primary to copy 1
2
1
3
Removing storage subsystem affected vDisks?
V
8
REDGRP6K
read/write
REDGRP0
write
V
11
REDGRP6K
read/write
Note: CLI command is svcinfo lscontrollerdependentvdisks
IBM_2145:REDCLUSTER:admin>svctask addvdiskcopy -mdiskgrp 2 -syncrate 100 -rsize 512 -
unit mb -autoexpand V_spunky
Vdisk [11] copy [1] successfully created
11,V_spunky,0,online,yes,yes,4,REDGRP6K,2.0GB,striped
11,V_spunky,1,online,yes,no,2,REDGRP1,2.0GB,striped
11,V_spunky,0,4,REDGRP6K,2.0GB,0.41MB,1.02GB,1.02GB,196,on,80,32
11,V_spunky,1,2,REDGRP1,2.0GB,0.41MB,528.38MB,527.97MB,387,on,80,32
4
5
6
OK now to take storage box offline
Add a vDisk copy in another storage subsystem
V
11
REDGRP6K
read/write
REDGRP1
write
V_THINex data access - primary copy offline
IBM_2145:REDCLUSTER:admin>svcinfo lsmdiskgrp -delim ,
id,name,status,mdisk_count,vdisk_count,capacity,extent_size,free_capacity,virtual_capacity,used_
capacity,real_capacity,overallocation,warning
0,REDGRP0,online,4,10,120.0GB,512,66.5GB,72.00GB,39.54GB,51.70GB,60,75
4,REDGRP6K,offIline,10,2,10.0GB,1024,3.0GB,7.00GB,5.00GB,6.02GB,70,0
V
8
REDGRP6K
REDGRP0
Read/write
V_THINex data access - primary copy online
IBM_2145:REDCLUSTER:admin>svcinfo lsmdiskgrp -delim ,
id,name,status,mdisk_count,vdisk_count,capacity,extent_size,free_capacity,virtual_capacity,used_
capacity,real_capacity,overallocation,warning
0,REDGRP0,online,4,10,120.0GB,512,66.5GB,72.00GB,39.69GB,51.70GB,60,75
4,REDGRP6K,online,10,2,10.0GB,1024,3.0GB,7.00GB,5.00GB,6.02GB,70,0
V
8
REDGRP6K
read/write
REDGRP0
write
V_THINex data access SEV copy deleted
8,V_THINex,0,0,REDGRP0,5.0GB,4.69GB,5.01GB,330.38MB,99,on,80,64
IBM_2145:REDCLUSTER:admin>svctask rmvdiskcopy -copy 0 8
8,V_THINex,1,online,yes,yes,4,REDGRP6K,5.0GB,striped
V
8
REDGRP6K
read/write
V_THINex vDisk detail after SEV copy 0 deleted
V
REDGRP6K
read/write
8
11,V_spunky,1,online,yes,no,2,REDGRP1,2.0GB,striped
V
11
REDGRP6K
read/write
REDGRP1
write
V
11
REDGRP6K
read/write
REDGRP1
read/write
V
nn
Split a mirrored copy to create a new vDisk
Note: CLI command is svctask splitvdiskcopy
Select the copy and name the new vDisk
IBM_2145:REDCLUSTER:admin>svcinfo lsvdisk -delim , -filtervalue name=V_spunk*
id,name,IO_group_id,IO_group_name,status,mdisk_grp_id,mdisk_grp_name,capacity,type,FC_id,F
C_name,RC_id,RC_name,vdisk_UID,fc_map_count,copy_count
11,V_spunky,0,IOGROUP0,online,4,REDGRP6K,2.0GB,striped,,,,,60050768018A8028580000000
000005C,0,1
23,V_spunky_PIT,0,IOGROUP0,online,2,REDGRP1,2.0GB,striped,,,,,60050768018A8028580000
0000000061,0,1
23,V_spunky_PIT,0,online,yes,yes,2,REDGRP1,2.0GB,striped
Two unique vDisks from mirrored copies
V
11
V
23
Mirrored vDisks require writes to both copies which may
impact performance
Mirrored function is placed below cache to minimize impact
Write performance may be restricted by the slower copys
storage subsystem
Mirror to like disk subsystems
No attempt in SVC v4.3.0 to take advantage of mirroring for
performance
For example, read algorithm doesnt try to balance load or
read from both copies
Synchronization is expected to have a similar impact on the
system as FlashCopy or data migration
Can be controlled by syncrate option on svctask chvdisk
VDM - performance
IBM_2145:REDCLUSTER:admin>svcinfo lsmdiskgrp 0
id 0
name REDGRP0
status online
mdisk_count 4
vdisk_count 12
capacity 120.0GB
extent_size 512
overallocation 105
warning 75
Notification options:
SVC log
SNMP trap
email
mDisk group space warning code 989001
(95/120GB)x100=79%
(used capacity/capacity)x100
Defaults to no warning; set with
mkmdiskgrp or chmdiskgrp -warning
SVC v4.3 highlights summary:
Space-efficient virtual disks (SEVs) and space-efficient FlashCopy
provides thin-provisioning and snapshot functionality
enhances utilization efficiency of physical disk capacity
available to all mDisk groups
available to ALL SVC supported storage subsystems
Multi-target FlashCopy - copies increased from 16 to 256
facilitates copy frequency and consumes less storage via SEVs
FlashCopy licensing based on source capacity only
Virtual disk mirroring (VDM) -- two sets of mDisk extents/vDisk
protects against storage subsystem hardware failures
expands data migration flexibility
Number of supported vDisks per I/O group doubles to 2048
SSPC replaces SVC Master Console for SVC Console
Reference Materials
Classes and reference books:
Course SN830 SVC Planning and Implementation Workshop
SVC Information Center http://tinyurl.com/6qdyx8
SVC support Web site - http://tinyurl.com/5bkclv
Redbooks http://www.redbooks.ibm.com, search on SVC
Trademarks and Disclaimers
The following are trademarks of the International Business Machines Corporation in the United States and/or other countries. For a
complete list of IBM Trademarks, see www.ibm.com/legal/copytrade.shtml: ADD TRADEMARKS FROM DOCUMENT THAT
APPLY
The following are trademarks or registered trademarks of other companies:
Java and all Java based trademarks and logos are trademarks of Sun Microsystems, Inc., in the United States and other countries
or both
Microsoft, Windows,Windows NT and the Windows logo are registered 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 or both.
Linux is a 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.
NOTES:
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. Users of this document should verify the applicable data for their
specific environment.
IBM hardware products are manufactured from new parts, or new and serviceable used parts. Regardless, our warranty terms
apply.
Information is provided AS IS without warranty of any kind.
All customer examples cited or described in this presentation are presented as illustrations of the manner in which some customers
have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics will
vary depending on individual customer configurations and conditions.
This publication was produced in the United States. IBM may not offer the products, services or features discussed in this document
in other countries, and the information may be subject to change without notice. Consult your local IBM business contact for
information on the product or services available in your area.
Trademarks and Disclaimers (continued)
All statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and
objectives only.
Information about non-IBM products is obtained from the manufacturers of those products or their published announcements. IBM has
not tested those products and cannot confirm the 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.
Prices are suggested US list prices and are subject to change without notice. Starting price may not include a hard drive, operating
system or other features. Contact your IBM representative or Business Partner for the most current pricing in your geography.
Any proposed use of claims in this presentation outside of the United States must be reviewed by local IBM country
counsel prior to such use.
The information could include technical inaccuracies or typographical errors. Changes are periodically made to the
information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes
in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve
as an endorsement of those Web sites. The
materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own
risk.
IBM makes no representation or warranty regarding third-party products or services including those designated as ServerProven,
ClusterProven or BladeCenter Interoperability Program products. Support for these third-party (non-IBM) products is provided by non-
IBM Manufacturers.
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.

IBM V7000 SAN Storage: Thin Provisioned vs. Fully Allocated

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

IBM V7000 SAN Storage: Thin Provisioned vs. Fully Allocated

Hochgeladen von

Copyright:

Verfügbare Formate

Copyright IBM Corporation 2008

Do You Really Wanna be THIN and/or

Das könnte Ihnen auch gefallen