whats new in vsphere 5 and srm 5 varrow branded1

8/3/2019 Whats New in Vsphere 5 and Srm 5 Varrow Branded1

http://slidepdf.com/reader/full/whats-new-in-vsphere-5-and-srm-5-varrow-branded1 1/62

vSphere 5.0 – What‘s New And some on SRM 5 too…



©2009 Varrow, Inc. - CONFIDENTIAL

Licensing – Get it out of theway.




Based on Annual Average




In 2011, VMware is Introducing a Major Upgrade of the Entire CloudInfrastructure Stack…

vCloud Director

vSphere

vShield Security

vCenter Management

vCloud Director 1.5

vSphere 5.0

vShield 5.0

SRM 5.0

Cloud Infrastructure Launch

New




Agenda

vSphere 5.0 What’s New?

Image Builder & Auto Deploy

Welcome

vSphere Core

What‘s New in Availability

Storage Enhancement

Platform Enhancements

Networking Enhancement

vSphere Storage Appliance (VSA)

What‘s New in vCenter Server

CLI



vSphere Core

Confidential




vSphere 5.0 CLI Components – ESXi Shell

• Rebranded Tech Support Mode• Local and remote (SSH)

– vCLI• ‗esxcli‘ Command Set

– Local and remote CLI – New and improved in 5.0

• ‗vicfg‘ Command Set – Remote CLI Only

• Other Commands: – vmware-cmd, vmkfstools,

etc.• vCLI available for Linux and

Windows

– vMA• vCLI Appliance

– PowerCLI• Windows CLI Tool

ESXiShell

vCLI

vMA PowerCLI




ESXi Command Line

esxcli

fcoe hardware iscsi license Network

fence Firewall

set load get refresh unload

ip vswitch nic

software storage system vm




Composition of an ESXi Image

CIMProviders

Drivers

CoreHypervisor

Plug-inComponents




Describing ESXi Components

• VIB – ―VMware Infrastructure Bundle‖

– Software packaging format used for ESXi• Often referred to as a ―Software Package‖

– Used for all components• ESXi Base Image

• Drivers

• CIM providers

• Other components

– Can specify relationship with other VIBs• VIBs that it depends on

• VIBs that it conflicts with




What is Auto Deploy•New host deployment method introduced in vSphere

5.0• Based on PXE Boot• Works with Image Builder, vCenter Server, and Host

Profiles• How it works:

• PXE boot the server• ESXi image profile loaded into host memory via Auto DeployServer

• Configuration applied using Answer File / Host Profile• Host placed/connected in vCenter

• Benefits

• No boot disk• Quickly and easily deploy large numbers of ESXi hosts• Share a standard ESXi image across many hosts• Host image decoupled from the physical server

• Recover host w/out recovering hardware or having to restorefrom backup




AutoDeploy

Depots

Auto Depoy Example – Initial Boot

OEM VIBs

DriverVIBs

ESXiVIBs

RulesEngine

―Waiter‖

Provision new host

ImageProfile

ImageProfile

ImageProfile

vCenter Server

Host ProfileHost Profile

Host Profile

TFTP DHCP




AutoDeploy

Depots


OEM VIBs

DriverVIBs

ESXiVIBs

RulesEngine

―Waiter‖

1) PXE Boot server

ImageProfile

ImageProfile

ImageProfile

vCenter Server


Host Profile

TFTP DHCP

DHCPrequest

gPXEimage




AutoDeploy

Depots


OEM VIBs

DriverVIBs

ESXiVIBs

RulesEngine

―Waiter‖

2) Contact Auto Deploy Server

ImageProfile

ImageProfile

ImageProfile

vCenter Server


Host Profile

Cluster A Cluster B




AutoDeploy

Depots


OEM VIBs

DriverVIBs

ESXiVIBs

RulesEngine

―Waiter‖

ImageProfile

ImageProfile

ImageProfile

vCenter Server


Host Profile

3) Determine Image Profile, Host Profile and cluster

•Image Profile X •Host Profile 1•Cluster B

Cluster A Cluster B




AutoDeploy

Depots


OEM VIBs

DriverVIBs

ESXiVIBs

RulesEngine

―Waiter‖

ImageProfile

ImageProfile

ImageProfile

vCenter Server


Host Profile

4) Push image to host, apply host profile

Cluster A Cluster B

Image Profile Host Profile

cache




AutoDeploy

Depots


OEM VIBs

DriverVIBs

ESXiVIBs

RulesEngine

―Waiter‖

ImageProfile

ImageProfile

ImageProfile

vCenter Server


Host Profile

5) Place host into cluster

Cluster A Cluster B


cache




AutoDeploy

Depots

Auto Depoy Example –subsequent reboot

OEM VIBs

DriverVIBs

ESXiVIBs

RulesEngine

―Waiter‖

Reboot Auto Deploy Host

ImageProfile

ImageProfile

ImageProfile

vCenter Server


Host Profile

TFTP DHCP


cache




New Virtual Machine Features• vSphere 5.0 supports the industry‘s most capable virtual machines

Other newfeatures

VM Scalability

Broader DeviceCoverage

32 virtual CPUs per VM

Client-connected USBdevices

USB 3.0 devices

Smart Card Readers forVM Console Access

UI for multi-core virtualCPUs

Extended VMwareTools compatibility

1TB RAM per VM 4x previous capabilities!

Support for Mac OS Xservers

Richer DesktopExperience

3D graphics

VM BIOS boot order config APIand PowerCLI interface

EFI BIOS

Items which require HW version 8 in Italics



What‘s New in vCenter Server

Confidential




Current Use Case

•The vSphere Web Client is tailored to met the needs of VM

Administrators in the first release. This includes: – VM Management

• VM Provisioning

• Edit VM, VM power ops, Snapshots, Migration

•

VM Resource Management• View all vSphere objects (hosts, clusters, datastores, folders, etc)

– Basic Health Monitoring

– Viewing the VM console remotely

– Search through large, complex environments

• Save search queries, and quickly run them to find detailed information

– vApp Management

• vApp Provisioning, vApp Editing, vApp Power Operations




Component Overview

Distribution Min Deployed Max Deployed

3.6GB ~5GB ~80GB

•vCenter Server Appliance (VCSA) consists of: – A pre-packaged 64 bit application running on SLES 11

• Distributed with sparse disks• Disk Footprint

• Memory Footprint – A built in enterprise level database with optional support for

a remote Oracle databases. – Limits are the same for VC and VCSA

• Embedded DB

– 5 hosts/50 VMs• External DB – <300 hosts/<3000 VMs (64 bit)

– A web-based configuration interface




Configuration•Complete configuration is possible through a

powerful web-based interface!



What‘s New in Availability

Confidential




Release Enhancement Summary

Complete re-write of vSphere HA

Provides a foundation for increased scale andfunctionality Eliminates common issues (DNS resolution)

Multiple Communication Paths Can leverage storage as well as the mgmt network for

communications Enhances the ability to detect certain types of failures and

provides redundancy

IPv6 Support

Enhanced Error Reporting One log file per host eases troubleshooting efforts

Enhanced User Interface Enhanced Deployment Mechanism




vSphere HA Primary Components

vCenter

ESX 02

ESX 01 ESX 03

ESX 04

•Every host runs an agent – Referred to as ‗FDM‘ or Fault Domain

Manger – One of the agents within the cluster is

chosen to assume the role of the Master• There is only one Master per cluster during

normal operations

– All other agents assume the role ofSlaves

•There is no more Primary/Secondaryconcept with vSphere HA




vCenter Communications

vCenter

ESX 01 ESX 03

ESX 04

• VC communicates with the Master primarily

– Once a Master is elected and contacts vCenter,vCenter sends a compatibility list to the Master.The Master saves this on a local disk, thenpushes it out to the other hosts in the cluster.

– vCenter also communicates with the Master toupdate changes to VM states and configurationinformation.

• vCenter may communicate to the Slaves incertain situations, such as:

• Scanning for a existing Master

• If the Master states that it cannot reach a

Slave. In this case, vCenter will try to

contact the Slave to determine why.

• When powering on a FT Secondary VM

• When host is reported isolated or

partitioned.

ESX 02




Storage Level Communications

vCenter

ESX 02

ESX 01 ESX 03

ESX 04

• One of the most exciting new features of vSphereHA is its ability to use a storage subsystem forcommunication.

• The datastores used for this are referred to as‗Heartbeat Datastores‘.

• This provides for increased communication

redundancy.• Heartbeat datastores are used as acommunication channel only when themanagement network is lost - such as in the caseof isolation or network partitioning.




Failure Scenarios – Network Partition

vCenter

ESX 02

ESX 01 ESX 03

ESX 04

•Occurs when: – Master can see heartbeat

datastores – Master can not reach hosts over

the management network. Results in:

• A Master in each partition

•

VMs in other partition are:• Monitored via the storage subsystem

• Restarted after a host of VM failure

• vCenter will only report the state of one of theMasters

•

When the situation is resolved,the Masters communicate andone is chosen to be the Master.




Failure Scenarios – Host Network Isolation

vCenter

ESX 02

ESX 01 ESX 03

ESX 04

•Occurs when: – Host is partitioned from the Master and

sees no vSphere HA network traffic – The host can not ping the isolation

address

Results in:

• Isolation response applied (if configured and the

Master can restart the VMs)

• VMs left running are monitored via the storagesubsystem and restarted as needed

• Note the default isolation response has beenchanged to Leave Powered On

Isolation Address



Networking Section

vSphere 5.0 – What‘s New




New Networking Features• Two broad categories of features

• Network Discovery and Visibility/Monitoring features• LLDP

• NetFlow

• Port Mirror

• IO Consolidation (10 Gig) related features• New traffic types• User Defined Network Resource Pool ( VM traffic )

• Host Based Replication traffic

• 802.1p Tagging (QoS)

• TCP IP stack improvement• Vmknics will see following improvement

• Higher throughput with small messages

• Better IOPs scaling for iSCSI traffic




What is Network I/O Control (NETIOC) ?

• Network I/O control is a traffic management feature of

vSphere Distributed Switch (vDS)• In a consolidated IO (10 gig) deployments this featureallows customer to

• Allocate Shares and Limits to different traffic types.

– Provide Isolation• One traffic type should not dominate others

– Guarantee Service Levels when different traffic typescompete

•Enhanced Network I/O Control — vSphere 5.0 builds

on previous versions of Network I/O Control feature byproviding

• User-defined network resource pools

• New Host Based Replication Traffic Type

• QoS tagging

Coke




Server Admin

Mgmt NFS iSCSI

vMotion FT

Scheduler

Shaper

Scheduler

Traffic Shares Limit (Mbps) 802.1p

vMotion 5 150 1

Mgmt 30 --

NFS 10 250 --

iSCSI 10 2

FT 60 --

HBR 10 --

VM 20 2000 4

Pepsi 5 --

Coke 15 --

Teaming Policy

Shares enforcement peruplink

Limit enforcement perteam

Load Based Teaming

vNetwork Distributed Switch

HBR

vNetwork Distributed Portgroup

NETIOC VM traffic

CokeVM

Pepsi VMs

Network I/O Control Enhancements User




Network I/O Control Enhancements – User-defined Network RP



vStorage - What‘s new

Storage Track

vSphere 5.0 – What‘s New




Introduction to VMFS-5

•Enhanced Scalability

• Increase the size limits of the filesystem & support much larger singleextent VMFS-5 volumes.

• Support for single extent 64TB Datastores

•Better Performance

– Uses VAAI locking mechanism with more tasks

•Easier to manage and less overhead

– Space reclamation on thin provisioned LUNs

– Smaller sub blocks

– Unified Block size

VMFS-5 vs VMFS-3 Feature




VMFS-5 vs VMFS-3 Featurecomparison

Feature VMFS-3 VMFS-5

2TB+ VMFS Volumes Yes(using extents)

Yes

Support for 2TB+ Physical RDMs No Yes

Unified Block size (1MB) No Yes

Atomic Test & Set Enhancements(part of VAAI, locking mechanism)

No Yes

Sub-blocks for space efficiency 64KB (max ~3k) 8KB (max ~30k)

Small file support No 1KB




VMFS-3 to VMFS-5 Upgrade

•The Upgrade to VMFS-5 is clearly displayed in the

vSphere Client under Configuration -> Storage view.•It is also displayed in the Datastores -> Configurationview.

•Non-disruptive upgrades.




VAAI - Introduction• vStorage API for Array

Integration = VAAI

• VAAI‘s main purpose is toleverage array capabilities

• Offloading tasks to reduce

overhead• Benefit from enhanced

mechanisms arrays mechanisms

• The ―traditional‖ VAAI primitives

have been improved• We have introduced multiple

new primitives

• Support for NAS!

Application

Hypervisor

Fabric

Array

LUN01

LUN02

VAAI

Non-VAAI

VI-3




Storage vMotion - Introduction

•In vSphere 5.0, a number of new enhancementswere made to Storage vMotion. – Storage vMotion will work with Virtual Machines that have

snapshots, which means coexistence with other VMwareproducts & features such as VCB, VDR & HBR.

– Storage vMotion will support the relocation of linked clones. – Storage vMotion has a new use case – Storage DRS – which use

Storage vMotion for Storage Maintenance Mode & Storage LoadBalancing (Space or Performance).




Storage vMotion Architecture Enhancements

VMkernel

Guest OS

Mirror Driver

Source Destination

Datamover

VMM/Guest

Userworld

What does Storage DRS




What does Storage DRSprovide?

•Storage DRS provides the following:1. Initial Placement of VMs and VMDKS based on available space and

I/O capacity.

2. Load balancing between datastores in a datastore cluster viaStorage vMotion based on storage space utilization.

3. Load balancing via Storage vMotion based on I/O metrics, i.e.latency.

• Storage DRS also includes Affinity/Anti-Affinity Rulesfor VMs & VMDKs;

• VMDK Affinity – Keep a VM‘s VMDKs together on thesame datastore. This is the default affinity rule.

• VMDK Anti-Affinity – Keep a VM‘s VMDKs separate ondifferent datastores

• Virtual Machine Anti-Affinity – Keep VMs separate ondifferent datastores

•Affinity rules cannot be violated during normal

operations.

D Cl




Datastore Cluster

•An integral part of SDRS is to create a group of datastores calleda datastore cluster.

• Datastore Cluster without Storage DRS – Simply a group ofdatastores.

• Datastore Cluster with Storage DRS - Load Balancing domainsimilar to a DRS Cluster.

•A datastore cluster , without SDRS is just a datastore folder. It is

the functionality provided by SDRS which makes it more than justa folder.

datastore cluster 2TB

datastores500GB 500GB 500GB 500GB

Storage DRS Operations –




Storage DRS Operations Initial Placement

Initial Placement - VM/VMDK create/clone/relocate.•When creating a VM you select a datastore cluster rather than anindividual datastore and let SDRS choose the appropriatedatastore.

•SDRS will select a datastore based on space utilization and I/Oload.

•By default, all the VMDKs of a VM will be placed on the same

datastore within a datastore cluster (VMDK Affinity Rule), but youcan choose to have VMDKs assigned to different datastoreclusters.

datastore cluster 2TB

datastores500GB 500GB 500GB 500GB

300GBavailable

260GBavailable

265GBavailable

275GBavailable




Storage DRS Operations – Load Balancing

Load balancing - SDRS triggers on space usage &latency threshold.

• Algorithm makes migration recommendations when I/O response time and/or spaceutilization thresholds have been exceeded

– Space utilization statistics are constantly gathered byvCenter, default threshold 80%

– I/O load trend is currently evaluated every 8 hours basedon a past day history, default threshold 15ms

•Load Balancing is based on I/O workload and space which ensures that nodatastore exceeds the configured thresholds.

•Storage DRS will do a cost / benefit analysis!

•For I/O load balancing Storage DRS leverages StorageI/O Control functionality

So what does it look like? Load




So what does it look like? LoadBalancing

•It will show ―utilization before‖ and ―after‖

•There‘s always the option to override therecommendations

What are vStorage APIs Storage Awareness




What are vStorage APIs Storage Awareness(VASA)?

• What are vStorage APIs Storage Awareness

(VASA)?• VASA is an Extension of the vSphere Storage APIs,

vCenter-based extensions. Allows storage arrays tointegrate with vCenter for management functionalityvia server-side plug-ins or Vendor Providers.

• This in turn allows a vCenter administrator to beaware of the topology, capabilities, and state of thephysical storage devices available to the cluster.

• VASA enables several features.

• For example it delivers System-defined (array-defined)Capabilities that enables Profile-driven Storage.• Another example is that it provides array internal information

that helps several Storage DRS use cases to work optimallywith various arrays.

S C bili i & VM S P fil




Storage Capabilities & VM Storage Profiles

Storage Capabilitiessurfaced by VASA or

user-defined

xxx VM Storage Profilereferencing Storage

Capabilities

VM Storage Profileassociated with VM

CompliantNot

Compliant



vSphere Storage Appliance

(VSA)

I d i h S h S A li (VSA)




Introducing the vSphere Storage Appliance (VSA)

We are basically providing our customers with a low cost, easy to deploy storageappliance which will provide shared storage.

• The VSA Manager installation/configuration steps are fool-proof, meaning thatan administrator without any SAN skills can deploy it quickly & painlessly. Thisis a really cool selling point when compared to some other VSAs on the market.

• The VSA creates shared storage out of local storage for use by a specificset of hosts.

• This means that vSphere HA & vMotion can now be made available on low-end (SMB) configurations, without external SAN or NAS servers.

• The vSphere Storage Appliance can be deployed in two configurations:

– 2 x ESXi 5.0 servers configuration• Deploys 2 vSphere Storage Appliances, one per ESXi server & a

VSA Cluster Service on the vCenter server.

– 3 x ESXi 5.0 servers configuration

vSphere Storage Appliance (VSA) How it




vSphere Storage Appliance (VSA) How itWorks

•Each ESXi server has a VSA deployed to it as a Virtual Machine.•The appliances use the available space on the local disk(s) of theESXi servers & present one replicated NFS volume per ESXiserver. This replication of storage makes the VSA very resilientto failures.

vSpherevSphere vSphere

VSA VSA VSA

NFS NFS NFS

vSphere Client

VSA Manager



What‘s New in vCenter SiteRecovery Manager 5

Key Components Of SRM 5




Key Components Of SRM 5

Storage

vCenter ServerSite

Recovery

Manager

Choice of Replication Options

Required at Both Protectedand Recovery Sites

vSphere

Site Recovery Manager

• Manages recovery plans

• Automates failovers and failbacks

• Tightly integrated with vCenter and replication

vSphere Replication

• Bundled with SRM

• Replicates virtual machines betweenvSphere clusters

Storage-Based Replication (3rd party)

• Provided by replication vendor

• Integrated via replication adapters created,

certified and supported by replication vendor

Wh t‘ N I Sit R M 5 0?

http://www-3.ibm.com/software/




What‘s New In Site Recovery Manager 5.0?

• vSphere Replication

• Bundled with SRM at no additional cost• Provides simple, cost-efficient replication

between vSphere clusters

• Automated failback

• Bi-directional recovery plans• Automates failback to original site

• Planned migration

• New workflow that can be applied to anyrecovery plan

• Ensures no data-loss, application-consistent migrations of virtual machines

• Others

• More granular control over VM startuporder

• Protection-side APIs• IPv6 support

Expand DR coverage to

Tier 2 apps and smallersites

Streamline plannedmigrations(for disaster avoidance,planned maintenance, …)

SRM P id B d Ch i f R li ti O ti




SRM Provides Broad Choice of Replication Options

vSphere Replication Simple, cost-efficient replication for Tier 2 applications and smaller sites

Storage-based Replication High-performance replication for business-critical applications in larger sites

vCenter ServerSite

Recovery

Manager

vSphere

vCenter ServerSite

Recovery

Manager

vSphere

vSphere

Replication

Storage-basedreplication

Site A (Primary) Site B (Recovery)

vSphere Replication For Cost-Efficient, Simple




p p , pReplication

Reduce storage costs by 2X

• Support for heterogeneous

storage across sites,

including non-replicating

storage

• Use lower-end or olderstorage at failover site

Eliminate replication

software costs


included with Site Recovery

Manager at no additionalcost

Manage replication directly

from vCenter

• Eliminate complex

interactions with storage

teams

Manage replication at the

individual VM level

• Eliminate need for

complicated VM-to-LUN

mapping

15 minute RPOs

• Set RPOs between 15 minutes and

24 hours

Efficient network utilization

• Replicate only changed disk areas

Highly scalable• 500 virtual machines

Limitations

• No automated failback

• File-level consistency only (except

planned migration)

• No FT, templates, linked clones,

physical RDMs

Cost-efficient Simple Powerful

Beyond DR: Disaster Avoidance And Planned




yMigrations

Recover from unexpected

site failure

• Full or partial site failure

The most critical but least

frequent use-case

• Unexpected site failures do

not happen often

• When they do, fast recovery

is critical to the business

Anticipate potential

datacenter outages

• For example: in case of

planned hurricane, floods,forced evacuation, etc.

Initiate preventive failover

for smooth migration

• Leverage SRM ‗planned

migration ‘ to ensure no

data-loss

• ‗Automated failback ‘

enables easy return to

original site

Most frequent SRM use case

• Planned datacenter maintenance

• Global load balancing

Streamline routine migrations

across sites

• Test to minimize risk

• Execute partial failovers

• Leverage SRM ‗planned

migration ‘ to ensure no data-

loss

• ‗Automated failback ‘ enablesbi-directional migrations

Disaster Failover Disaster Avoidance Planned Migration

3 typical use-cases for SRM

Planned Migrations For App Consistency & No Data Loss




Planned Migrations For App Consistency & No Data Loss

Overview

Benefits

Two workflows can be applied to recovery plans: DR failover

Planned migration

Planned migration ensures applicationconsistency and no data-loss during migration Graceful shutdown of production VMs in

application consistent state Data sync to complete replication of VMs

Recover fully replicated VMs

Better support for planned migrations

No loss of data during migration process

Recover ‗application-consistent‘ VMs at

recovery site

Planned Migration

Site BSite A

Replication

1 Shut downproduction VMs

2

Sync data, stop replicationand present LUNs to vSphere

3 Recover app-consistent VMs

vSphere vSphere

Automated Failback To Streamline Bi-Directional




Simplify failback process

Automate replication management

Eliminate need to set up new recovery plan

Streamline frequent bi-directional migarations

Migrations

Re-protect VMs from Site B to Site A Reverse replication

Apply reverse resource mapping

Automate failover from Site B to Site A

Reverse original recovery plan

Restrictions

Does not apply if Site A has undergonemajor changes / been rebuilt

Not available with vSphere Replication

Overview

Benefits

Automated Failback

Site BSite A

Reverse

Replication

Reverse original recovery plan

vSphere vSphere

SRM 5 Editions Lineup




SRM 5 Editions LineupSRM 5

Standard Enterprise

Price per protected virtual machine (license only)

$195 $495

Scalability Limits

• Maximum protected VMs 75 virtual machines(1)

Unlimited(2)

Features

• Support for storage-based replication

• Centralized recovery plans

• Non-disruptive testing

• Automated DR failover


• Automated failback

• Planned migration

New in SRM 5.01. Maximum of 75 VMs per site and per SRM instance

2. Subject to the product‘s technical scalability limits



Thank You!

whats new in vsphere 5 and srm 5 varrow branded1

Documents