KeepYourMission2cri4calApplica4onsUp andRunning24...

1

IA B13 Keep Your Mission-‐cri4cal Applica4ons Up and Running 24/7 in Hyper-‐V Environments

IA B13

Lisa Erickson Principal Product Manager Symantec

SYMANTEC VISION 2013 IA B13 2

Symantec’s Availability SoluFon for MicrosoH Hyper-‐V Ø OpFmize Data Availability Ø OpFons for ApplicaFon Availability Ø  Virtual Machine Disaster Recovery

q Demo: Disaster Recovery Manager

1

Agenda

Symantec’s Availability Roadmap for MicrosoH Hyper-‐V 2

SYMANTEC VISION 2013

Any informaFon regarding pre-‐release Symantec offerings, future updates or other planned modificaFons is subject to ongoing evaluaFon by Symantec and therefore subject to change. This informaFon is provided without warranty of any kind, express or implied. Customers who purchase Symantec offerings should make their purchase decision based upon features that are currently available.

3 IA B13

Disclaimer


Symantec’s Availability Solu4on for Hyper-‐V

IA B13 4


Solving Hyper-‐V Storage Management Challenges

IA B13 5

Flexible & Available Storage Management for Hyper-‐V Virtual

Machines

Simplified Online

Configura4on

Online Migra4on

Improve Performance

Op4mized Storage

Availability Access


Storage Founda4on value add func4onality available in Hyper-‐V host

•  Redundant & performance driven volume layouts

•  Online (re)configuraFon •  Online Storage MigraFon •  Thin Provisioning •  Autogrow, Capacity Monitoring •  Online Shrink, Site Awareness

Must adhere to base Live Migra4on limita4ons •  VHDs and VM configuraFon available on the

Target Node within the “Live MigraFon” Fmeout

SFW in parent requirements •  VHDs reside on SFW Volumes •  CSV not required/supported •  1 VM mapped to 1DG

VM-‐2

VM-‐3

VM-‐1

VM-‐3

memory content sync

VHD-‐3

disk group switch over

Live Migra4on

6 IA B13

Storage Founda4on – Hyper-‐V Live Migra4on Support


Ø  Install OpFon •  Within Storage FoundaFon

6.0 + for Windows “MicrosoH Failover Cluster” OpFon

Ø  Uninstall process •  Removing “MicrosoH

Failover Cluster” opFon •  Note: If “Live MigraFon

support” is configured, it should be un-‐configured before un-‐installaFon otherwise un-‐installaFon of the opFon will warn and fail

Configure Messaging Infrastructure between the

Cluster nodes

Create the VMDG resource and set the agribute

“LiveMigraFonSupport” to TRUE

Set the VM dependency on the VMDG Resource

Installa4on Configura4on Flow Launch the SFW Configura4on U4lity for Hyper-‐V Live Migra4on Support from SCC

7 IA B13

Storage Founda4on – Hyper-‐V Live Migra4on Support Prerequisites and Configura4on Process

•  Supported in SFW-‐HA 6.0 + •  DG version: 6.0 •  SCSI-‐3 support in mandatory

Prerequisites


AHer Failover Cluster is configured, from SoluFon ConfiguraFon Center (SCC) launch “ SFW Configura.on U.lity for Hyper-‐V Live Migra.on Support”

8 IA B13

•  Configura4on ID Unique ID 0 -‐ 65535 •  Port: Can change only for the first host •  System List: List of Failover Cluster nodes •  IP Address : UDP based LLT

communicaFon •  Configura4on Status

–  “Configured” -‐ Node already configured for LiveMigraFon –  “Non-‐Configured” – Node not configured for LiveMigraFon

•  (Re)configure Live MigraFon Support in following cases: •  First Fme cluster configuraFon •  Adding new node to the cluster •  Removing node from cluster •  Network changes (adapter, IP, port)

Configures GAB and LLT on cluster nodes

Storage Founda4on – Hyper-‐V Live Migra4on Support Configura4on Wizard


Seamless migra4on across arrays •  Move volumes containing VHDs to different arrays

VMs remain online •  Independent of backend storage •  Re-‐layout

Storage Migra4on Wizard •  VM centric -‐cChoose the VMs and moves all the storage to new target

SmartMove •  Copies only NTFS blocks containing data

NTFS VM

Array Migra4on

Array Type 2 Array Type 1

vhd1

OS

App

vhd2 vhd3 vol 1 vol2

$$$ $

Hyper-‐V Virtual Machine

SmartMove

9 IA B13

Storage Founda4on – Hyper-‐V Online Storage Migra4on


Host All Disk Groups Specific disk group

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

10 IA B13

Storage Founda4on – Hyper-‐V Storage Migra4on Wizard


•  Hyper-‐V Virtual Machines discovered

•  Select a Hyper-‐V Virtual Machine for migraFon

•  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


11 IA B13



•  Select subset or all target disks per volume

•  Wizard will display the available target disks

•  Wizard validaFon of the selecFon •  Checks for space, layout and site •  ValidaFon failures result in appropriate

error message

Next


12 IA B13



•  Summary informaFon

•  Click Finish to complete the operaFon

•  Task created per sub disk

•  Check progress of each sub disk task in Veritas Enterprise Administrator

Next


13 IA B13


Primary Site

Replicated Volumes

Windows Server Hyper-‐V Host

Storage Founda4on 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


VM 4_Vol1


Secondary Site

Replicate and recover volumes •  Contain all or selecFve data for one or more virtual machines – volumes that contain sys/boot and app data VHDs

Con4nuous

Synch, Asynch or Synch Override

Tunable – Packet size, Throhling

Key Requirements & Considera4ons •  SFW is storage mgmt in parent

• No CSV •  Enable SFW Live MigraFon support

•  VM Disk •  VHD/VHDX

•  VM Consistency •  Ensure all volumes containing VHDs for single VM are within same Replicated Volume Group

•  Recovery process •  To import, copy of export of VM properFes required or Create VM

14 IA B13

Veritas Volume Replicator Hyper-‐V Data Recovery or Long Distance Migra4on

VM1 VM2 VM3 VM4

Windows Server Hyper-‐V Host

Target Replicated Volumes

VM 1_Vol1

Sys/Boot VHDs

VM 1_Vol2

App Data VHDs

VM 2_Vol1


VM 3_Vol1


VM 4_Vol1


Storage Founda4on for Windows & Veritas Volume Replicator

VM1 VM2 VM3 VM4

Dynamic Mul4-‐Pathing Protect And Op4mize Hyper-‐V Server Storage Access Full Microsoi MPIO compliance

• CerFfied Device Specific Modules • All MPIO load balancing policies

Detailed path management Live Migra4on compliant Standalone is agnos4c to logical volume management AVID naming

• Bridge storage and server admins • Consistent names across severs

Aggregate I/O sta4s4cs • Group-‐by disk and array

Extended ahribute discovery • HW RAID • Thin Provisioned • Storage based replicaFon • Storage based snapshot/clone

15

Vendor B Disk Array

Vendor A Disk Array

Vendor C Disk Array

Vendor D Disk Array

DMP within Hyper-‐V Server

IA B13

c0t5d65 c1t5d65

c4t5d65 c3t5d65

AVID: 0AF4

EMC0_0AF4 EMC0_0AF4

LUN


Solving Applica4on Availability Challenges in Hyper-‐V Environments

IA B13 16

Resilient Applica4on Availability in Hyper-‐V Virtual

Machines

Deep insight into applica4on

health & dependencies

Dependable fast failover

Recovery Confidence

Ecosystem co-‐existence, integra4on and flexibility


Veritas Cluster Server in Hyper-‐V Guest Applica4on Insight and Fast Failure Detec4on

Solu4on –  Basic service monitor through user defined detailed

monitoring –  Includes infrastructure dependencies –  Intelligent Monitoring Framework -‐ real Fme monitor –  Interfaces with Agent Framework for registraFon and

relaying state change

Intelligent Monitoring Agent Support –  Exchange –  SQL –  Oracle, NetLsnr –  IIS –  Generic Service, Service Monitor, Process –  MountV, Mount, VMDg, IP, NIC, Registry ReplicaFon

Intelligent Monitoring Performance Benefit –  Reduced memory and processor overhead –  In some cases, processor usage dropped to 0%

High Availability Daemon (HAD)

Agent Framework

Resources Being Monitored

Registering…

Intelligent Monitoring Framework

Faulted

17 IA B13


Metro-‐area availability with Stretch Cluster

•  Redundancy throughout stack à Resilient to site failure

•  Agempt failover within site first (“System Zones”) •  Allocate storage at correct site (Site-‐aware Alloca4on) •  Mirroring over stretched SAN or Sync replicaFon over IP

Veritas Cluster Server in Hyper-‐V Guest Extensive Applica4on HA/DR Topology Support

SQL SQL

Asynchronous Replica4on

Mirroring or Replica4on

Primary Site Secondary Site <100km

RPO=0 RTO=near 0

Any Distance

Subnet A Subnet Z

APP 1 APP 3 APP 2 APP 4 APP 4 APP 1 APP 2 APP 3

Asynchronous Replica4on

Primary Site DR Site RPO=near 0 RTO=mins

Wide-‐area DR with Global Cluster

•  One click DR – Failover & Failback. Automates: –  reverse replicaFon à mount disks/volume à plumb IP on

different subnet à start app in dependency order à update DNS

•  Out-‐of-‐box agents for all major replicaFon technologies

SQL

Primary Site

RPO=0 RTO=near 0

Custom Single site availability with Local Cluster

•  Scale out – nodes & applicaFons

•  Restart or failover •  N:N failover


Primary Site

Volume Snapshot

Ini4ate Fire Drill Mount Snapshot

Replica4on

Test Applica4on Reset

Secondary Site

Simulate DR Failover

Test end to end recovery path –  Replicated data àserver à app

No Produc4on Impact –  SimulaFon done on DR site

–  Fire Drill Service Group – copy of producFon

–  Snapshot of replicated data –  RepersonalizaFon -‐ no IP conflicts

Easy to use –  Automated –  Wizard based setup and ongoing tests

Veritas Cluster Server in Hyper-‐V Guest Applica4on Centric DR Readiness Tes4ng


*From within guest has SCSI protocol support & no “shared” virtual adapter issue. Largely aligns to MicrosoH Hyper-‐V supportability stance

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

Virtual Fibre Channel (VFC)

iSCSI to guest/node

No-‐HA* Yes-‐Single node DR

20 IA B13






Yes Yes Yes

Yes Yes Yes

Veritas Cluster Server in Hyper-‐V Guest Storage Configura4on Support


Configura4on Area Configura4on Requirement or Considera4on

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

VHD Pass-‐through No VFC

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

iSCSI directly to guest (use MSFT iSCSI soHware iniFator in guest) VFC VHD\X for single node DR

Network for cluster communica4on vSwitch: 2 for private cluster communicaFon; bound to independent physical adapters; do not allow management operaFng system to interact

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

Requires operaFonal understanding, processes and configuraFon to manage Planned VM failovers:

•  Live MigraFon: Low risk as VM never inaccessible during process •  Quick MigraFon: VM inaccessible for short Fme due to pause and resume = failover of app in guest could start

• Move: VM inaccessible for longer period of Fme 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 aHer planned/unplanned

21 IA B13

Veritas Cluster Server in Hyper-‐V Guest Virtual Machine Configura4on Considera4ons

VM1

vSwitch1=Mgmt/Public vSwitch2=Cluster1 vSwitch3=Cluster2

Hyper-‐V Host 1

DAS storage (if no host VM HA for )

VM Sys/Boot

Storage Founda4on HA or Veritas Cluster Server

App1 (online)

iSCSI Ini4ator iSCSI Target

VM2


Hyper-‐V Host 2


App1 (offline)

iSCSI Ini4ator

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

SAN 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

22 IA B13

Veritas Cluster Server in Hyper-‐V Guest Blueprint: Local High Availability + iSCSI

VM1


Hyper-‐V Host 1

DAS storage (if no host VM HA for )

VM Sys/Boot


App1 (online)

VFC Adapter FC Storage

VM2


Hyper-‐V Host 2


App1 (offline)

VFC Adapter

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

SAN shared storage (if host clustering for VM HA)

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

OR OR


23 IA B13

Veritas Cluster Server in Hyper-‐V Guest Blueprint: Local High Availability + Hyper-‐V Virtual FC

VM1


Hyper-‐V Host 1

DAS storage (if no host VM HA)

VM Sys/Boot

App1 (online)

iSCSI Ini4ator

VM2


Hyper-‐V Host 2

App1 (offline)

iSCSI Ini4ator

SAN shared storage (if stretch host clustering for VM HA)

VM Sys/Boot

OR

Site A Site B

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


VM Sys/Boot SAN shared storage

(if stretch host clustering for VM HA) VM Sys/Boot

OR SFW Mirroring (if campus)

24 IA B13

Veritas Cluster Server in Hyper-‐V Guest Blueprint: Stretch Cluster + iSCSI


iSCSI Target 1



iSCSI Target 2


VM1


Hyper-‐V Host 1


VM Sys/Boot

App1 (online)

VFC Adapter

VM2


Hyper-‐V Host 2

App1 (offline)

VFC Adapter

SAN shared storage (if stretch host clustering for VM HA)

VM Sys/Boot

OR

Site A Site B

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



(if stretch host clustering for VM HA) VM Sys/Boot

OR SFW Mirroring (if campus)

25 IA B13

Veritas Cluster Server in Hyper-‐V Guest Blueprint: Stretch Cluster + Hyper-‐V Virtual FC


FC Storage



FC Storage


VM1

vSwitch1=Mgmt/Public vSwitch2=Cluster1

Hyper-‐V Host 1


VM Sys/Boot


App1 (online)

iSCSI Ini4ator

VM3


Hyper-‐V Host 2


App1 (offline)

iSCSI Ini4ator

SAN shared storage (if local host clustering for VM HA)

VM Sys/Boot

OR

iSCSI Target 1



iSCSI Target 2



(if local host clustering for VM HA) VM Sys/Boot

OR

VM level DR & App in-‐guest DR – poten4ally in conflict

26 IA B13

Site A Site B Local Failover

Wide Area Failover

VVR Asynch

Veritas Cluster Server in Hyper-‐V Guest Blueprint: Local HA + Wide Area DR + iSCSI

VM2

VM1


Hyper-‐V Host 1


VM Sys/Boot


App1 (online)

VFC Adapter

VM3


Hyper-‐V Host 2


App1 (offline)

VFC Adapter

SAN shared storage (if local host clustering for VM HA)

VM Sys/Boot

OR

FC Storage



FC Storage



(if local host clustering for VM HA) VM Sys/Boot

OR

27 IA B13

Site A Site B Local Failover

Wide Area Failover

VVR Asynch

VM level DR & App in-‐guest DR – poten4ally in conflict

VM2

Veritas Cluster Server in Hyper-‐V Guest Blueprint: Local HA + Wide Area DR + Virtual FC

VMNSDg Agent: • Works with Storage FoundaFon secondary disk group (bypasses reservaFon) • DR-‐only failover configuraFon, replicated applicaFon data could reside on VHD

28 IA B13

Veritas Cluster Server in Hyper-‐V Guest Applica4on Centric DR-‐only Configura4on


Solving Disaster Recovery Challenges in Hyper-‐V Environments

IA B13 29

Reliable & Flexible Hyper-‐V Virtual Machine

Disaster Recovery

Replica4on awareness &

control

End-‐to-‐end automa4on

Meet DR Recovery Point

& Time Objec4ves

Awareness, Integra4on & co-‐existence with Virtual Machine HA

SLA

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

Replica4on takeover/reversal

Monitor Replica4on X Import VM Config

Online VM

Network Update Network Updater

Network Updater

Command Devices/ LUN Access

Global cluster communica4on

VM Disk: VHD, Pass-‐through

Hyper-‐V Parent Storage: LDM, CSV, SFW

Physical Storage: EMC or Hitachi

Replica4on: HTC or SRDF

Co-‐exist with Microsoi Failover Cluster •  Failover Cluster provides VM HA (App & VCS Controller VM)

VCS Manager VM is the “brain” •  Global Clustering •  MonitorVMs & ReplicaFon Agents/Resources •  Import VMs •  Pushes Network updates to VMs

Re-‐personaliza4on via Network Updater Service •  App VM network configuraFon stored in file •  Network Updater Service in App VMs performs change

HTC and SRDF Replica4on Agent Support CSV or SF managed in-‐parent storage App VM Guest Support

•  Windows Server 2008/R2/2012, Vista, 7, 8 + IntegraFon Services

30 IA B13

Veritas Cluster Server Virtual Machine Disaster Recovery Disaster Recovery Manager for Hyper-‐V

31 IA B13

Veritas Cluster Server Disaster Recovery Manager Configura4on Wizard (6.0.1+)


Demo: Disaster Recovery Manager for Hyper-‐V Note: This posted presenta4on does not include the demo that was provided in the session. Please contact your Symantec Account Representa4ve if you are interested in seeing a demo of Symantec’s solu4on.

IA B13 32


Symantec’s Availability Roadmap for Microsoi Hyper-‐V

IA B13 33

Note: This posted presenta4on does not include the roadmap that was discussed in the session. Please contact your Symantec Account Representa4ve if you are interested in having discussions on Symantec’s roadmap for storage management, high availability and disaster recovery for Microsoi Hyper-‐V environments.


6.1 Beta Enrollment Star4ng!

IA B13 34

• Release focused upon Hyper-‐V storage management, HA and DR improvements

• Benefits –  1:1 feedback sessions – product team demonstraFons and usability tesFng

–  Hands on tesFng •  Interested?

–  Email: •  [email protected] or [email protected]

Thank you!

Copyright © 2013 Symantec Corpora4on. All rights reserved. Symantec and the Symantec Logo are trademarks or registered trademarks of Symantec CorporaFon or its affiliates in the U.S. and other countries. Other names may be trademarks of their respecFve owners. This document is provided for informaFonal purposes only and is not intended as adverFsing. All warranFes relaFng to the informaFon in this document, either express or implied, are disclaimed to the maximum extent allowed by law. The informaFon in this document is subject to change without noFce.

IA B13 35

Lisa Erickson [email protected]

Date post:	17-Jul-2020
Category:	Documents
Upload:	others
View:	4 times
Download:	0 times

KeepYourMission2cri4calApplica4onsUp andRunning24...

Documents