SAN components
A SAN consists of the following hardware and software components:
+ Switches: A Fibre Channel switch creates the fabric of the SAN. By interconnecting switches, you can create scalable SANs with thousands of port connections.
+ Routers, bridges, and gateways: Router functionality provides high levels of scalability, dynamic device sharing, and Fibre Channel network fault isolation. Routers extend the SAN over long distances and enable integration of multiprotocol technologies.
+ Storage devices: A SAN can integrate multiple storage system types, such as disk arrays and tape libraries, to allocate storage efficiently.
+ Servers and HBAs: Host bus adapters (HBAs) connect the server to the SAN. HBA drivers provide an intelligent interface to the switches and minimize CPU overhead.
+ Cabling and cable connectors: Fiber optic cables provide the physical connections between SAN components.
+ SAN management applications: HP applications manage and monitor components and ensure optimal SAN operation.
A SAN consists of the following hardware and software components:
+ Switches: A Fibre Channel switch creates the fabric of the SAN. By interconnecting switches, you can create scalable SANs with thousands of port connections.
+ Routers, bridges, and gateways: Router functionality provides high levels of scalability, dynamic device sharing, and Fibre Channel network fault isolation. Routers extend the SAN over long distances and enable integration of multiprotocol technologies.
+ Storage devices: A SAN can integrate multiple storage system types, such as disk arrays and tape libraries, to allocate storage efficiently.
+ Servers and HBAs: Host bus adapters (HBAs) connect the server to the SAN. HBA drivers provide an intelligent interface to the switches and minimize CPU overhead.
+ Cabling and cable connectors: Fiber optic cables provide the physical connections between SAN components.
+ SAN management applications: HP applications manage and monitor components and ensure optimal SAN operation.
Comparing SAN and NAS
The main strengths of NAS are interoperability, lower total cost of ownership, and relative simplicity. Limitations of each solution are:
SAN limitations:
+ Up to 1,024 LUNs per Fiber Channel port
+ Up to 32 Fibre Channel ports per single storage subsystem
+ LUN sizes from 512KB to more than 2TB
+ Up to 16 million addressable ports
NAS limitations:
+ 64-bit file system architecture
+ Theoretical maximum file and file system size in the Petabyte range
+ Maximum LUN of 2TB
SAN limitations:
+ Up to 1,024 LUNs per Fiber Channel port
+ Up to 32 Fibre Channel ports per single storage subsystem
+ LUN sizes from 512KB to more than 2TB
+ Up to 16 million addressable ports
NAS limitations:
+ 64-bit file system architecture
+ Theoretical maximum file and file system size in the Petabyte range
+ Maximum LUN of 2TB
Design considerations
Before a design is complete consider the following factors:
+ Applications and operating systems — Can the current operating systems and applications accommodate the future expansion plans?
+ Availability — Is the current environment highly available, and is high availability a necessity for the customer?
+ Accessibility — Does the customer have employees who need remote access? Does the company need a firewall? Are there other security issues that need to be addressed?
+ I/O Profile — Is the current I/O profile adequate and if not how can it be improved?
+ Backup — What is the customer’s current backup process, if any? What can be done to address backup speeds and interruption?
+ Security — Are password expirations enforced? Is the network locked down?
+ Migration — Does the migration plan provide for minimal impact on uptime?
+ Applications and operating systems — Can the current operating systems and applications accommodate the future expansion plans?
+ Availability — Is the current environment highly available, and is high availability a necessity for the customer?
+ Accessibility — Does the customer have employees who need remote access? Does the company need a firewall? Are there other security issues that need to be addressed?
+ I/O Profile — Is the current I/O profile adequate and if not how can it be improved?
+ Backup — What is the customer’s current backup process, if any? What can be done to address backup speeds and interruption?
+ Security — Are password expirations enforced? Is the network locked down?
+ Migration — Does the migration plan provide for minimal impact on uptime?
+ Management — What management software will enable better SAN management?
Defining the infrastructure requirements
If a previous SAN exists, you can begin the design process by performing an inventory of the current environment. To provide the customer with a detailed growth plan, document
+ Inventory of current environment
+ Growth plan
+ Current storage configuration
+ LAN or SAN structure
+ Application uses
+ Traffic loads
+ Peak periods
+ Current performance
+ Inventory of current environment
+ Growth plan
+ Current storage configuration
+ LAN or SAN structure
+ Application uses
+ Traffic loads
+ Peak periods
+ Current performance
The HP StorageWorks SAN Design Reference Guide provides the detailed information you need to design a SAN that meets your unique storage system requirements.
To design an effective SAN, you must be familiar with:
To design an effective SAN, you must be familiar with:
+ SAN concepts
+ Products and rules
+ Combining products
+ Storage rules
+ Products and rules
+ Combining products
+ Storage rules
+ Operating system rules
+ Fabric rules
+ Zoning rules
+ Other rules
• Number of switches supported
• Types of switches supported
• Maximum number of hops supported
• Domain IDs and Worldwide Names needed
• Number of ISLs supported
+ Fabric rules
+ Zoning rules
+ Other rules
• Number of switches supported
• Types of switches supported
• Maximum number of hops supported
• Domain IDs and Worldwide Names needed
• Number of ISLs supported
0 comments
Post a Comment