Using NAS as a Gateway to
SAN
Dave Rosenberg
Hewlett-Packard Company
825 14th Street SW
Loveland, CO 80537 [email protected]
Using NAS as a Gateway to
SAN
• Network Attached Storage (NAS) is a
purpose-built device (appliance) that presents file systems to client systems via a network. • A Storage Area Network (SAN) is a dedicated
network of interconnected storage and
servers that offers any-to-any communication between these devices and allows multiple servers to access the same storage device independently.
Using NAS as a Gateway to
SAN
• Can you connect a NAS device into a SAN so network clients get efficient file system
access to all that SAN storage?
Overview
• The need for storage is growing at an unprecedented rate.
• How to meet that need and keep IT budgets under control remains at the forefront for
most enterprise system managers.
• NAS and SAN are two technologies that can help.
NAS
• NAS devices are essentially dedicated
file servers.
• A NAS device consists of:
– Processor– Network interface – Disk storage
Benefits of NAS
• Multiple file system access (Heterogeneous):
– Windows (SMB/CIFS) – UNIX (NFS)
• Inexpensive implementation
– Ease of installation on the network – Ease of maintenance
• Protection against hardware failures • Embedded Virus protection
SAN
• SAN provides an efficient method for
linking storage systems.
• SAN consist of:
– Storage devices – Servers (Hosts)– HBA (Host Bus Adapters)
Benefits of SAN
• SAN allows scaling of storage to match individual server (user) needs.
– Can easily grow by attaching additional storage devices.
• Provide raw block level storage access. • Allow general purpose servers.
• Multiple vendors’ devices can be managed as a single storage pool.
SAN Architecture
FC-AL 9 8 7 6 5 4 3 21 10 11 12 13 14 15
VA CC B upgrade VA CC A
FC Int FC Host
PS + FanPS + Fan
VA7100 Array
363636 36 36 36 36 36 36 36 36 36 36 36 36
9 8 7 6 5 4 3 2
1 10 11 12 13 14 15
VA CC B upgrade VA CC A
FC Int FC Host
PS + Fan PS + Fan
VA7100 Array Windows Server UNIX Server SD
4567 891011 10/10 0 BASE T X
1 2
3
5 411 Ent erp ris e Switch POWER M GM T 45 6789 1 0 1111223333
3 R R 1000 BASE X AM BER = GREEN = F LASHING GREEN = ACT IVITY LINK OK DISABLED
S D HEWLETT PACKA RD S D HEWLETT P ACKARD LAN SAN S D
Profess ional Workst at ion 6000
PR O
S D
P rof essional Work st ation 6000
PR O
Storage Allocation
• Storage in a SAN is allocated to servers by Logical Unit Numbers (LUNS)
• Server Level Control
– Access governed at each SAN server
– Requires special software on each server
• Access Control Within the Network
– Managed within network switches by “zoning” port connections
Access Control Within the
Network
9 8 7 6 5 4 3 21 10 11 12 13 14 15
VA CC B upgrade VA CC A
FC Int FC Host
PS + Fan PS + Fan VA7100 Array
363636 36 36 36 36 36 36 36 36 36 36 36 36
9 8 7 6 5 4 3 2
1 10 11 12 13 14 15
VA CC B upgrade VA CC A
FC Int FC Host
PS + Fan PS + Fan VA7100 Array LUN 0
LUN 1
LUN 2 LUN 3
Visible LUNs: LUN 0, LUN 1 Visible LUNs: LUN 2, LUN 3
Windows Server
UNIX Server
SD
4 5 6 7 8 91011
10/100 BASE TX
1 2 3
5411 Enterprise Switch POWER MGMT
456789 10 11 1
12 23 33 3 3R R 1000 BASE X
AM BER = GREEN = FLASHING GREEN = ACTIVITY LINK OK DISABLED SD H EWLETT P ACKARD S D HEWL ETT PACKA RD
Ports 1 and 2 "Zoned"
Ports 5and 6 "Zoned" LAN
Storage Allocation
• Access Control Within the Storage
Array
– Most secure and flexible
– Access governed by storage array – Utilizes unique “World-Wide-Name”
– Requires “LUN masking” tables at each array
Access Control by the Storage
Array
FC-AL 9 8 7 6 5 4 3 21 10 11 12 13 14 15
VA CC B upgrade VA CC A
FC Int FC Host
PS + Fan PS + Fan VA7100 Array
363636 36 36 36 36 36 36 36 36 36 36 36 36
9 8 7 6 5 4 3 2
1 10 11 12 13 14 15
VA CC B upgrade VA CC A
FC Int FC Host
PS + Fan PS + Fan VA7100 Array LUN 0
LUN 1
LUN 2 LUN 3 Array 1 LUN Masking Table:
0x000011110000ABF0, LUN 0, WRITE
Array 2 LUN Masking Table:
0x000011110000ABF1, LUN 2, WRITE 0x000011110000ABF1, LUN 3, WRITE HBA WWN:0x000011110000ABF0
Visible LUNs: LUN 0
HBA WWN: 0x000011110000ABF1 Visible LUNs: LUN 2,LUN 3 Windows
Server
UNIX Server
SD
4567 891011 10/ 100 BA SE TX
1 2
3 5411 Ent erpris e S wit ch POW ER M GMT 4 5 6 7 8 9 10 1111223333
3 R R 1000 B AS E X AMBER = GREEN = FLA SHI NG GREE N = A CTIV ITY LINK OK DISA BLED
S D HEWLETT PAC KARD S D HEWL ETT PACKARD LAN
NAS and SAN Together
• Increasing volume requirements are pushing the bandwidth and performance limits of
traditional NAS.
• The net effect is a convergence of NAS and SAN technologies.
• The combining of NAS and SAN, referred to as “NAS/SAN fusion” allows IT managers to capitalize on the advantages of both
NAS/SAN Fusion
• NAS/SAN fusion results in significant benefit to IT managers and system users..
• The “head” of the NAS is used as a dedicated file server.
• The SAN becomes a pool of storage for use by the NAS head.
• Thus, the NAS head becomes a file level “gateway” into the SAN.
NAS/SAN Fusion
• General purpose servers placed on a SAN are either Windows or UNIX file system
based.
– NAS/SAN fusion provides both Windows and UNIX clients access to the same data.
• Backing up NAS can be difficult and is not always reliable.
– With NAS/SAN fusion, the backup of SAN-resident data is collectively controlled by the SAN. Backup is simpler.
How to Incorporate NAS Into
an Existing SAN
• Incorporating NAS into an existing SAN is not very different from adding any other server on a SAN.
• NAS just happens to be a server dedicated to file sharing.
• If you are converting a stand-alone NAS to operate on a SAN, you may need to add a Fiber Channel HBA to your NAS head.
How to Incorporate NAS Into
an Existing SAN (cont)
FC-AL 9 8 7 6 5 4 3 2
1 10 11 12 13 14 15
VA CC B upgrade VA CC A
FC Int FC Host
PS + FanPS + Fan
VA7100 Array
363636 36 36 36 36 36 36 36 36 36 36 36 36
9 8 7 6 5 4 3 2
1 10 11 12 13 14 15
VA CC B upgrade VA CC A
FC Int FC Host
PS + FanPS + Fan
VA7100 Array Windows Server UNIX Server SD
4567 891011 10/100 BASE TX
1 2
3
541 1 Ente rprise Switch PO WER MGM T 4 5 6 78 9 10 1 111223333
3R R 1000 BASE X AMBER = GREEN = F LASHING GREEN = ACTIVIT Y LINK OK DISABLED
S D
H EWL ET T PACKARD
SD
HEWL ET T PACKARD
LAN
SAN SD
Pr ofe ssion a l Wor ksta tion 6 000
PRO
SD
Profe ssio na l Wo rkst atio n 6 00 0
P RO
Client Workstatiopns
How to Incorporate NAS Into
an Existing SAN (cont)
• Identify LUNs to be allocated to NAS. • Use either network zoning or array LUN
masking to make LUNs available to the NAS device.
• Connect the NAS to the IP network and Fiber Channel.
• Configure the NAS on the IP network as defined by the manufacturer.
How to Incorporate NAS Into
an Existing SAN (cont)
• Configure the NAS Storage
• NAS should automatically “discover” LUNs allocated to it
• Create Volumes from LUNs
• Create Volume Groups from Volumes • Create File Systems across Volumes
• Expose File Systems as either Windows “Shares” or UNIX “Exports”
The Future of NAS/SAN
Fusion
• NAS and SAN management tasks are
segregated and require human oversight. • Market demand requires devices from
multiple manufacturers to coexist and be managed by a centralized Storage Area Manager.
• Several developers are moving towards
achieving this interoperability based on the “Common Information Model (CIM)”.