You are on page 1of 41

SNIA-SA 100

Introduction to
Network Storage
Chapter 6
SAN Management

Version 1.1

1
© COPYRIGHTED 2004
Coverage
1. Illustration of SAN
2. Requirements of SAN Management
3. SAN Management Hierarchy
4. Management Software
5. Review Questions

2
© COPYRIGHTED 2004
Section 1

1. Illustration of SAN
2. Requirements of SAN Management
3. SAN Management Hierarchy
4. Management Software
5. Review Questions

3
© COPYRIGHTED 2004
Illustration of SAN
LAN/WAN
attached clients
LAN / WAN

Heterogeneo
us servers

SAN Fabric Management system


SWITCH SWITCH

Storage
Systems
Tape Library
Disks / RAID Optical Library
4
© COPYRIGHTED 2004
Section 2
1. Illustration of SAN
2. Requirements of SAN Management
3. SAN Management Hierarchy
4. Management Software
5. Review Questions

5
© COPYRIGHTED 2004
Requirements of SAN
Management
• Controlling SAN resources from a single point
• Monitoring the state of SAN
• Servicing a SAN
• Identifying and Resolving problems
• Preventive maintenance

6
© COPYRIGHTED 2004
Section 3
1. Illustration of SAN
2. Requirements of SAN Management
3. SAN Management Hierarchy
4. Management Software
5. Review Questions

7
© COPYRIGHTED 2004
SECTION 3: SAN Management
Hierarchy

3.1 Application Management


3.2 Data Management
3.3 Resource Management
3.4 Network Management
3.5 Element Management

8
© COPYRIGHTED 2004
SAN Management Hierarchy
3.1 Applications Management

3.2 Data Management

3.3 Resource Management

3.4 Network Management

3.5 Element Management


9
© COPYRIGHTED 2004
SAN Management Hierarchy
3.1 Applications Management

3.2 Data Management

3.3 Resource Management

3.4 Network Management

3.5 Element Management


10
© COPYRIGHTED 2004
SAN Management Hierarchy
1. Business process policy/SLA definition/execution
2. Resource optimization across business processes
layer 5 Applications Mgt 3. Application optimization, failover/fallback, scalability
End to End SAN Management

1. ‘real time’ copy (mirroring, remote copy,


layer 4 replication)
Data Mgt 2. ‘point-in-time’ copy ( snapshot)
3. Data sharing

1. capacity management & planning


layer 3 Resource Mgt 2. Resource attribution (policy) management
3. Storage sharing (disk & tape pooling).
4. Space management

1. Physical to logical mapping within SAN


layer 2 Network Mgt network
2. Zoning
3. Performance/availability of SAN network

1. Configuration, initialization, of storage devices.


layer 1 Element Mgt 2. Performance monitoring.
3. Authentication, authorization, security
11
© COPYRIGHTED 2004
Application Management
Deals with:

• Availability, performance and recoverability of applications.


• Service-Level Management and control in accordance with SLA.
• Resource optimization across business applications.
• Application Optimization,fail over/fail back.

12
© COPYRIGHTED 2004
SAN Management Hierarchy
3.1 Applications Management

3.2 Data Management

3.3 Resource Management

3.4 Network Management

3.5 Element Management


13
© COPYRIGHTED 2004
Data Management
• Ensuring data availability and accessibility for applications.

• Ensuring proper performance of data for applications.

• Ensuring recoverability of data.

• Management of:

• Point-in-time copy.(snapshot)
• Data Sharing.

• Hierarchical Storage Management (HSM)

• Information Lifecycle Management


14
© COPYRIGHTED 2004
Hierarchical Storage
Management (HSM)
• Deals with storage hierarchies.

• Data is classified according the their access frequency.

• Policy settings set by administrator.

• Less frequently accessed data are archived.

15
© COPYRIGHTED 2004
Hierarchical Storage Management
(cont’d)

Increasing
Faster response Availability
Active Data
(Cache/RAM Disk)

Recent historical
(Magnetic Disk)

Offline archival
(Tape/Optical Disk)
16
© COPYRIGHTED 2004
How HSM works
• A system administrator set file policies on the HSM engine.
• Files that fit the policy will be copied to a secondary storage
Catalogs are maintained in the disk
• Catalogs act as a pointer to the actual files, even if it has been moved
to another location.
• Examines the access for each administrator-defined set of file systems
• Migrate files that have been inactive for an administrator-defined period
• Migration consist of :
• Copying the file
• Update the file directory
• Reclaim the online space for use by other files

17
© COPYRIGHTED 2004
Information Lifecycle
Management
(ILM)

• Definition and Scope of ILM


• Policies, processes, practices, services and tools used to
align the business value of information with the most
appropriate and cost effective infrastructure from time
information is created through its final disposition.

Source http://www.snia.org/dmf
18
© COPYRIGHTED 2004
SAN Management Hierarchy
3.1 Applications Management

3.2 Data Management

3.3 Resource Management

3.4 Network Management

3.5 Element Management


19
© COPYRIGHTED 2004
Resource Management
• Automated management of existing storage and fabric resources.

• Automated corrections where necessary.

Addresses the following tasks:

• Storage Pooling ( Disk and Tape Pooling).

• Space Management.

• Capacity Management.

• Policy Management.

20
© COPYRIGHTED 2004
Storage Pooling
• Enables many physical volumes, the pool, to appear as one logical
target. Allows repurposing by shifting ownership from one server to
another.
• Example: DataCore SANSymphony.

Benefits
• Reduced capital cost .
• Greater ability to react to ad hoc demands, flexible.

21
© COPYRIGHTED 2004
Storage Pool- An Illustration
UNIX Windows Netware LINUX

Dedicated Storage SAN


Server for
management

HDS IBM Compaq

EMC
JBOD SCSI DELL
Storage Pool
22
© COPYRIGHTED 2004
Capacity Management
• Include volume management, both logical and physical.
• Logical unit number(LUN)configurations and disk capacities.
• Viewing common capacity metrics across a variety of storage
subsystems.
• Eg: IBM Storwatch Product.

23
© COPYRIGHTED 2004
Space Management
• Manage primary storage efficiently
• Delete unwanted data.

• Prioritize the usable space.

• Release unused allocated space.

• Eg: Tivoli Space Manager.

24
© COPYRIGHTED 2004
Space Management
-Illustration
Primary Level Large amount of free-space on
primary level maintained by
User Volumes
migrating old unreferenced
data

Migration
Data is compressed
Level 1

Migration Migrated data recalled to


Level 2 primary level when needed
25
© COPYRIGHTED 2004
Policy Management
• Policies represent the translation of business goals
to rules and actions.
• When rules and conditions are true, the policy actions
are executed.
• Policy Actions: some activity being performed or cessation of
activity.
• Reduces the complexity to manage SAN-based systems.
• Eg. IBM Storwatch.

26
© COPYRIGHTED 2004
SAN Management Hierarchy
3.1 Applications Management

3.2 Data Management

3.3 Resource Management

3.4 Network Management

3.5 Element Management


27
© COPYRIGHTED 2004
Network Management
• Deals with the Performance /Availability of SAN network
• Monitoring of network paths
• Maintenance of network components
• Control of logical SAN connections
• Authentication of clients
• Inventorying of network components
• Zoning

28
© COPYRIGHTED 2004
Zoning
• What is a Zone?
• A group of devices in a SAN that can communicate with and
access each other.
• Communication is allowed only between devices of the same
zone.
• Benefits of Zoning
• Segregate devices based on operating systems.
• Control access to multiple devices.
• Enhance network security.
• Concurrent testing and maintenance

29
© COPYRIGHTED 2004
Zoning – An Illustration
Solaris

NT HP-UX
Zoning

• Fulfill the SAN


Fabric any-to-any
connection
requirement

• Truly enable
NT Solaris HP-UX heterogeneous
Disks Disks Disks SAN.

30
© COPYRIGHTED 2004
SAN Management Hierarchy
3.1 Applications Management

3.2 Data Management

3.3 Resource Management

3.4 Network Management

3.5 Element Management


31
© COPYRIGHTED 2004
Element Management
• Elements that gets managed in SAN’s are:

• Storage Devices.

• SAN Infrastructure components.

• Servers.

• Environmental Software.

32
© COPYRIGHTED 2004
Storage Devices
• Disk & Tape Drives
• Device discovery
• Establishing & maintaining secure logical connections with
servers
• Fault detection and isolation

• RAID subsystems
• Management of spare and unused drive
• Array configuration.
• Soft failure recovery.

• Tape Libraries
• Management of removable media and unused media

33
© COPYRIGHTED 2004
SAN Infrastructure
Components
• Managing Hubs, Switches, Bridges,Routers and converters
include:

• Establishing and maintaining zones- sets of ports to


intercommunicate.

• Allocation of storage capacity to severs, applications and


users.

• Fault detection and recovery

• Asset tracking and maintenance.

34
© COPYRIGHTED 2004
Servers
• Server management includes:

• HBA management

• Fault detection and recovery(use redundant paths).

• Controls the logical connection between server and


storage devices.

• Asset tracking and maintenance.

35
© COPYRIGHTED 2004
Section 4
1. Illustration of SAN
2. Requirements of SAN Management
3. SAN Management Hierarchy
4. Management Software
5. Review Questions

36
© COPYRIGHTED 2004
Software Components
• Software Management includes:
• Revision and upgrading
• Patching, so as to function properly.
• Eg: Drivers, volume managers, cluster managers etc:

37
© COPYRIGHTED 2004
SAN Management Softwares –
Examples
• SANPoint fromVERITAS

• SANworks form Compaq

• Tivoli SAN Management Software from IBM

• SANSymphony from Datacore

38
© COPYRIGHTED 2004
Section 5
1. Illustration of SAN
2. Requirements of SAN Management
3. SAN Management Hierarchy
4. Management Software
5. Review Questions

39
© COPYRIGHTED 2004
Review Questions
• Explain SAN Management Hierarchy.
• What is Resource Management?Explain Storage Pooling and its
benefits.
• What is Zoning?
• List a few management software available in the market.

40
© COPYRIGHTED 2004
References
• http://www.otn.oracle.com/deploy/availability/htdocs/storage_ov
erview
• IBM Enterprise Storage Solutions Handbook
• Managing a Fibre Channel SAN – www.snia.org
• An Introduction to Zoning-www.McData.com
• IBM SAN survival guide

41
© COPYRIGHTED 2004

You might also like