Deep Dive: Storage Optimization and High Availability in ......Hyper-V Storage Storage Attach Type •Network-attached storage (NAS) is not supported for Hyper-V (pre WS2012) •FC

Symantec Storage and Availability Management Group 1 Symantec Storage and Availability Management Group 1

Deep Dive: Storage Optimization and High Availability in Evolving Data Centers with Hyper-V, SSD and Windows 8

Paul Belk Director, Technical Product Management

Agenda

Hyper-V Technology Overview 1

Top Reasons for Symantec in Hyper-V Environments 2

Storage Requirements & Best Practices 3

VM Configuration Requirements & Considerations 4

HA/DR Design Blueprints 5

Symantec Storage and Availability Management Group 2

Roadmaps 6


Hyper-V Technology Overview

Hyper-V Storage

Storage Attach Type

• Network-attached storage (NAS) is not supported for Hyper-V (pre WS2012)

• FC to parent. Still bound by capability of VM’s virtual adapter & storage type

• Direct Attached to parent. Still bound by capability of VM’s virtual adapter & storage type

• iSCSI to parent. Still bound by capability of VM’s virtual adapter & storage type

• iSCSI to guest. Completely bypasses hypervisor

Virtual Adapter

• IDE: Up to two IDE controllers with two disks on each controller. Primarily used for boot.

• SCSI: Four SCSI controllers with each controller supporting up to 64 disks.

Virtual Disk (VHD)

• Stored as VHD file on NTFS

• On VM, appears as either an IDE or SCSI device independent of underlying storage presented to parent

• Types: Fixed, Dynamic, Differencing

• For Live Migration, VHD must exist on CSV (pre WS2012)

Pass-through (a Windows Physical Harddisk)

• Hyper-V pass-through bypasses parent’s file system and allows direct access by the guest

• Parent has to be aware of the disk. Must be offline on parent and online in guest

• Fully supported with Live Migration

4 Symantec Storage and Availability Management Group 4

Virtual Disk Type Details (VHD)

Type Characteristics Usage Recommendation

Fixed • Allocated size does not change

• I/O performance is highest

• Avoids write failures

• File format ensures consistency of data

• Recommended for production

Dynamic • Size of VHD keeps on expanding until it reaches a fixed maximum size

• It will not shrink if the data is deleted

• No check done of free space in the Parent Volume – expansion could fail

• Expansions are not transactional is nature – IO failures could lead to un-useable VHD

• In general, nonproduction/test

• Flexible use of disk space

• Faster transfer time when copying VHDs between locations

Differencing • Contains only the modified disk blocks of the associated parent VHD

• Parent VHD should be made Read-Only

• Must keep both files (the parent VHD and the differencing VHD) in the same directory on a local volume for native-boot scenarios

• Multi “chained” Differencing VHDs

• Boot image management

• Non production/test

5 Symantec Storage and Availability Management Group 5


Cluster Shared Volumes

VM-2

VM-3

VM-1

VM-3

C:\ClusterStorage\Volume1\

Live Migration

Meta Data IO - CreateFile, DeleteFile

VHDs

Owner

Data IO – Read & Write

Redirector

CSV not mandatory for Live Migration – can use pass-through

6

Benefits

• Can store all VM VHDs on one LUN

• All nodes have read/write access to file data

• VM movement between nodes

Disadvantages:

• Only basic disks supported

• Has had challenges in replicated environments

• IO Performance during Backup Windows


Disaster Avoidance - Migration

1. Configuration Data

2. Memory Content

3. Modified Memory Pages

Source Host Maintenance Host

Live Migration • Same site – FoC driven or standalone through SMB v3 (WS2012)

• Between site – FoC shared data stretch or SMB v3 (WS2012)

• For proactive administratively driven maintenance

Alternative Migration Scenarios • Quick Migration. Requires downtime = VM Pause>Migrate>VM Resume

• Move. Requires downtime = VM Save State>VM Shutdown>Move>VM Start


Disaster Recovery – Failover Cluster

VM HA Failover

Cluster Host 1 Cluster Host 2

Failover Cluster • Host fault & VM failover

• Local Site

• Between sites (shared data stretch cluster)

Alternative Scenarios • Failover Cluster + Hyper-V Replica (WS2012)

X


Top Reasons for Symantec in Hyper-V Environments


Top Reasons to Use Symantec in Hyper-V Environments

• Improve Storage Utilization

– CSV, by itself, does not support redundant layouts (need extra layer of virtualization to do this)

– Ease of storage movement/consolidation (subdisk move)

• Simplify Operations

– SmartMove

– Online storage migration for VMs; array migration

• Reduce Acquisition Costs

– Leverage existing storage hardware investment

– Consolidate storage management & multi-pathing into parent

• Enterprise class wide area DR

– Integration with existing enterprise replication investment

• Hardware independent stretch HA/DR

– Hardware agnostic mirroring across arrays with site awareness


Storage Managements Requirements & Practices


SFW in Parent - Hyper-V Live Migration Support

SFW must adhere to base Live Migration limitations:

• VHDs and VM configuration available on the Target Node within the “Live Migration” timeout

• VMs can be Live Migrated to nodes that are a part of FoC Cluster

SFW in parent requirements

• VHDs would lie on SFW Volumes

• CSV not required/supported

• 1 VM mapped to 1DG

All volume management functionality available

• Storage Migration

• Thin Provisioning

• Autogrow, Capacity Monitoring

• Online Shrink, Site Awareness

VM-2

VM-3

VM-1

VM-3

Memory Content sync

VHD-3

Disk Group switch over

Live Migration


SFW in Parent - Hyper-V Live Migration Config Process

• Supported in SFW-HA 6.0 +

• DG Version should be changed to 6.0

• SCSI-3 support in mandatory

• Install Option

• This feature is available with SFW 6.0 with “Microsoft Failover Cluster” option.

• Uninstall process

• Removing “Microsoft Failover Cluster” option

• Note: If “Live Migration support” is configured, it should be un-configured before un-installation otherwise un-installation of the option will warn and fail.

Configure Messaging Infrastructure between the

Cluster nodes

Create the VMDG resource and set the attribute

“LiveMigrationSupport” to TRUE

Set the VM dependency on the VMDG Resource

Installation Configuration Flow

Prerequisites

Launch the SFW Configuration Utility for Hyper-V Live Migration Support

from SCC


After FoC is configured, from Solution Configuration Center (SCC) launch

“ SFW Configuration Utility for Hyper-V Live Migration Support”

SFW in Parent - Live Migration Configuration Wizard

• Configuration ID Unique ID 0 - 65535

• Port Can change only for the first host

• System List List of nodes configured under FoC.

• IP Address : UDP based LLT communication

• Configuration Status

– “Configured” - Node already configured for LiveMigration

– “Non-Configured” – Node not configured for LiveMigration

• User needs to configure\reconfigure Live Migration in following cases:

• After configuring cluster first time.

• After adding new node to the cluster

• After removing node from cluster.

• Reconfigure in case of some network properties(IP\port) changes.

This wizard configures GAB & LLT on the selected nodes


SFW in Parent – Online Storage Migration for Hyper-V

• VMs remain online

• Equivalent to VMware Storage vMotion

• Seamless migration between arrays

• Move Volumes (on which the VHDs lie) to different arrays -online

• Storage Migration Wizard

• Choose the VMs and moves all the storage to new target LUNs

• SmartMove

• Ensures that SFW copies only the NTFS blocks that contain user data

NTFS VM

Array Migration

Array Type 2 Array Type 1

vhd1

OS

App

vhd2 vhd3

vol 1 vol2

$$$ $

Hyper-v Virtual Machine

SmartMove


localhost Disk Groups Individual disk group

SFW in Parent - Storage Migration Wizard for Hyper-V

Launch the Wizard Select the VM Select the Target Disk Finish & Track Progress


• Hyper-V Virtual Machines discovered

• User needs to select a Hyper-V Virtual Machine for migration

• All the volumes associated to the Hyper-V VM discovered & listed

• All VHDs on the volumes associated to the Hyper-V VM discovered & listed

Next




• Specify target disks per volume or for all the volumes in a single selection

• Wizard will display the possible target disks based on source volume(s) selection

• Selected target disks for each volume are displayed in Selected Disks table

• Backend validation by wizard of the selection

• Constraints like space, layout and site are checked

• Validation failures result in appropriate error message

Next




• Summary information

• Click Finish to complete the operation

• One task will be created per sub disk

• Check progress of each sub disk task in VEA bottom panel tasks tab

Next

SFW Hyper-V Storage Migration Wizard



DMP in Hyper-V Environments

VMBus

Hyper-V Aware Windows Server

Parent Partition Child Partition

Hyper-V Aware Windows Client

Kernel

Device Drivers

Virtualization Service Client (VSC)

Hypercall API

Hyper-V Hypervisor

Hardware

Kernel

Device Drivers

Virtualization Service Provider (VSP)

Hypercall API

`

Microsoft

Hardware vendor

Symantec

File System

SFW

SCSI FullPort/Miniports

Disk

Storport

DSM DSM DSM DSM

LDM

Multipath I/O

SCSIport

StorPort Miniports

Kernel Mode

Cluster Shared Volumes (CSV) Live Migration


Storage Configuration for VMs with SFWHA/DR in Guest

*“Shared VHDs” are not supported for in guest clustering purposes. Access to VHD file on NTFS from within guest does not support SCSI protocol & no “shared” virtual adapter concept **Largely due to general Microsoft supportability stance. & own qualifications

Storage type Clusters on One Physical Machine (Cluster in a Box)

Cluster Across Physical Machines (Cluster Across Boxes)

Clusters of Physical and Virtual Machines (Standby Host Clustering)

Virtual disks (VHD)

Pass-through

iSCSI to guest/node

No-HA* Yes-Single node DR

No-HA* Yes-Single node DR

No-HA Yes-Single node DR

No-HA** Yes-Single node DR



Yes Yes Yes


VM Configuration Requirements & Considerations


Configuring Virtual Machines for SFWHA/DR

Consideration Description

Storage Support – VM sys/boot (based on Hyper-V supportability)

VHD Pass-through

Storage Support – VM shared app data (based on Hyper-V supportability)

Must by-pass hypervisor (Hyper-V virtual SCSI controllers do not have SCSI-3 support) Has to be iSCSI directly to guest today (use MSFT iSCSI software initiator in guest)

Network for cluster communication vSwitch: 2 for private cluster communication; bound to independent physical adapters; do not allow management operating system to interact

Co-existence with host based clustering (for VM HA)

Overall, can be tricky and requires operational understanding, processes and configuration to manage. Planned VM failovers:

• Live Migration: Low risk as VM never inaccessible during process • Quick Migration: VM inaccessible for short time due to pause and

resume = failover of app in guest could start • Move: VM inaccessible for longer period of time due to save

state>shutdown>move>start = failover of app in guest • For planned outage maintenance, failover app before VM movement

Unplanned VM: failover of app in guest will occur • Ensure failover target VMs NOT on same host (preferred/possible owners) • Checking app and in guest cluster status after planned/unplanned


Bring It All Together: HA/DR Design Blueprints


SFWHA in Hyper-V Guest - Local HA

VM1

vSwitch1=Mgmt/Public vSwitch2=Cluster1 vSwitch3=Cluster2

Hyper-V Host 1

DAS storage (if no host VM HA for )

VM Sys/Boot

SFWHA

App1 (online)

iSCSI Initiator iSCSI Target

VM2


Hyper-V Host 2

SFWHA

App1 (offline)

iSCSI Initiator

DAS storage (if no host VM HA) For VM Sys/Boot

Shared storage (if host clustering for VM HA)

(SFW or CSV>VHD or Pass-through for ) VM Sys/Boot

OR OR

Shared Storage App Data


SFWHA in Hyper-V Guest - Stretch Cluster

VM1


Hyper-V Host 1

DAS storage (if no host VM HA)

VM Sys/Boot

SFWHA

App1 (online)

iSCSI Initiator

VM2


Hyper-V Host 2

SFWHA

App1 (offline)

iSCSI Initiator

Shared storage (if stretch host clustering for VM HA)

VM Sys/Boot

OR

iSCSI Target 1


Site A Site B


iSCSI Target 2

SFW Mirroring (if campus) or VVR (if RDC)


VM Sys/Boot

Shared storage (if stretch host clustering for VM HA)

VM Sys/Boot

OR SFW Mirroring

(if campus)


SFWHA in Hyper-V Guest – HA + DR

VM1

vSwitch1=Mgmt/Public vSwitch2=Cluster1

Hyper-V Host 1


VM Sys/Boot

SFWHA

App1 (online)

iSCSI Initiator

VM2

vSwitch1=Mgmt/Public vSwitch2=Cluster1

Hyper-V Host 2

SFWHA

App1 (offline)

iSCSI Initiator

Shared storage (if local host clustering for VM HA)

VM Sys/Boot

OR

iSCSI Target 1



iSCSI Target 2

VVR Asynch


VM Sys/Boot

Shared storage (if local host clustering for VM HA)

VM Sys/Boot

OR

VM level wide area DR would be in “conflict” with

In guest DR

Site A Site B


SFWHA in Hyper-V Guest – Single Node GCO (6.0.1)

VMNSDg Agent:

•Works with SFW Secondary Disk Group (avoiding reservation that cdg requires)

•Hyper-V VM storage for apps can now be “non-shared” – VHD (use case=single node app DR in guest)


VM Replication Only DR – SFW + VVR in Parent

Primary Site

VM 1

Replicated Volumes

VM 2 VM 3 VM 4

Windows Server 2008/R2 – Hyper-V

Physical Server

Storage Foundation for Windows –

Veritas Volume Replicator

VM 1_Vol1

Sys/Boot

VHDs

VM 1_Vol2

App Data

VHDs

VM 2_Vol1

Sys/Boot/

App Data

VHDs

VM 3_Vol1

Sys/Boot/

App Data

VHDs

VM 4_Vol1

Sys/Boot/

App Data

VHDs

Secondary Site

VM 1

Target Replicated Volumes

VM 2 VM 3 VM 4

Windows Server 2008/R2 – Hyper-V

Physical Server

Storage Foundation for Windows –

Veritas Volume Replicator

VM 1_Vol1

Sys/Boot

VHDs

VM 1_Vol2

App Data

VHDs

VM 2_Vol1

Sys/Boot/

App Data

VHDs

VM 3_Vol1

Sys/Boot/

App Data

VHDs

VM 4_Vol1

Sys/Boot/

App Data

VHDs

• Replicate and recover volumes that

• Contain selective virtual machines

• Contain all virtual machines

• Contain all data or selective data for a virtual machine – volumes that contain sys/boot VHDs vs. app data VHDs

VMs remain offline/not attached at

secondary site until recovery event

• Key Requirements/Considerations • SFW is storage mgmt in parent

• No CSV • Enable SFW LM support

• VM Disk • VHD

• VM Consistency • Ensure at least all volumes

containing VHD’s for single VM are within same RVG

• Recovery process • To import, copy of export of VM

properties required. Otherwise, it is rebuild VM>rebuild VM


Cluster-level VM DR – VCS Hyper-V DR Manager

VCS VM

VM VM

Failover Cluster Provides VM HA

Replicated VM Data VM Data

VCS MonitorVMs

agent

VCS VM

VM VM

Failover Cluster Provides VM HA

Replication takeover/reversal

Monitor Replication X

Import VM Config

Online VM

Network Update Network Updater

Network Updater

Command Devices/ LUN Access

Global cluster communication

VM Disk: VHD, Pass-through

Hyper-V Parent Storage: LDM, CSV, SFW

Physical Storage: EMC or Hitachi

Replication: HTC or SRDF

• Co-exist with Microsoft Failover Cluster – FoC provides VM HA (App & VCS Controller VM)

• VCS Manager VM is the “brain” – GCO

– MonitorVMs & Replication Agents/Resources

– Import VMs

– Pushes Network updates to VMs

• VCS Network Updates of App VMs – App VM network configuration stored in file

– Network Updater Service in App VMs performs change

• HTC and SRDF Replication Agent Support

• CSV or SFW managed in-parent storage

• App VM Guest Support – Windows Server 2008/R2, Vista, 7 + Integration Services installed

30


VCS DR for Hyper-V Virtual Machines Config Wizard (6.0.1)


Roadmaps


Customer Trends

• Increasing VM (& app) consolidation ratio

• Storage growth, Increasing LUN sizes

• Create, delete, migrate of VMs & storage

• Adjust storage infra for evolving app needs

Storage Related Challenges & Directions in Windows Env

VM VM VM VM VM VM VM VM VM

VM VM VM VM VM VM

VM

VM

VM

VM

VM

VM VM VM VM

VM

VM

VM

Storage Efficiency

I/O Performance

Storage Pooling

Application Awareness

Windows Storage Mgmt Directions

App App App App App App App App App App App

VM VM VM VM VM VM VM VM VM

IO Bottlenecks

Ap

p-S

tora

ge

Alig

nm

en

t

VM

Disclaimer : This forward-looking indication of plans for products is preliminary, and is subject to change. Any future release of the product or planned modifications

to product capability or functionality are subject to ongoing evaluation by Symantec, and may or may not be implemented.


RW

Shared DG

Storage Pooling for Windows Physical & Hyper-V Env

RW

VM

VM

VM

VM

VM

VM

VM

RW RW

Pooled Storage + Granular Access

5.1SP2

• 5.1 SP2: VM storage mgmt from parent

‒ DMP

‒ Quick migration

‒ TP/R

‒ Replication

‒ Snapshot

‒ Online operations (eg. grow, shrink)

‒ Capacity monitoring

‒ Auto-grow

Future Direction

• VHDs on SFW volumes; co-exist with CSV

• Better storage utilization with lower management overhead

• All storage mgmt features ‒ Storage Migration, Thin Provisioning

‒ Autogrow, Capacity Monitoring

‒ Online Shrink, Site Awareness

SFW

Hyper-V Parent

VM2

SPS

VM1

SQL

6.0

• 6.0: VM and Storage Live Migration

• Shared DG accessible from multiple nodes

• Provision logically related VMs on same storage pool (DG)

RO RO




I/O Performance with SSD Optimization

• CPU vs. HDD gap & ‘I/O blender’ limits virtualization

• CPU = 175x vs. HDD IO = 1.3x

• IOs reach the spindles in a random fashion

• Gets worse with higher # of apps or VMs per LUN

I/O Challenge x86 Virtual

• SSDs $30/GB->$2/GB (08-11)

• TCO much lower than HDD

• $ /IOPS better for SSDs

• Better “write endurance” & lower write perf issues

1. SSD discovery and reporting

2. SSD-aware storage operations - Volume create/grow/mirror - Storage/array migration - Preferred Read from SSD - etc.

3. Read-cache

4. Write-cache

Future Direction

Time

Pe

rfo

rman

ce

CPU

HDD

Source: Storage IO Group

VM VM VM SSD

SSD (Disk) SSD (Disk)

Cache Cache

SFW SFW

SSD (Cache) SSD (Cache)

RW RW






Application-aware Storage Management

• Even with faster storage, IO performance from an application perspective may still not be optimal

• Poor storage layout, caching, etc. from application perspective

• Unintended resource starvation for high priority applications

• Inefficient operations without insight into app data eg. replicating irrelevant data

• Need application intelligence for IO performance and storage efficiency

SPS SQL EXC SAP ORA

Challenges without application-awareness Future Direction

• Application-specific performance optimizations, eg. application hints for caching

• IO prioritization among applications

• App or VM awareness & granularity, eg. file replication for DR to cloud




Storage Management on Windows Future Directions

I/O Performance

• SSD discovery & reporting

• SSD-aware allocation and IOs

• Leverage SSD as a cache

Application-aware Storage

• Application-specific performance optimizations

• IO prioritization among applications

• Application/VM level granularity

Cost-effective, Resilient Storage

• Storage pooling for Hyper-V

• Granular access enabling multiple VMs per LUN

• All major storage management features for Hyper-V VMs

SFW

Hyper-V Parent

VM2

SPS

VM1

SQL

This information is about pre-release software. Any unreleased update to the product or other planned modification is subject to ongoing evaluation by Symantec and

therefore subject to change. This information is provided without warranty of any kind, express or implied. Customers who purchase Symantec products should make their

purchase decision based upon features that are currently available.

SPS SQL EXC SAP ORA




HA/DR Challenges & Strategy in Windows Data Centers

VM VM VM VM VM VM

VM

VM

VM

VM VM

Primary Site DR Site

VM VM

Cloud

Shared Infrastructure

Application Placement

Get smarter about app & ecosystem

Cloud Automation

Support cloud operational model

Disaster Recovery Next

Cost-effective, easy to use, reliable DR

Minimize downtime; detect potential failures

Make clustering more reliable

Make clustering easy to deploy Rigid DR workflows

DR to public cloud




Symantec ApplicationHA for Microsoft Hyper-V

• App monitoring

– ApplicationHA in Guest

– Instant fault detection

– Deep Insight into apps: DB queries/transaction success, performance, dependent resources

• Coordinated monitoring & remediation

– Integration via new MSFT app monitoring API

– App availability coordination from standalone, failover, through DR

• Visibility & Manageability

– ApplicationHA Console

– Target in context manageability with SC VMM

• Recovery or Proactive remediation

– Recovery – app restart, VM restart, failover, image recovery based on failures

– Proactive – migrate based on trends toward service loss; workload close to exceeding capacity

• Application Agent Supportability

– SQL, Exchange, SAP, File, Print, IIS, Custom, etc

VM 1

Hyper-V Integration

Services

VM 2

Hyper-V Integration

Services

Hyper-V Hosts (Failover Cluster or Standalone)

ApplicationHA ApplicationHA

SQL Custom

ApplicationHA Host Service

This information is about pre-release software. Any unreleased update to the product or other planned modification is subject to ongoing evaluation by Symantec and therefore subject to change. This information is provided without warranty of any kind, express or implied. Customers who purchase Symantec products should make their purchase decision based upon features that are currently available.

Application Restart

Virtual Machine Restart

Virtual Machine Failover

Virtual Machine Migrate

Virtual Machine Image Recovery




Disaster Recovery as a Service on Azure

On-Premise Data Center

Storage Foundation HA for Windows

VM • Secure Connection

• Global Clustering

• Replication

VM

• Site failure

• Compute failures

• Storage failures

• Network failures

• Software component

failures

• Maintenance/change

failures

Protection against common failures

• Recovery of end-to-

end DR process

• Replication->Storage-

>VM->Network->App

• DR testing without

impact on production

• "One click" failover and

failback

DR automation and reliability




HA/DR on Windows Future Directions

Cloud Automation

• Template-based deployment

• Integration with cloud frameworks

• HA service levels in stateless environment


• App failover for VMware environments

• ApplicationHA for Hyper-V

• Deep application insight

• Ecosystem awareness

• Failover readiness


• Cost-Effective, Resilient & Easy-to-use

• Hyper-V DR ease-of-use

• Coordinated DR with FOC and SRM

• A/A DR with site re-purpose

• DRaaS: low cost DR to cloud

Primary

Cloud

DR




HA/DR on Windows Future Directions

Presentation Identifier Goes Here 42

Cloud Automation

• Template-based deployment

• Integration with cloud frameworks

• HA service levels in stateless environment


• App failover for VMware environments

• ApplicationHA for Hyper-V

• Deep application insight

• Ecosystem awareness

• Failover readiness


• Cost-Effective, Resilient & Easy-to-use

• Hyper-V DR ease-of-use

• Coordinated DR with FOC and SRM

• A/A DR with site re-purpose

• DRaaS: low cost DR to cloud

Primary

Cloud

DR







Q & A

Paul Belk

[email protected]

44

Thank You

Documents

Deep Dive: Storage Optimization and High Availability in ......Hyper-V Storage Storage Attach Type •Network-attached storage (NAS) is not supported for Hyper-V (pre WS2012) •FC