230 likes | 313 Views
Building a SAN for the Enterprise. Ken Hallam. Unisys Director of Technology. Storage Systems Engineering. The Ubiquitous Cloud. Looking At Storage In a New Way. As a Universal Data Resource In theory, anyone can attach to any stored data Eliminate bottlenecks, allow direct connections
E N D
Building a SAN for the Enterprise Ken Hallam Unisys Director of Technology Storage Systems Engineering
Looking At Storage In a New Way • As a Universal Data Resource • In theory, anyone can attach to any stored data • Eliminate bottlenecks, allow direct connections • Requires a new architecture • Global addressing structure • Global storage/data management • Gradual introduction • Change is never easy • Not all components are available today
Today’s Architecture Servers Storage Clients Channels LAN
The Back-up Issue Servers Storage Clients Channels LAN
The Replication Issue Servers Storage Clients Channels LAN
Complications • Heterogeneous Environment (Unisys) • 4 Different platforms • INTEL, SPARC, 2 Proprietary • 5 Different O/S Environments • NT, Win95, UNIX, 2 Proprietary • Common I/O Requirement • Move from SCSI + Block Mux to FC across all environments • Common support philosophy
Storage Area Network, (SAN) • Enabled by Fibre Channel • Relieves the LAN of storage management traffic • Eliminates bottlenecks • Switched environment • Global addressing • LAN no longer the path for backup • Allows all Data to become an Enterprise Resource • Data Storage no longer tied to specific channels and systems • Bridge to all Data Islands
The SAN Solution Servers Storage Clients SAN LAN
SAN Definition • Multiple paths to each resource • Any-to-any connections • Global Address view • Open structure using industry standard protocol • No node dependencies, (can function even if one or more nodes are inoperative) • Optimized for large block transfers • High bandwidth and high availability • Scales up with no performance loss
Backup or Replication Servers Storage Clients SAN LAN
“Architecture is not destiny.Implementation counts!” Gregory F. Pfister, IBM Corp.
Staged Implementation • Stage 1- Building Blocks • Replace channels with FC-AL, Hubs • Stage 2 - Basic SAN • Implement Topology (switches, global addressing) • Stage 3 - Intelligent SAN • Implement global management, dynamic allocation of storage • Stage 4 - Storage as a Utility • SAN implements policy, total data access, automated management
Stage 1 - Building Blocks • Replace Traditional Channels • FC-AL replaces SCSI Bus + Block Mux or ? • Similar host-peripheral assignments • Similar I/O drivers (some w/address restrictions) • Dual Port Use: • NT - Failover • Proprietary - Active/Active • Minimize risk, gain experience
Converter Converter Stage 1 FC Components clients server FC-AL Legacy Components LAN server FC-AL
Stage 2 - Basic SAN • Switch adds: • Multiple paths to each storage resource • Any-to-any connections • High bandwidth and high availability • Global addressing • Scales up with no performance loss • Shared storage • File locking and/or partitioning support • Leverages existing S/W
Converter Converter Stage 2 Management console server FC-Switch LAN server
Stage 3 - Intelligent SAN • Major Software Enhancements to SAN • Global management of all data • Dynamic resource allocation • Server no longer in path for Backup/restore • Automatic Discovery, Name Server • S/W Components in systems, servers and switches
Converter Stage 3 Management console server FC-Fabric LAN server
Stage 4 - Storage Utility • Storage like gas, water or electric utility service • Always there when you need it • Pay only for what you use • Universally accessible • SAN implements Policies and Procedures • Automated management of storage • Full security implemented • Frees up staff to focus on strategic issues
Stage 4 Management console server FC-Fabric LAN NAS
Switches Hubs NICs Routers LAN + WAN protocols Clients Manual management Optimize for small blocks Switches Hubs Host Adapters Converters SCSI Protocols Data Automate Policies and procedures Optimize for large blocks Network Cloud Vs SAN Cloud SAN Network
Summary • Implementation of SAN done in stages • Minimize risk • Preserve client investments • Maintain multiple platform interoperability • Gradual deployment of new architecture • Data becomes a universal utility for the enterprise