© 2007 EMC Corporation. All rights reserved. Virtualization Technologies Module 6.2

© 2007 EMC Corporation. All rights reserved.

Virtualization TechnologiesVirtualization Technologies

Module 6.2

© 2007 EMC Corporation. All rights reserved. Virtualization Technologies - 2

Virtualization Technologies

Upon completion of this module, you will be able to:

Identify different virtualization technologies

Describe block-level virtualization technologies and processes

Describe file-level virtualization technologies and processes


Lesson 1 – Virtualization – An Overview

Upon completion of this lesson, you will be able to:

Identify and discuss the various options for virtualization technologies


Defining Virtualization

Virtualization provides logical views of physical resources while preserving the usage interfaces for those resources

Virtualization removes physical resource limits and improves resource utilization


What Makes Virtualization Interesting

Potential Benefits:

Higher rates of usage

Simplified management

Platform independence

More flexibility

Lower total cost of ownership

Better availability

Server

Storagenetwork

Storage


Virtualization Comes in Many Forms

6

Each application sees its own logical memory, independent of physical memory

Virtual Memory

Each application sees its own logical network, independent of physical network

Virtual Networks

Each application sees its own logical server, independent of physical servers

Virtual Servers

Each application sees its own logical storage, independent of physical storage

Virtual Storage

© 2007 EMC Corporation. All rights reserved. Virtualization Technologies - 7 7

Each application sees its own logical memory, independent of physical memory

Virtual Memory


Benefits of Virtual Memory•Remove physical-memory limits•Run multiple applications at once

Physical memory

Swap space

App

App

App


Each application sees its own logical network, independent of physical network

Virtual Networks


Benefits of Virtual Networks•Common network links with access-control properties of separate links

•Manage logical networks instead of physical networks

•Virtual SANs provide similar benefits for storage-area networks

VLAN A VLAN B VLAN C

VLAN trunkSwitch Switch


Server-Virtualization Basics

Before Server Virtualization:

Operating system

Application

Single operating system image per machine

Software and hardware tightly coupled

Running multiple applications on same machine often creates conflict

Underutilized resources

After Server Virtualization:

Virtual Machines (VMs) break dependencies between operating system and hardware

Manage operating system and application as single unit by encapsulating them into VMs

Strong fault and security isolation

Hardware-independent: They can be provisioned anywhere

Virtualization layer

Operating system

App App App

Operating system

App App App


Check Your Knowledge

Define Virtualization

What type of virtualization has existed for many years at the storage layer?

What is a VSAN?

Explain the concept of a swap file

Explain the concept of server virtualization


Lesson 2 – Storage Virtualization


Identify and discuss the various options for virtualization technologies


Server

Storagenetwork

Storage

Volume management– LUNs

Access control Replication RAID Cache protection

Path management Volume management Replication

Connectivity

Storage Functionality Today

Intelligence Lives Primarily on Servers and Storage Arrays


Storage Virtualization Requires a Multi-Level Approach

Distributed intelligence / centralized management

Application functionsServer

Storagenetwork

Storage

Data-access functions

Data-preservation functions

Intelligence Should Be Placed Closest to What it Controls


SNIA Storage Virtualization Taxonomy

Storage

Virtualization

Block Virtualization Disk Virtualization

Tape, Tape Drive,

Tape Library

Virtualization

File System,

File/record

Virtualization

Other Device

Virtualization

Host based server

Based VirtualizationNetwork based Virtualization Storage Device Storage

subsystem Virtualization

In-band Virtualization Out-of-band Virtualization

What is created

How it is implemented

Where it is done:


Problem:

Current Storage Virtualization Examples

NAS Gateway

Consolidatedfile-based storage

Mgmt Station

NAS Heads

LANFile

Block Storagenetwork

Solution: MultiPathing Software

I/O path performanceand availability

Storage-Virtualization Examples


Four Challenges of Storage Virtualization

Scale:Virtualization technology aggregates multiple devices—must scale in performance to support the combined environment

Functionality:Virtualization technology masks existing storage functionality—must provide required functions, or enable existing functions

Management:Virtualization technology introduces a new layer of management—must be integrated with existing storage-management tools

Support:Virtualization technology adds new complexity into the storagenetwork—requires vendors to perform additional interoperability tests


The Scaling Challenge

Before:

Performance requirements are distributed across multiple storage arrays

– Application performance– Replication performance

Standard environment

Each array delivers units of performance(e.g., IOPS, SPEC-SFS, MB/s)

20,000 20,000 20,000 20,000 20,000


The Scaling ChallengeBefore:

Performance requirements are distributed across multiple storage arrays

– Application performance– Replication performance

After:

Storage network capabilities must support the aggregated environment

– Aggregate application performance

– Aggregate replication performance

Virtualized environment

Aggregated performance(e.g., IOPS, SPEC-SFS, MB/s)

100,000+

+ + + +20,000 20,000 20,000 20,000 20,000


The Functionality Challenge

Before:

Applications have access to rich array functionality

– Advanced local replication– Advanced remote replication– Array-level optimization


Advanced array functionality:

• Mirrors, clones, and snapshots

• Protected and instant restores

• Synchronous and asynchronous replication

• Consistency Groups


The Functionality ChallengeBefore:

Applications have access to rich array functionality

– Advanced local replication– Advanced remote replication– Array-level optimization

After:

Virtualization device must provide either required functionality

or

Specialized access to array functionality


Network functionality(depending on implementation)

Advanced array functionality:

• Mirrors, clones, and snapshots

• Protected and instant restores

• Synchronous and asynchronous replication

• Consistency Groups

?


The Management Challenge

Before:

Management tools provide integrated view of application to physical-storage mapping

– Monitoring and reporting– Planning and provisioning


End-to-end management


The Management ChallengeBefore:

Management tools provide integrated view of application to physical-storage mapping

– Monitoring and reporting– Planning and provisioning

After:

Storage network requiresmodification of management tools to support a virtualized environment

– Servers– Networks– Storage– … and virtualization device


Virtualization device

Server tovirtualization device

Virtualization deviceto physical storage


The Support Challenge

Before:

Storage vendor must support complexity of multi-vendor network environments

– Servers and software– Networks and software– Arrays and software


Interoperability: server types OS versions network elements storage-software products


The Support ChallengeBefore:

Storage vendor must support complexity of multi-vendor network environments

– Servers and software– Networks and software– Arrays and software

After:

Storage-virtualization vendor must provide additionalsupport to address increased complexity

– New platforms– New intelligence– Interaction with existing infrastructure


More complexity requires additional interoperability investments

Considerations:• New hardware-

qualification requirements

• Service and support ownership

• Problem escalation and resolution


Each application sees its own logical storage, independent of physical storage

Virtual Storage

Virtual Storage

Benefits of Virtual Storage•Nondisruptive data migrations

•Access files while migrating

• Increase storage utilization

Storage Virtualization:Block and File Level

Storagenetwork

IPnetwork


No state / no cache

I/O at wire speed

Full-fabric bandwidth

High availability

High scalability

Value-add functionality

Out-of-Band In-Band State / cache

I/O latency

Limited fabric ports

More suited for static environments or environments with less growth

Value-replace functionality

Comparison of Virtualization Architectures



What are the four challenges of storage virtualization?

At which level(s) is storage virtualization implemented?

Control data in the data path is a feature of what type of virtualization architecture?


Lesson 3 – Block-Level Virtualization


Describe Block-Level Virtualization technologies and functionality


Block-Level Storage Virtualization Basics

Ties together multiple independent storage arrays– Presented to host as a single storage

device

– Mapping used to redirect I/O on this device to underlying physical arrays

Deployed in a SAN environment

Nondisruptive data mobility and data migration

Multi-vendor storage arrays

Storage-area network (SAN)


Usage Scenarios for Block-level Storage Virtualization

HeterogeneousStorage

ApplicationGrowth

30© Copyright 2006 EMC Corporation. All rights reserved.

Next-Generation Data Center Operations

Extending Volumes

Online

Scalability

Consolidation

BusinessContinuity

StorageUtilization

Nondisruptive Data Mobility

Nondisruptive Data Mobility


After


VirtualizationSAN

Simplify volume access Nondisruptive mobilityOptimize resources

Block-Level Storage Virtualization

Optimizes Resources and Improves Flexibility

Before


SAN

All applications have direct knowledge of storage location


Data Mobility

How much data can you migrate on the weekend?

– Average migration rate using server-based copies is 4 GB per hour and with downtime

– At 48 hours of time per weekend, you can migrate 192 GB of data a week

With network-based virtualization, data canbe migrated at any time at much faster rates

Data mobility becomes a routine operation, making it a daily part

of infrastructure optimization


Block-Level Virtualization Example: EMC Invista

Intelligent Switches: Fibre Channel switches with custom hardware for enhanced processing

Capable of performing operations on data streams at line speed

Controlled by instructions from external management software (via APIs)

Inside the Intelligent Switch

Mapping

operation

Mapped I/O streams

Host Storage

Intelligent switch becomes storage target

Input I/O stream




Mapped I/O streams

Host Storage

Control Path Cluster—control path The CPC gets involved to make changes

(e.g., allocate more storage), handle uncommon cases (e.g., SCSI inquires, SCSI reservations), perform control operations (e.g., cloning), etc.

Intelligent switch—data pathControl processing

Invista Control Path Cluster (CPC)

Mappingoperation

Input I/O stream



Control processingInvista Control Path Cluster

(CPC)


Input I/O stream

Requests received and dispatched to assigned storage location

Host

Mapping

Operation

Mapped I/O streams

Storage

Mappingoperation

A new device is placed within the data center, and the CPC discovers the new device

The CPC creates the map and shows the host where the virtual volume exists; I/O begins

Contents of an existing volume are moved online, and the volume is freed



Consider that you have a leased storage array that is being replaced by a newer model. Place the relevant steps below in the correct order for data migration (hint: not all steps apply)– Reconfigure LUN definitions on hosts

– Implement new array into existing environment

– Decommission legacy array

– Obtain new array

– Take host volumes offline for migration

– Migrate existing data from legacy array to new array

– Present storage on new array to virtualization engine


Lesson 4 – File Level Virtualization


Describe File Level Virtualization technologies and functionality


Before File-level Virtualization:

File-Level Virtualization Basics

Every NAS device is an independent entity, physically and logically

Underutilized storage resources

Downtime caused by data migrations

NAS devices/platforms

IPnetwork

After File-level Server Virtualization:

Break dependencies between end-user access and data location

Storage utilization is optimized

Nondisruptive migrations

NAS devices/platforms

IPnetwork


After

Move data while writing and accessing existing data Update Global Namespace

Multi-vendor NAS systems

File VirtualizationIP

File-Level Storage Virtualization

File Abstraction that Optimizes Resources and Improves Flexibility

Multi-vendor NAS systems

Before

All users have direct knowledge of file locations

File systems


Automount

NIS LDAP

DFS

AD

Moving Files Online: A File Virtualization Example

NFS4 Root

NIS LDAP

Global Namespace

Manager

Event Log File Virtualization inserted

into I/O Client redirection

Global Namespace updated

File Virtualization Appliance

DFS

AD

Automount

NIS LDAP

Global Namespace

Manager

NFS4 root

NIS LDAPAdmin

File-datamigrationFile-datamigration


Moving Files Online: A File Virtualization Example (continued)

DFS

AD

NFS4 Root

NIS LDAP

Global Namespace

Manager

Event Log File virtualization inserted

into I/O Client redirection

Global Namespace updated Migration complete without

downtime

File Virtualization Appliance

Admin

File-datamigration

Automount

NIS LDAP


Usage Scenarios for File-Level Storage Virtualization



PerformanceManagement

Tiered StorageManagement

Consolidation

BusinessContinuity

Capacity Management

GlobalNamespaceManagement

Consolidation


Accelerated Consolidation

Move Files Nondisruptively—with Continuous Access to Data

After:

Eliminate servers via migration to underutilized servers

Maintain full read/write access during migration

Transparent to clients and applications

Before:

Too many file servers– Buying more file servers

for additional storage

Complex migrations

IP network File Virtualization

Server 1 Server 2 Server 3 Server 4

Averageutilization Eliminate

file servers

Increasedutilization


Usage Scenarios for File-Level Storage Virtualization



PerformanceManagement

Tiered StorageManagement

Consolidation

BusinessContinuity

Capacity Management




Global Namespace Management

Situation Billions of files with thousands to hundreds of thousands of clients

Update namespace and retain access to files while migrating

Scenario Update 1,000 client namespaces over the weekend

95% successful—50 typos or glitches

50 calls with 50 very angry employees

There goes Monday...and Tuesday

Wednesday: Start planning next set of changes

Zero mistypes, 100% access during migration

45


Simplified Namespace Management

Access to Files and Folders

Before:

Complex file-server environments

Namespace changes are time-consuming

Multiple shares or mounts per client

After:

Multiple file systems appear as a single virtual file system via standard namespace

Simplify management and ensure continuous access to files and folders

Updates standard-namespace entries (UNIX, Linux, Windows)

Server 1 Server 2 Server 3 Server 4

SHARE1WindowsT:\svr1\

SHARE2NetAppS:\svr2\

SHARE3CelerraH:\svr3\

SHARE4UNIXG:\svr4\



Name two benefits of file-level virtualization

What is a Global Namespace?


Module Summary

Key points covered in this module:

Virtualization technologies

Block-level virtualization technologies and processes

File-level virtualization technologies and processes


Course SummaryKey points covered in this course:

Challenges found in today’s complex information management environment

Storage technology solutions– DAS– NAS– SAN

Key business drivers for storage - Information Availability and Business Continuity

Business continuity, managing and monitoring the data center, storage security, and virtualization

Common storage management roles and responsibilities

Key themes – Technology Requirements– Physical and Logical Elements – Host – Interconnect – Storage – Data Flow– Storage Security


Closing Slide

Documents

© 2007 EMC Corporation. All rights reserved. Virtualization Technologies Module 6.2