san design considerations hylton leigh senior consultant novell consulting, uk stuart thompson...

SAN Design Considerations

Hylton LeighSenior ConsultantNovell Consulting, UK

Stuart ThompsonSenior ConsultantNovell Consulting, UK

© March 9, 2004 Novell Inc.2

one Net: Information without boundaries…where the right people are connected with the right information at the right time to make the right decisions.

The one Net vision

Novell exteNd™

Novell Nsure™

Novell Nterprise™

Novell NgageSM

:

:

:

:

© March 9, 2004 Novell Inc.3

The one Net vision

Novell Nterprise is an innovative family of products which gives you the power to enable and manage the constant interaction of people with your business systems — regardless of who they are or where they are.

Novell Nterprise™

Novell exteNd™

Novell Nsure™

Novell Nterprise™

Novell NgageSM

:

:

:

:

© February 24, 2004 Novell Inc.4

Agenda

Business Drivers

Storage Methodologies

SAN Components

Design Considerations

• Storage

• Cluster Services


Business Drivers

Availability

Fault Tolerance

Consolidation

Disaster Recovery

Nice new toy!


DAS NAS SAN

ServerApplication

File System

Data

Storage Methodologies

Application

File System

Client or Server

NAS Server

Application

File System

Server

RAID Array

Data Data

LAN

SAN


Storage Costs

DAS

SANNAS

Implementation Cost

Op

era

tional C

ost


Scale of Storage

DAS

SAN

NAS

Availability

Sca

labili

ty


Logical SAN Components

Storage Initiator (Client)

Storage Target

Storage

CommunicationChannel

Server NIC, Cluster HBA

Storage Controller

Discs

Cable, SAN Switch/Hub

Physical SAN Components


Server NIC

• iSCSI-based SAN

• NIC teaming

Storage Target

Storage

Communication Channel


Cluster Node HBA

•Connects the Cluster Node to the SAN Switch

•Single or Multiple

•Cost v. Node Availability

•Multiple HBA

• OS, HBA Driver, Multipath software

• Failover

• Load Balancing

– Dynamic or Static

Storage Target

Storage



Cable


Storage Target

Storage

•Often overlooked but critical

•Fiber

•Ethernet

•Copper

•Protocols

• FC, iSCSI, FCIP, iFCP


SAN Switch/Hub

• Connects the Storage to the Cluster Nodes

• Similarities with LAN switches/hubs

• Can expand to include discussion of arbitrated loop, switched fabric etc…

• Edge v Core v Director class switches

• Zoning


Storage Target

Storage


Storage Controller


Storage


• Provides intelligence of the storage

• Provides caching

• Snapshot controlled here

• LUN Masking

• Security

• What your cable plugs into

• How many to have?

• Connected to Switch/Hub

• FalconStor type virtualisation devices


Storage


Storage Target


• SCSI / Serial ATA / Parallel ATA / FC / Solid State

• JBOD

• RAID

• Virtualisation


Non-physical Components

Storage Management

Data Replication

Data Backup


Storage Management

Vendor Specific

Scope of Management

Industry Standards

• SNMP

• SNIA SMI


Data Replication

Mirrors

Snaps

Clones


Data Backup

NDMP

SAN attached tape library

Separate Node for Backup

Cluster aware backup software

Open File Backup


LUNs / Partitions / Pools

LUN is unit of storage presented by SAN

LUN can be thought of as a “disk”

LUN “owned” by a SAN Controller

LUN contains Partition

Partition contains Pool

Pool contains Volumes

Pool is unit of clustering


Presenting storage to nodes

Storage Area Network Devices (JBOD Disks or RAID sets)

Partition SegmentsPartition Segments

NetWare DisksNetWare Disks

Aggregation function()Aggregation function()

Storage PoolsStorage Pools

Logical Volumes Logical VolumesLogical Volumes Logical Volumes


LUN access on SANs

Homogeneous SANs• LUNs shared by all servers in a cluster

– Cluster software controls multi-initiator I/O

Heterogeneous SANs• LUNs dedicated to standalone servers• LUNs shared by all servers in a given cluster

LUN access control (masking)• Extremely important in heterogeneous SANs• Mis-configuration may cause data corruption

– Multiple standalone servers fight for a LUN– A cluster and a standalone server fight for a

LUN


Design Considerations

Number of storage controllers• Multipath• “Static” load balancing

RAID• Software - defined per partition• Hardware – defined per LUN

Profile of Data to be stored• Databases vs office apps

SBD Partition – separate LUN

SAN Booting


Design Considerations 2

Mapping Volumes to Pools• One to one

Mapping Pools to LUNs• One to one, many to one, one to many

Spread the workload (2N)

Pool Snapshots

NSS Pool / Volume features• Purge immediate, compression,

shredding• IO315 – “Understanding the New Novell

Storage Services Features in NetWare 6.5”

Question and Answer


General DisclaimerThis document is not to be construed as a promise by any participating company to develop, deliver, or market a product. Novell, Inc., makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc., reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All Novell marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.

No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of Novell, Inc. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability.

san design considerations hylton leigh senior consultant novell consulting, uk stuart thompson...

Documents