IP Storage

Maximizing the business value
IP Storage Networking - STRAIGHT TO THE CORE

of enterprise storage technology
Complete diagram set
Perfect for IP Storage Education and Training
For more information visit:
www.straighttothecore.com
© Pearson Education. May not be reused for commercial purposes. www.straighttothecore.com 1

Chapter 01
Storage in a Wired World

1-1: Components of Optimized Storage Deployment
Utilization Availability
and Efficiency
Networked Business
Storage Continuity
Architectures Practices
Optimized
Storage
Deployment
Think Defensively
AND
Offensively
Storage Competence and Agility

1-2: Charting a Storage Networking Roadmap
Charting a Storage Networking Roadmap
Implement
Develop Skills Realize Capabilities
Resources
Utilization and
Efficiency Ne
two
rke
dS
tor
age
Roadmap
Availability Business Continuity Practices
Completion
s
gie
t rate
eS
e nsiv
Off
ND
iveA
ns
Storage Defe
Competence
and Agility

1-3: Target Audience for the Book
Research and Senior IT

CIOs, CEOs
Development Management
Technology Responsibility
Storage and
Straight to the Core CFOs,
Networking
Ambassadors Financial Planners
Professionals
Industry Press and Senior Business

Technology Investors
Analysts Management
Financial Responsibility

Chapter 02
The Storage Architectural Landscape

2-1: Basic Storage Building Blocks
Operating System
File System
Volume Management
Storage Devices (Disks, LUNs)

2-2: The SNIA shared storage model
Application
File/record layer
Database File system

Storage domain
(DBMS) (FS)
Services
Host
Network
Block
aggregation Device
Storage devices (disks, …)
Block layer
© Storage Networking Industry Association

2-3: SNIA shared storage model depicting direct-attach…
Application
1. Direct-attach
1 2 3 4
2. SAN-attach
3. NAS head
File/record
Host Host
4. NAS server
and software RAID
Host. with LVM
Host. with LVM

layer
LAN
NAS
head
Host block-aggregation
NAS Network block-aggregation

SAN server
Block
layer
Device block-aggregation
Disk
array
© Storage Networking Industry Association

2-4: Basic JBOD design
Primary Loop
Secondary Loop
Disks

2-5: RAID Levels Disk 1 Disk 2 Disk 3
RAID 0 – Striping Block 1 Block 2 Block 3

• Data blocks written sequentially
• Not really RAID – no redundancy Block 4 Block 5 Block 6
• Higher performance than single disk access Block 7 Block 8 Block 9
Disk 1 Disk1 Mirror

RAID 1 – Mirroring
• Data blocks written to both disks at once Block 1 Block 1
• 100% redundancy with 100% additional capacity required
Block 2 Block 2
• Reads can be distributed across both disks to increase performance
Block 3 Block 3
Disk 1 Disk 2 Disk 3

RAID 3 – Striping with Byte Parity
• Adds parity information to rebuild data in the event of disk failure
• High transfer rate and availability with lower capacity required than RAID 1 Block 1 Block 2 Parity
• Transaction performance low because all disks operate in lockstep Block 3 Block 4 Parity
Block 5 Block 6 Parity

RAID 4 – Striping with Block Parity – Independently accessible disks
• Data blocks written sequentially to each disk in the array Block 1A Block 1B Parity
• Parity still protects data from disk failure
• Dedicated parity disk is write bottleneck and leads to poor performance Block 2A Block 2B Parity
Block 3A Block 3B Parity

RAID 5 – Striping with Rotational Parity
• Parity blocks written per row and distributed across all disks
Block 1 Block 2 Parity
• Parity distribution eliminates single write bottleneck
• Overhead for parity calculation on writes supplemented with parallel Block 3 Parity Block 4
microprocessors or caching Parity Block 5 Block 6
2-6: Direct Attached Storage
Local Area
Network
Servers Pros:
• Easily configured
• External storage extends server life
• SCSI or Fibre Channel server-to-storage
connection
Cons:
High-speed SCSI • Storage expansion incurs costs of added
or servers
Fibre Channel • Limited scalability
interconnect • No resource sharing
• Single point of failure
Storage Devices

2-7: Comparing SAN and NAS
Windows
Sun File IBM File
File
System System
System
Block commands File Level Commands

to captive disks (NFS, CIFS)
Windows Sun IBM Common File System
Disk Array NAS Filer
SAN–attached disk NAS–disk

2-8: Network attached storage
Local Area Network- Attached

Network Storage
Servers Pros:
• Uses standard Ethernet and IP
• Optimized file handling
performance
• Improved scalability over DAS
NAS Cons:
Filers
• Doesn’t alleviate LAN congestion
• Disruptive “block” storage
expansion/maintenance
• Filer “owns” storage resource
• Unique OS
Tape
Storage Devices RAID Library

2-9: Basics of Fibre Channel Protocol (FCP)
Fibre Channel FC
FCP is an approved ANSI SCSI serialization standard to
Fibre Channel transmit SCSI commands, data, and status information
FCP
Protocol between a SCSI initiator and SCSI target on a serial link.
SCSI Command
SCSI
Set SCSI Bus Protocol
Fibre Channel Network
SCSI Core command set for hosts and device communication
FCP Layer Routable packaging (SCSI serialization) for network connectivity

2-10: Fibre Channel Storage Area Networks
Local Area
Network
Pros:
Fibre • Gigabit speed performance
Channel • Distance storage connectivity ~10KM
Servers • Scales to thousands of storage nodes
• Enables storage resource sharing
• Cons:
• Unresolved Fibre Channel
Fibre Channel interoperability issues
Storage Area • Lack of customer Fibre Channel trained
Network staff
• Introduces second network technology
• Requires separate management system
Storage Devices

2-11: Basics of Internet Small Computer Systems Interface
Internet Protocol IP
The iSCSI protocol transmits SCSI commands, data, and
iSCSI Protocol iSCSI status information between a SCSI initiator and SCSI target
on TCP/IP link.
SCSI Command
SCSI
Set SCSI Bus Protocol
Serial SCSI-3 Transport
TCP/IP Network (SAN, LAN, MAN, WAN)
SCSI Core command set for hosts and device communication
iSCSI Layer Routable packaging (SCSI serialization) for network connectivity
IP Layer Universal connectivity to global IP infrastructure

2-12: Pure iSCSI storage networks
Local Area
Network
Pros:
• Common IP and Gigabit Ethernet
network platform for both LAN and SAN
• Gigabit speed performance
• Unified management structure iSCSI Campus,
• Extensible to WAN and MAN Servers MAN, WAN
• Optimized service provider architecture
• Extensive base of IP and Gigabit
Ethernet trained personnel
• Well defined roadmap to 10 Gbps and Pure
beyond Ethernet and IP
iSCSI Network
SAN
• Cons:
• Relatively new products
• Emerging IP Storage standards
• Replacement of end devices (storage
and adapters)
iSCSI Storage Devices

2-13: NICs, HBAs, and IP storage adapters
Traditional IP Traditional Storage IP Storage
(LAN traffic, NAS) (Fibre Channel based) (Blocks on Ethernet)
Server
Server
Server
Application File Block Block
Layer
Protocols LAN messaging, Fibre Channel Protocol iSCSI

NFS, CIFS
1.5K 1.5K
Frame Frame
Block Block
Driver 1.5K 1.5K
Frame Frame
Layer
1.5K 1.5K
Frame Frame
1.5K 1.5K 1.5K 2K 2K 2K 1.5K 1.5K 1.5K

Link Frame Frame Frame Frame Frame Frame Frame Frame Frame
Layer
On Ethernet On Fibre Channel On Ethernet
Currently, the TCP/IP Fibre Channel avoids the New IP Storage Adapters such
segmentation resides in slowdowns and CPU utilization as iSCSI will also handle the
software, not on the adapter. IP by handling the segmentation in segmentation in hardware on the
Storage can operate like this, but hardware on the adapter adapter through TCP offloading
will be inherently slow and have and acceleration
high CPU utilization

2-14: Using IP to enhance Fibre Channel
Access IP Core
FC Switches / SANs
FC Directors
• Traffic engineering
• Routing
• Global scale of IP
IP Storage Distribution
IP Core IP Storage Distribution Layer

• IP enhancement of FC storage
FC JBODs
• Amplifies Fibre Channel reach and
IP Storage
Switches capabilities
or
Gateways
• Protects both IP and Fibre
• Layer 3 Routers
• Chassis-based Channel existing infrastructure
Ethernet Switches
• Optical Ethernet,
DWDM
FC Tapes
FC Loop
Fibre Channel Access
• End-device aggregation
• Direct-attach focus
FC
FC
• Fan-out of storage ports
Servers
RAIDs

2-15: Mechanisms for linking FC SANs and devices with IP
FC SAN* FC SAN*
IP IP * with IP
Storage Switch
IP Core or Gateway
IP IP
Fibre Channel IP Fibre Channel

2-16: Mechanisms for linking FC SANs to iSCSI with IP
FC SAN* iSCSI SAN
IP IP
* with IP
Storage Switch IP Core
or Gateway
IP IP
Fibre Channel IP

2-17: iSCSI and iFCP/FCIP to connect two FC end nodes
SCSI SCSI SCSI SCSI
FCP iSCSI iSCSI FCP

iSCSI
FC IP IP FC
• Currently, most FC-2 control messages* do not have an iSCSI equivalent,

and the original information cannot be reconstructed from iSCSI.
• iFCP and FCIP provide full transparency for Control Messages, and may
provide more resiliency for Fibre Channel applications heavily reliant on Fibre
Channel infrastructure and error recovery mechanisms.
iFCP/ SCSI
FCP
SCSI
iFCP/
SCSI
iFCP/
SCSI
FCP
FCIP FC
FCIP
IP
FCIP
IP FC
*e.g., RES (Read Exchange Status Block), RSI (Request Sequence Initiative),
TPRLO (Third Party Process Logout), RSS (Read Sequence Status Block)

2-18: Protocol Options for IP storage
iSCSI iFCP FCIP
Devices: iSCSI/IP Fibre Channel Fibre Channel
Fabric Services: Internet Protocol Internet Protocol Fibre Channel
IP IP FC FC FC FC
IP or FC
IP SAN FC SAN
SAN
IP Network
IP or FC
IP SAN FC SAN
SAN
IP IP FC FC FC FC

Chapter 03
The Software Spectrum

3-1: Core components of storage management
Infrastructure
Management
Storage
Management
Transaction Recovery
Management Management

3-2: Software elements of storage management
Infrastructure Transaction Disaster Recovery

Management Management Management
Platform Focus Application Focus Availability Focus
SAN Management Data Coordination Data Protection
Resource Management Policy Management High Availability
Virtualization

3-3: Storage management software components in the enterprise
MGMT
Resource 2 1 SAN
Storage Area Network
5 Virtualization
Policy- 4
Based
Management 3 Data Coordination
and Protection

3-4: Typical storage networking zone configuration
Storage Area Network Zone Configuration
Zones Devices
• Zone 1 • JBOD-A (Drive 0)

• Windows Host A HBA • JBOD-A (Drive 1)
• JBOD-A (Drive 0)
• JBOD-A (Drive 1) • JBOD-B (Drive 0)
• DLT 8000 (Tape Library) • JBOD-B (Drive 1)
• Zone 2 • DLT 8000 (Tape Library)

• Unix Host B HBA
• JBOD-B (Drive 0) • Windows Host A HBA
• JBOD-B (Drive 1)
• DLT 8000 (Tape Library) • Unix Host B HBA

3-5: Topology view of a storage network
Alpha Alpha Alpha Alpha HP9000 HP9000 HP9000 RS/6000
Switch 3
Switch 2
Switch 1
IBM Compaq HP HP IBM

ESS Tape Library XP512 XP512 ESS

3-6: Types of IP and Fibre Channel protocol conversion
FC Domain IP Domain
IP Storage Switches
1. Multiprotocol Conversion
FC Servers and Gateways iSCSI Servers
(iSCSI-FC)
1
FC Storage iSCSI Storage
2. Device-to-device (End Node) 2 (End Node)
interconnect (iSCSI-FC)
for subsystem mirroring
applications
3. SAN extension / FC Fabric/ IP Fabric/

FC Switch FC Switch IP Switch IP Switch
interconnect (iSCSI-FC) Network Network
(FC E_Port)
FC Switch FC Switch 3 IP Switch IP Switch
(Native IP)
4. Protocol extension FC Switch FC Switch 4 IP Switch IP Switch
iFCP and FCIP

FC Switch FC Switch IP Switch IP Switch

3-7: The data coordination path
Operating System
File Systems / File Services

Storage
Aggregation
Volume Management
Storage Devices (Disks, LUNs)

3-8: Storage policies
Storage Policies
Security and Capacity, Content, and Quality of Service

Authentication Quota Management for Storage and SANs

3-9: Storage policy cycle
Start Assessment Definition
Storage Policy Cycle
Evaluation Implementation
Enforcement

3-10: Types of Storage Encryption
Disk
Fabric
Attached
FC Switch Encryption FC Switch Tape
3rd Party
Disk Services
Subsystem
Attached
FC Switch Encryption Tape Offsite
Vaulting
Remote
Mirrored
Gateway / Disk
Tunnel
Encryption Gateways Gateways Encryption
Primary Site Secondary Site
Source:
NeoScale
Disk
Systems
Application
Attached FC Switch Encryption Virtualized
Application Storage
Server
3-11: Storage transport quality of service
Non-critical file
backup
Online transaction processing
backup receives 50 MB/s
guaranteed throughput
50 MB/s
MB/s
Oracle backup
Non-prioritized backup uses
initiated remaining available bandwidth
50MB/s
$ guaranteed
Oracle
OLTP Database
Time
Leverage Ethernet Standards for IP Storage Prioritization
• 802.1Q VLANs to segregate traffic streams
• 802.1p/Q prioritization to guarantee delivery of mission-critical storage data

3-12: Cost-availability tradeoff
Cost
Mirroring
Replication
Snapshot
Disk Backup
Tape
Vaulting (Onsite)
Tape
Vaulting (Offsite)
Days Hours Minutes Seconds
Availability (Backup and Recovery Time)

3-13: Consolidated tape backup across servers and NAS
Servers NAS
Disk Disk Tape

3-14: Serverless-backup through 3rd party copy
Servers NAS
Backup initiation commands
Third-party copy
Data movement (third-party copy)
Disk Disk Tape

3-15: Comparisons of media technologies: disk, optical, tape
Cost per
Megabyte
High-end Disk
Midrange Disk
Optical
Tape
(Onsite)
Tape
(Offsite)
Retrieval Time

3-16: Comparing asynchronous and synchronous replication
Asynchronous Replication Synchronous Replication
Primary Host Secondary Host Primary Host Secondary Host

1. Write to 1. Write to
primary primary
2. I/O 2. Write to
completion – secondary
application 1 1
posted 3. Write
complete on
3. Write to 2 secondary 4
secondary
4. I/O
4. Write completion –
complete on 3 application 2
secondary posted
4 3
Primary Secondary Primary Secondary
Logical Logical Logical Logical
Volume Volume Volume Volume

3-17: Virtualization in homogeneous and heterogeneous
environments
Homogeneous Heterogeneous
A Virtualized B Virtualized
Storage Storage

3-18: Areas of virtualization deployment: host, fabric, subsystems
Host
Fabric
Subsystem

3-19: Types of fabric virtualization
Types
Out-of-band
Speed*
In-band Scalability
Appliance- Switch-
Location
*defined as lower latency based based

3-20: Interoperability strategies and challenges for virtualization
Host
Interoperability Strategy
Interoperability Fabric
Challenge
Subsystem

Chapter 04
Storage System Control Points
Intelligence in the Storage Area Network

4-1: Storage Services within the Storage Software Landscape
See slide 3-2 for greyed areas
Infrastructure Transaction Disaster Recovery
Platform Focus Application Focus Availability Focus
SAN Management Data Coordination Data Protection
Storage
Manageability Capacity Recoverability
Service
Sample
e.g., simplified administration e.g., virtualization e.g., point-in-time copies
Implementation
Resource Management Policy Management High Availability
Storage
Performance Security Availability
Service
Sample e.g., increase I/O beyond e.g., beyond disk failure –
e.g., access control
Implementation single disk with RAID 0,5 mirroring

4-2: Potential Storage Services Locations
Area of Intelligence Hardware Platform
• Servers
Host
• Mainframes
• Appliances
Fabric • Switches
• Directors
• Disks/RAIDs/Controllers
Subsystem • Filers
• Tape Libraries

4-3: Historical trends across computing and storage infrastructure
design
Computing Minicomputers Distributed Web,

Mainframes Client-server
Architecture and Clustering App, DB servers
Storage Access Direct Cluster Small network Global network
Storage Nodes <5 5—10 10—1000 > 1000
Storage
Centralized Decentralized Split Distributed
Architecture
Tape, Large disks and Virtualized storage

Storage Capacity Storage islands
RAMAC RAID pools
Data center and PCs and

Storage Location Data center Anywhere
beyond application servers

4-4: Storage services require size, speed, and distance scalability
Manageability Capacity Recoverability
Performance Security Availability
Storage services require scalability in:
Size
Speed
# of nodes Distance
throughput
reach

4-5: Routers progressed from single to distributed tables for
greater speed and performance
Single Routing Table Distributed Routing Table
Routing tables Routing tables
Router Router
Ports Ports Ports Ports

4-6: Using distributed storage services for optimized deployments
A B
Single Services Location Distributed Services Locations
Ingress Ingress
Services Services
Services
Services Services
Egress Egress

4-7: Optimized network flow through distributed services
Ingress
Egress
Services Services
Intelligent Nodes
with Distributed
Services
Services Services Egress
Egress • With distributed systems, any ingress

connects directly to any egress
• Direct paths are enabled as each node
has embedded services intelligence

4-8: Optimizing Network Efficiency
Network Good
Optimization /
Pushing replication to
Efficiency
appropriate end nodes
minimizes network traffic
and maximizes network
efficiency
Poor
Close
Far
Replication proximity to
destination nodes

4-9: Simplifying network usage models with network-based
storage services
Host-based RAID 1 Target-based RAID 1 Network-based RAID 1
Mirroring
2x x x
Mirroring
x x 2x x x x
Mirroring
4 4 3
Network segments used to complete operation

4-10: Network based services provide full access to storage
attributes
Services Services
Mirror
Host
Services Services
 Target
• Network-based storage services have direct

access to all network points and end nodes
• Host may never know if a mirror is substituted for
corrupt disk

4-11: Optimal locations for storage services
Implementation Optimal Location Reasons

• Attribute-based storage • Network • Visibility, access, knowledge,
Manageability reactive capability
• Application coordination • Host
• LUN creation • Target • Disk aggregation
Capacity
• Volume • Host, network, target • Resizing most easily at host
• Packet recovery • Network • Proximity
Recoverability • Point-in-time copy • Network • Minimize copy traffic
• Disk error • Target or network` • Recovery speed
• RAID 0,5 • Target • Balance target throughput with
Performance network
• Data movement • Network • Minimize usage
Security • Access control • Network • Knows ingress, egress points
• RAID 1 • Depends: network location • Similar to multicasting

Availability optimizes bandwidth
• Dynamic multipath hosting • Host • OS integration

4-12: Primary computing functions
memory cpu I/O network

4-13: The gap between computing resources
Networking and I/O have failed

to keep par with memory and
the CPU
memory cpu I/O network

4-14: I/O and networking increase speed and converge
architecturally
Prior Thinking Current Thinking
I/O
I/O cpu network cpu
network
memory memory

4-15: Leveling the interconnect playing field
Network Scalability (size, speed, distance) Greater Bandwidth Enables Move to I/O Space
A Inter-Processor
Communication
Input/
Output
Local Area
Network
Wide Area
Network B
(IPC) (I/O) (LAN) (WAN)
Number of Nodes
Number of Nodes
ATM
Ethernet
Ethernet
SCSI
PCI FC-
FC-AL
PCI-
PCI-X
InfiniBand
Distance
Distance
Network Space Absorbs I/O Ethernet Efficiencies and Capabilities Move to WAN
C D
Number of Nodes
Number of Nodes
Distance
Distance

4-16: Balancing Multi-Vendor Configurations
Host
Future Competition
Current Competition Fabric
Subsystem

Chapter 05
Reaping Value from Storage Area Networks

5-1: Comparing defensive and offensive storage
networking strategies
Defensive Strategies Offensive Strategies
• Risk management • Operational agility and flexibility

• Short-term cost savings • Medium- to long-term cost savings
• Focus on current assets • Focus on current and future assets
• Conventional platforms • Emerging platforms
• Data Preservation • Enhance enterprise market position

5-2: Storage growth increases risk and total cost of ownership
(TCO)
Defensive Strategies Offensive Strategies

(Drive down risk) (Drive down TCO)
Risk TCO
Storage
Storage
growth
growth
increases
increases risk
TCO
Time Time

5-3: Data availability through redundant paths in a simple SAN
Servers
Storage
Area
Network
Storage Devices

5-4: High availability through director-class switches and scalable
fabrics
Servers
Storage
Core Fibre Channel Directors
Area
OR Gigabit Ethernet Switches
Network
Storage Devices

5-5: Incorporating remote sites to storage networks
Servers
Remote Site
Storage
Area
Remote
Network Network
Storage Devices
5-6: Sample customer configuration with a redundant
core and remote storage
Legend
Server Storage Core Switch
FC or iSCSI FC or iSCSI Switch
Primary Site
Storage
Remote Network
Remote Site

5-7: Storage networks facilitate storage management savings
Direct-attached SAN-attached
Storage Management Storage Management
Servers Servers
Storage
Management
Storage
Management
Storage Devices Storage Devices

5-8: IP networking extends across traditional data and new IP
storage applications
• IP network provides flexibility and operational agility across all installations

• Centralization of network technology reduces management and administration cost
FC SAN with Mixed SAN with

IP Storage IP Storage
LAN Clients NAS Clients Gateways Switches or Routers iSCSI Servers
IP Network
LAN Servers NAS Servers FC SAN with Mixed SAN with iSCSI Storage
Gateways Switches or Routers

5-9: Conventional Fibre Channel storage area network and
Ethernet/IP local area network
Clients
• Dual SAN and LAN / NAS fabrics
cost more to install and operate
IP Network
– Having IP and Fibre Channel
(LAN) fabrics for storage requires
LAN / NAS Network-
• dual management systems
Access Attached
Storage
• extra hardware
• duplicate staffs and training
FC
SAN
Access • Fibre Channel fabric has no
transition path to native IP end
FC Fabric
systems
FC
FC FC FC
Storage Storage Storage

5-10: Introduction of IP storage fabric and iSCSI
Clients
• IP storage fabric complements
or replaces FC fabric
IP Network
– Functionality identical to that of
(LAN) Fibre Channel switches, but
LAN / NAS Network-
with more flexibility
Access Attached
Storage
– Non-blocking, IP storage fabric
iSCSI or FC
provides full support for iSCSI
SAN and FC, with wire-speed
Access
conversion between the two
protocols
IP Storage IP
Fabric MAN / WAN • IP storage fabric supports
FC gradual or immediate shift to
FC Switches iSCSI end systems
iSCSI
Storage

5-11: Integrated SAN and NAS
Clients
Enhanced Functionality of Integrated
SAN and NAS Solution
– Optional use of IP storage fabric
FC for both SAN (block-based) and
Servers with IS-NICs Server
Network-
NAS (file-based)
Attached
Storage
– IS-NICs provide access for all
SAN / NAS
end systems (SAN, NAS, and
Access LAN clients)
(iSCSI, FC,
NFS, CIFS) – IP storage switches provide wire-
speed, non-blocking IP storage
IP Storage IP
Fabric MAN / WAN fabric for all IP and Fibre Channel
devices
Hybrid NAS/SAN
Subsystems
iSCSI FC FC
Storage Storage Storage

5-12: Segmenting the IP storage fabric from the IP
network backbone
Fibre Channel iSCSI
NAS Client
Servers Servers
IP Storage Fabric
Legacy IP Network
Fibre Channel Backbone
Fabric
Fibre Fibre Server End User Voice

Channel Channel Farm Access
Servers Storage
Fibre Channel iSCSI NAS
Storage Storage Server

5-13: Framework for multi-layered storage fabrics
iSCSI/IP Servers
IP Core
FC Switches / SANs
• Traffic engineering
• Routing
• Global scale of IP
IP Storage Distribution Layer

• IP enhancement of FC storage
FC Storage
• Amplifies Fibre Channel reach and
IP Storage
Switches capabilities
or
Gateways
• Protects both IP and Fibre
Channel existing infrastructure
• Layer 3 routers
• Chassis-based Ethernet switches
FC Tapes • Optical Ethernet, DWDM
Multifunction
Devices
including NAS
Access Layer
FC
Servers
• End-device aggregation
iSCSI/IP Storage • Direct-attach focus
• Fan-out of storage ports

5-14: Allocating the IP storage fabric among storage platforms
IP Core and IP Core

Distribution serve
multiple storage
platforms and can
be allocated as
needed IP Storage
Distribution Layer
Multifunction
FC Switches / iSCSI Storage
devices including
SANs devices
NAS

5-15: Setting information technology business priorities
Information Technology Investment Priorities
Defend, support, Enhance IT

expand current Develop new business capabilities and
business expertise
First Priority Second Priority Third Priority
Long-term planning cycle and feedback loop

(Third priority can’t be ignored, but may have lower spending)

5-16: Creating strategic and operational links between IT groups
and business units
CEO
and
Financial Planning Group
Information Business Units

Technology Group
Strategic Links
Integrated
service
offering Operational Links
Immediate Strategic
Requirement

5-17: Storage technologies and opportunities for competitive
advantage
Technologies
Leading and Emerging Exploit competitive

Warning for present
• e.g., Mulitprotocol SANs advantage
Competitive and Developing Develop competitive

Warning for future
• e.g., conventional SAN/NAS advantage
Basic and Commoditized Warning for waste of

Warning for survival!
• e.g., RAID, tape backup resources?
Weak Strong Competitive Strength

Chapter 06
Business Continuity for Mission Critical Applications

6-1: Increasing levels of availability requirements
1. Backup 2. Disk Redundancy 3. Failover 4. Point-in-Time Copy
5. Wide-Area Replication 6. Wide-Area Replication and Failover

6-2: Sample storage application placements against RPO and
RTO
Weeks
Backup
Recovery Point Objective
Days
Asynchronous
Replication
Minutes
Local Synchronous
Seconds
Clustering Replication
Seconds Minutes Days Weeks
Recovery Time Objective

6-3: Single host backup method and using mirroring
prior to backup
Single-Host Backup Method Using Mirroring Prior to Backup
Backup Server
Application Application
1. Quiesce application
2. Flush cached data
3. Take application off hot
backup mode
4. Attach mirror to backup
host Mirror
5. Reattach mirror to
primary upon backup
completion
Application server processes Backup server processes the

the backup operation, backup operation using
including primary data set mirrored data set

6-4: Comparing RAID 0+1 and 1+0
RAID 0+1 RAID 1+0
 Stripe A
Stripe B
Mirror Stripe
Mirror Mirror Mirror
1. lose 1 disk 1. lose 1 disk

2. entire stripe is lost 2. disk is lost
3. shift to mirror 3. continue to run stripe
4. no room for error 4. disk failure in another mirror
non-impacting

6-5: An example point-in-time snapshot copy method
12:00pm 12:05pm 12:30pm

Snapshot taken C becomes C1 Snapshot taken
Data Snapshot Data Snapshot Data Snapshot
A … A … A …
File System
… … …
B … B C B …
… … ..
C 2 C1 C1
D D C D
1
Snapshot taken with • Copy C Original C is available

references to original data • Update data C to C1 through 12:00pm snapshot
(must be retained)

6-6: Examples of clustering and high-availability storage
networking solutions
Clustering Failover and Multiple Application Failover

High-Availability
Simultaneous Data Access Standby Data Access Standby Data Access
Application Application Application Application App 1 App 2 App 3 App 1−3

Instance 1 Instance2 Instance Standby Standby

1 2 3

6-7: Off-site vaulting delivers geographic disaster tolerance
Offsite Vaulting
Data Center 1 Data Center 2
Location A Location B (Media Warehouse)

6-8: Intelligence required to avoid corruption during
asynchronous replication
Database Standby Database Database Standby Database
Block 1
8KB Data
Block Block 2
4KB
Committed
 Block 2
Committed
4KB
Incomplete
Block 1
Potential corruption due to partial Potential corruption without

write acknowledgment maintaining write order fidelity

6-9: Data consistency chart
Replication Modes
Synchronous Asynchronous
No
Confirm no partial In-order writes May need point-in-time
writes acknowledged Full block writes copy at second site
Yes Yes
Data consistent at Data consistent at

second site second site

6-10: Stack layers for various replication technologies
Replication Layer Sample

Stack Application Pros Cons
Data integrity easily

Application Custom applications Application-specific
maintained at second site
Oracle Dataguard, Sybase

Database administrator- Does not replicate binaries
Database replication, Quest
friendly or application components
Shareplex
Host
NetApp SnapMirror,
Active-active mode Not available for raw-
File System VERITAS Storage accessible during access database
Replicator, NSI replication (non-database) applications
Doubletake
Logical Volumes VERITAS Volume

Replicates all elements Host support limitations
Replicator, Sun SNDR
Storage device
LUNs EMC SRDF, HDS Replicates all elements compatibility issues; may
Storage TrueCopy, XIOtech REDI
Multihost support not operate across more
SAN Links
Array than two arrays

6-11: Sample operation of database transaction log replication
Database Transaction Log Replication

Database Standby Database
Apply transaction logs periodically. Point-in-

time copy is the transaction log last
copy/replication.

6-12: Layers of storage redundancy and sample enterprise
applications
Redundancy
Sample Enterprise Applications
Layer
Internal Web Sites

Load balancers
(tied to back-end
ERP databases)
(e-commerce, ERP with front-end Web-services)
Web servers
End-to-End Applications
Application
servers
Standalone
Database
Database
servers
Ethernet
Core
Database
Storage area
network
Storage
subsystems

Chapter 07
Options for Operational Agility

7-1: Increases in complexity of solution create value and need for
outsourcing
Value HW, SW and Infrastructure, People, Management Software
People
Software and Infrastructure
Hardware
Complexity

7-2: Service offerings for a across storage and network service
providers
Storage Service Provider Capabilities
Full-service SSP
Backup/Restore Primary SAN Primary NAS
Service Offerings
offerings
Network service
Remote Tape Remote SAN Remote NAS
provider offerings
Surge Capacity Mirroring Content Delivery Accessory services
Onsite Offsite A la carte

Tape Vaulting
Management Management management options

7-3: The effect of storage management software on the deployed
infrastructure
Normalized Infrastructure
Normalization
Gap
Readiness
SLA
RAS
Integration
Price
Vendor A Vendor B Vendor C Vendor D

7-4: The effect of provisioning capacity to meet short-term
capacity requirements
Capacity
(GB)
Original
Purchase 1
Purchase Plan
$ Savings*
Purchase Plan
Purchase 2 w/Terabyte
Rental
Time * less terabyte rental fees

7-5: A comparison of the activities between onsite and offsite
storage management
Onsite Storage Management Offsite Storage Management
Value HW, SW and Infrastructure, People, Management Software Value HW, SW and Infrastructure, People, Management Software
People People
Software and Infrastructure Software and Infrastructure
Hardware Hardware
Complexity Complexity

7-6: The Storage SLA Process
Storage SLA Process
Plan Requirements Assessment Develop SLA
Execute Final Design Build Out Activation
NOC Change Ongoing

Manage Management Management Activities
7-7: Description of the relationship between centralization phases
and roles
Phase Roles
Initial 1. Quality Assurance
Proactive Management 1. Asset Tracking

2. Change Management
Reactive Management 1. Event Management

and Troubleshooting 2. Problem Management
7-8: Lack of disruption when changing the application server
Application Transition
App 1 App 2 App 3 App 1 App 2 App 3 App 2
Network Layer Network Layer

 
Chapter 08
Initiating Deployment
8-1: Commoditization and open systems drive fluidity of the end-
to-end storage chain
Intelligent
Storage
I/O Device I/O Network Node Drive
Network
Blade
Server
I/O HBA
Enabler PCI-X iSCSI IP Storage Protocols x86-based Serial ATA,

PCI-Express Devices IDE
8-2: Applying fluidity to the IP Storage Model
Platform Convergence Drivers Layered Model

(NAS, SAN, Object)
• Ethernet and IP • IP Core / Backbone

Networks, IP Storage
Protocols • Storage Distribution
Layer
IP Core / Backbone • Intelligent Storage
• Rack-Mounted x86
Servers Nodes
Intelligent
• Distributed Services
Storage
• PCI-X, PCI-Express Nodes
Servers • Access
• Serial ATA, IDE • End-Device
Storage Distribution Aggregation
Storage
Access
8-3: Locations for storage intelligence
Area of Intelligence Hardware Platform
• Servers
Host
• Mainframes
• Appliances
Fabric • Switches
• Directors
• Disks/RAIDs/Controllers
Subsystem • Filers
• Tape Libraries
8-4: Overlaying host, fabric, and subsystem intelligence with the
IP storage model
Access Host
Storage Distribution
Fabric IP Core / Backbone
Storage Distribution
Subsystem
Access
Network SAN Storage Remote SAN

Areas of Storage Intelligence Attached Consolidation Connection
(Host, Fabric, Subsystem) Storage (ISCSI converted (FC-IP-FC)
(Server to Filer) to FC)
8-5: Minimizing improvement costs through product consolidation
Storage Network- Object-
Area Attached Oriented
Networks Storage Storage
Access
• Hosts Product Product Product
• Subsystem
Distribution
• Intelligent Product Product Product
Storage Nodes
Core
• Switches, Product Product Product
Directors
Product Consolidation Opportunities
Conventional Fibre Channel Network Object

Fibre Channel SAN Attached Oriented
SAN Extension Storage Storage
FC Servers FC Servers NAS Clients Clients and

Disk Arrays Disk Arrays and Servers Servers
IP Storage Index or
SAN Appliance Transparent
Router Content Nodes
FC Switches IP Core IP Core IP Core
8-8: Using IP networking for SAN to SAN remote mirroring
Campus C IP SAN
Campus A Campus B
High Availability
FC SAN FC SAN
IP MAN or WAN
Switch or Switch or
Gateway Gateway
8-9: Using an IP core for storage consolidation
Native IP
Devices
FC SAN . FC SAN
Switch or Switch or
Gateway Gateway
Native IP
FC Devices
Devices
8-10: Metropolitan area IP connectivity for outsourced storage
services
Customer B Customer C
ON PREMISES ON PREMISES
Customer A Customer D
ON PREMISES ON PREMISES
FC SAN FC SAN
FC SAN
FC SAN
MAN/WAN
Storage Service Provider

Primary Storage
Collocation Center
8-11: The transition to reference information
Source: The Enterprise Storage Group, April 2002
8-12: Comparing dynamic and fix content characteristics
Dynamic: Fixed Content:

OLTP, ERP, Data Warehousing … Email, Images, Documents …
Throughput Retrieval Speed
• Block and file I/O • Metadata query processing
Availability Availability
• 99.9999% uptime • 99% uptime
Total Cost of Ownership Total Cost of Ownership
• Component versus component cost • Greater upstream and downstream cost
implications (e.g., more exchange
servers required to point to data)
8-14: Implementing a distributed system for email storage
Servers Servers
. .
Intelligent Storage
Nodes
Storage Storage
8-15: Distributed intelligent storage nodes for NAS scalability
Servers Servers
. .
Intelligent Storage
Nodes
Storage
Storage
Chapter 09
Assessing Network Connectivity
9-1: Cargo and Data Transport Analogies
Empty Railcars on a Railroad SONET Frames on Fiber-Optic Cable
Layer One
SONET SONET
Mux Mux
Containers on Trailers on Railcars IP Packets in Ethernet Frames on SONET

Layers One, Two, and Three
Ethernet Frames
IP Packet IP Packet
SONET SONET
Mux Mux
Containers Placed Directly on Railcars IP Packets Directly on SONET

Layers One and Three
IP Packet IP Packet
SONET SONET
Mux Mux
9-2: Ethernet Interfaces on Multiplexers Enable Direct Link from
Ethernet LAN
(100 or 1000 Mbps)
LAN Switches
Ethernet LAN
(100 or 1000 Mbps)
Switch Switch
Switch Switch
Switch
Ethernet Link Switch
(100 or 1000 Mbps)
SONET / SDH Ethernet Link
Router
Router Mux Network (100 or 1000 Mbps)
SONET / SDH (622 or 2488 Mbps)
(155 or 622 Mbps) Router
Router
SONET / SDH
Packet over SONET Router (155 or 622 Mbps)
Ethernet LAN
(100 or 1000 Mbps)
Ethernet LAN
(100 or 1000 Mbps)
Switch Switch
Switch Switch
Switch
Ethernet Link
Switch
(100 or 1000 Mbps)
SONET / SDH Ethernet Link
Mux Network (100 or 1000 Mbps)
(622 or 2488 Mbps)
Direct Ethernet Link to Muxes
9-3: File-based Backup Locally, via the LAN, and Remotely, via
the Existing Data Network
Ethernet LAN Ethernet LAN

Clients and Servers Clients and Servers
(File-based) (File-based)
SONET / SDH
LAN Router Mux Network Router LAN
Servers Convert between

Files (IP and Ethernet) and
Blocks (Fibre Channel or SCSI)
External Storage External Storage

(Block-based) (Block-based)
9-4: Block-based Backup Locally, via the SAN, and Remotely, via
Dedicated Fiber

Clients and Servers Separate Mux Circuit Clients and Servers
(File-based) (Fibre Channel) (File-based)
SONET / SDH
SAN SAN
Separate Dedicated Link

(Fibre Channel)
External Storage External Storage

(Block-based) (Block-based)
9-5: Rates for SONET and SDH transmissions
SONET (North America) SDH (Rest of World) Rate
OC-3c STM-1 155Mbps
OC-12c STM-4 622Mbps

(2.5Gbps)

(10Gbps)
9-6: Block-based Backup Locally, via the SAN, and Remotely, via
the Existing SONET Network, using the IP Storage Protocol

Clients and Servers Clients and Servers
(File-based) (File-based)
SONET / SDH
If SAN is Fibre Channel,

a Separate Switch is
SAN used to convert to IP SAN
SAN can be Fibre Channel,

iSCSI, or iFCP External Storage
(Block-based)
9-7: IP Storage Protocol Recommendations for SANs, Metro, and
Wide Area Connections
Fibre Channel to Fibre Channel to

Fibre Channel IP Storage
Fibre Channel Fibre Channel
to IP Storage to IP Storage
(MAN and WAN) (Data Center SANs)
FC IP FC FC IP FC FC IP IPS IPS IP IPS
FCIP (No specifications) (No specifications) (No specifications)

(Tunneling)
iFCP (iSCSI recommended) (iSCSI recommended)

(Native IP)
iSCSI (No specifications) (No specifications)

(Native IP)
9-8: Native IP SANs can be Interconnected across Metro and
Wide Areas with no Additional Conversion Equipment
SONET / SDH
IP IP
Fibre Fibre
Channel Channel
SAN Separate switch converts SAN
FC into IP format
(FCIP or iFCP)
SONET / SDH
IP IP
IP SAN IP SAN
No separate switch
is needed
9-9: IP SANs can be Expanded Easily, using Standard
Gigabit Ethernet Core Switches
SONET / SDH
LAN Router Mux Network
IP
Fibre Channel
or iSCSI
iFCP or iSCSI links between
Server Links
the storage switches
and the core switches
Multiprotocol
Storage Switches iSCSI can be connected
and Gigabit Ethernet directly to the core switches or
through the storage switches
Core Switches
Fibre Channel
or iSCSI
Storage Links
9-10: Service Provider Connections Vary by Subscriber
Density and Location
Subscribers A, B, C Data Centers Subscriber A Backup Center
in Multi-tenant Office Building in Suburban Office Building
Subscriber B
A Backup Center
Center in Asia
A B New Cable
Installed to
Nearest Mux
Riser B
Cables
CLE SONET / SDH

Mux Network International WAN
Underground
C Vault by
Building
Subscriber C Backup Center

in Nearby Office Building
9-11: Areas for IP Storage Security Solutions
Device I/O VPN at Data Center Egress

Fibre Channel HBAs and Minimum requirement for
native IP (iSCSI) HBAs SAN
IP storage security
VPN
SAN Interconnect
IP and Ethernet
MANs and WANs
VPN
VPN
SAN
Data Center Network (SAN)

Fibre Channel switches, IP storage
switches, or IP switches
9-12: Sample security implementation across data center, metro,
and wide area networks
Data Center Metro Area Network Wide Area Network
Network • FC, Gigabit Ethernet / IP • FC, Gigabit Ethernet / IP • IP over Ethernet

Technology • Layer 2 / 3 • Layer 2 / 3 • Layer 3
Network • Local Area • Dedicated or provisioned • Shared network

Characteristics Connectivity bandwidth
Security • MAC level • MAC level • VPN

Implementation • IPSec at end device • IPSec at end device or
Options • FC encryption egress point
• FC encryption
• VPN
Chapter 10
Long Distance Storage Networking Applications
10-1: Remote data replication and centralized backup
Primary
Metro Area Data
Backup Center in
Data Center London
in Reading
Storage Consolidation
in London and Vancouver
Data Centers
10-2: IP network performance is close to light speed and packet
loss is near zero
Source: AT&T Website
10-3: Estimating the amount of data to be mirrored
• Determine the amount of data stored on the primary storage

array.
Primary
Storage Array
SAN SAN
• Estimate the portion of the primary storage that is changed on a

peak day. For example, the peak day might be a certain day of
the week or the last day of each fiscal quarter.
• If the activity on that day is concentrated mainly into, say, eight or

ten hours, then an average hourly data rate for the peak day
should be calculated over that amount of time rather than over 24
hours.
• If there is a peak hour during the peak business day, it should be

used for the estimate rather than simply taking the average rate.
For example, if from 1:00 to 2:00 p.m., the data rate is two or
three times the average, the circuit should be sized for that rate.
10-4: Numerical example of peak hour data activity
• The usable capacity of the primary storage array is 12 TB

(terabytes). However, the array only is about one-third full, so
assume that 4 TB (4000 GB) of actual data is stored.
• On the peak day, approximately 15 percent of the data is

changed:
4000 GB x 0.15 = 600 GB
12 TB usable capacity Peak
Data 2.5x
Activity Average
4 TB used
15% changed daily

Time in Business Day
• During the day, most of the activity occurs between 9:00 a.m. and
7:00 p.m. (ten hours), so the average amount of data written per
hour during that period is approximately
600 GB / 10 hours = 60 GB/hour
• The amount of increase over the average for the peak hour of the
day is not known, so a peak-to-average ratio of 2.5 is used:
60 GB/hour x 2.5 = 150 GB/hour
10-5: Estimating the amount of traffic on the network links
• Convert the peak hour data estimate from gigabytes per hour to
megabytes per second.
• Add approximately 10 percent for network protocol framing

overhead.
• Convert from megabytes (MB) to megabits (Mb). There are about

1.049 million (220) bytes in a megabyte of data and there are eight
bits in a byte of data, so the conversion factor is 8.39.
10-6: Numerical example of a network link traffic estimate
• The amount of data written to the primary storage array during the
peak hour is 150 GB. That can be converted to megabytes per
second (MBps) as follows:
150 GB/hour x 1000 MB/GB = 150,000 MB/hour

150,000 MB/hour x 1 hour/3600 seconds = 41.6 MBps
• Including the additional framing overhead, the amount of WAN

traffic generated per second during the peak hour is
41.6 MBps x 1.1 = 45.8 MBps
• In bits per second (bps), the estimated WAN bandwidth required

for this application is
45.8 MBps x 8.39 Mb/MB = 384 Mbps
10-7: Estimating the propagation and node delays
• Determine the actual route distance between the endpoints of the

network link. The service provider usually can furnish that
information. Assume a propagation delay of one millisecond per
hundred miles (round trip).
• Determine the number of switches and routers in the data path.

The service provider also can furnish that information or at least
estimate it. Assume a relatively conservative estimate of two
milliseconds per switch or router. Be sure to include the number
of nodes in both directions for the round trip delay.
10-8: Estimating the congestion queuing delay
• Determine the current average utilization of the network link

without the storage application (0−100 percent).
• Subtract that value from 100 percent to derive the proportion of

bandwidth that is available for the new storage networking
application.
• Divide the total node delay by the proportion of bandwidth

available for the new storage networking application. For
example, if all of the bandwidth is available for storage
networking, the divisor will be 1.0, and there will be no additional
congestion queuing. On the other hand, if only half of the
bandwidth is available, the divisor will be 0.5, which would predict
that the node delay would be doubled by the congestion queuing.
10-9: Numerical example of total network latency
• The distance between the endpoints of the network link, which
connects the primary and secondary data centers, is 200 miles.
Therefore, the round-trip propagation delay is:
200 miles x 2 = 400 miles
400 miles x 1 ms/100 miles = 4 ms
• There are four routers in the path taken by the data, so the
estimated round trip node delay is:
4 nodes x 2 x (2 ms/node) = 16 ms
• The current average network link utilization without the storage

application is 15 percent, so the amount of bandwidth available for
the new storage networking application is:
100% – 15% = 85%
• With congestion processing delay, the round trip node delay is

increased to:
16 ms / 0.85 = 19 ms (in this case, the congestion delay adds 3 ms)
• The total network latency (propagation delay + node delay +

congestion delay) is:
4 ms + 16 ms + 3 ms = 23 ms
200 miles
LAN Assume each router adds 2 ms LAN
Router Router
SAN SAN

Existing network
15% capacity
85% of bandwidth
available for storage
Chapter 11
Managing the Storage Domain
11-4: Defining simplicity
Current Environment Required Environment

Context Overload Managed Context
Storage Storage
Management
Infrastructure Infrastructure
$ per $ per
Gigabyte Gigabyte
Management
Time Time
11-5: Practice disciplines for managing the storage domain
Business
Management
Risk Data
Source: The Data Mobility Group
11-6: Business management practice objectives and
implementation examples
Business Business Management Objective

Management • Management of storage domain as
business entity
Implementation examples
• Service Level Agreements (SLAs)
• Tracking and usage charge-back
• Quality of Service (QoS)
• Hardware and software decision making
11-7: Risk management practice objectives and implementation
examples
Risk Management Objective

• Use of the storage domain to mitigate
corporate risk
• Disaster recovery and business continuity
• Backup and restore
• Security Risk
Management
11-8: Data management practice objectives and implementation
examples
Data Management Objective

• Effective presentation of data within the
storage domain using storage-based file
systems and copy functions
• Storage-based file systems (e.g., NAS)
• Copy functions for content distribution,
Data
performance optimization
Management
• Network storage design and architecture
11-9: Implementing Quality of Service Policies
Partitioned Intelligent
Host Systems Storage Subsystem
OLTP OLTP
A •QoS Mechanisms: A
Server Server
IEEE 802.1p/Q, IETF DiffServ, IETF MPLS, IETF RSVP
Customer Web Customer Web

B B
Catalog Server Catalog Server
Storage Network
Corporate Corporate
C C
Email Server Email Server
Corporate Corporate
D Traffic Prioritization Engine D
File Server File Server
First In D Corporate File Server OLTP Server A High Priority
B Customer Web Catalog Customer Web Catalog B

Incoming Outgoing
Traffic Priority
C Corporate Email Server Corporate Email Server C
Last In A OLTP Server Corporate File Server D Low Priority
11-10: Storage Network Open Management Checklist
SAN / DAS NAS
Vendor A Vendor B Vendor C Vendor A Vendor A
Topology
Discover
Logical relationships
Array, SAN, NAS, and host health
Array performance
Monitor/ SAN performance

Report Host performance
Database performance
Configuration/utilization
Filesystems and volume managers
Zoning
Provision
LUN masking
Storage devices
Alert resolution
Automate Provisioning
Replication
Source: EMC Corporation

Chapter 12
Perfecting the Storage Engine
12-1: From Defensive to Offensive Strategies
Medium- to
Defensive Strategies Long-Term Offensive Strategies
Planning
From Context to Core

IP Storage

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IP Storage

Uploaded by

Copyright:

Available Formats

Maximizing the business value

IP Storage Networking - STRAIGHT TO THE CORE

Complete diagram set

Perfect for IP Storage Education and Training

For more information visit:

© Pearson Education. May not be reused for commercial purposes. www.straighttothecore.com 1

Storage in a Wired World

© Pearson Education. May not be reused for commercial purposes. www.straighttothecore.com 2

Storage Competence and Agility

Charting a Storage Networking Roadmap

© Pearson Education. May not be reused for commercial purposes. www.straighttothecore.com 4

Research and Senior IT

Industry Press and Senior Business

© Pearson Education. May not be reused for commercial purposes. www.straighttothecore.com 5

The Storage Architectural Landscape

© Pearson Education. May not be reused for commercial purposes. www.straighttothecore.com 6

Storage Devices (Disks, LUNs)

© Pearson Education. May not be reused for commercial purposes. www.straighttothecore.com 7

Database File system

Storage devices (disks, …)

© Pearson Education. May not be reused for commercial purposes. www.straighttothecore.com 8

Host. with LVM

NAS Network block-aggregation

© Storage Networking Industry Association

© Pearson Education. May not be reused for commercial purposes. www.straighttothecore.com 9

© Pearson Education. May not be reused for commercial purposes. www.straighttothecore.com 10

RAID 0 – Striping Block 1 Block 2 Block 3

Disk 1 Disk1 Mirror

Disk 1 Disk 2 Disk 3

Block 5 Block 6 Parity

Disk 1 Disk 2 Disk 3

Block 3A Block 3B Parity

Disk 1 Disk 2 Disk 3

© Pearson Education. May not be reused for commercial purposes. www.straighttothecore.com 12

Block commands File Level Commands

Windows Sun IBM Common File System

Disk Array NAS Filer

SAN–attached disk NAS–disk

© Pearson Education. May not be reused for commercial purposes. www.straighttothecore.com 13

Local Area Network- Attached

© Pearson Education. May not be reused for commercial purposes. www.straighttothecore.com 14

Fibre Channel Network

SCSI Core command set for hosts and device communication

FCP Layer Routable packaging (SCSI serialization) for network connectivity

© Pearson Education. May not be reused for commercial purposes. www.straighttothecore.com 15

© Pearson Education. May not be reused for commercial purposes. www.straighttothecore.com 16

Serial SCSI-3 Transport

TCP/IP Network (SAN, LAN, MAN, WAN)

SCSI Core command set for hosts and device communication

iSCSI Layer Routable packaging (SCSI serialization) for network connectivity

IP Layer Universal connectivity to global IP infrastructure

© Pearson Education. May not be reused for commercial purposes. www.straighttothecore.com 17

iSCSI Storage Devices

© Pearson Education. May not be reused for commercial purposes. www.straighttothecore.com 18

Protocols LAN messaging, Fibre Channel Protocol iSCSI

1.5K 1.5K 1.5K 2K 2K 2K 1.5K 1.5K 1.5K

© Pearson Education. May not be reused for commercial purposes. www.straighttothecore.com 19

IP Core IP Storage Distribution Layer

© Pearson Education. May not be reused for commercial purposes. www.straighttothecore.com 20

Fibre Channel IP Fibre Channel

© Pearson Education. May not be reused for commercial purposes. www.straighttothecore.com 21

FC SAN* iSCSI SAN

© Pearson Education. May not be reused for commercial purposes. www.straighttothecore.com 22