Veritas InfoScale™ 7.3.1 Virtualization Guide - Linux on ESXi
- Section I. Overview
- Overview of Veritas InfoScale solutions in a VMware environment
- Introduction to using Veritas InfoScale solutions in the VMware virtualization environment
- Introduction to using Dynamic Multi-Pathing for VMware
- About Veritas InfoScale solutions support for the VMware ESXi environment
- Overview of Veritas InfoScale solutions in a VMware environment
- Section II. Deploying Veritas InfoScale products in a VMware environment
- Getting started
- Getting started
- Section III. Use cases for Veritas InfoScale product components in a VMware environment
- Storage to application visibility using Veritas InfoScale Operations Manager
- About storage to application visibility using Veritas InfoScale Operations Manager
- About discovering the VMware Infrastructure using Veritas InfoScale Operations Manager
- About the multi-pathing discovery in the VMware environment
- About near real-time (NRT) update of virtual machine states
- Application availability using Cluster Server
- Multi-tier business service support
- Improving storage visibility, availability, and I/O performance using Dynamic Multi-Pathing
- How DMP works
- Improving I/O performance using SmartPool
- Improving data protection, storage optimization, data migration, and database performance
- Protecting data with Veritas InfoScale product components in the VMware guest
- Optimizing storage with Veritas InfoScale product components in the VMware guest
- Migrating data with Veritas InfoScale product components in the VMware guest
- Improving database performance with Veritas InfoScale product components in the VMware guest
- Setting up virtual machines for fast failover using Storage Foundation Cluster File System High Availability on VMware disks
- About setting up Storage Foundation Cluster File High System High Availability on VMware ESXi
- Configuring coordination point (CP) servers
- Configuring storage
- Storage to application visibility using Veritas InfoScale Operations Manager
- Section IV. Reference
Assessing availability levels for Cluster Server in the VMware guest
In certain situations, VMware HA with VCS-in-guest would yield higher availability than a standalone VCS-in-guest.
For example:
Three ESXi hosts H1, H2, and H3 and two virtual machines (VMs) N1 and N2 are in a VCS-in-guest cluster.
N1 is running on H1 and N2 is running on H2. N1 is running the application.
If H2 fails, then VMware HA restarts N2 on H3.
Now if H1 fails, the application would fail over to N2. In absence of VMware-HA this would not be possible.
In certain situations, VMware HA with VCS-in-guest would yield lesser availability than standalone VCS-in-guest.
For example:
Two ESXi hosts H1 and H2 and two VMs N1 and N2 are in a VCS-in-guest cluster.
N1 is running on H1 and N2 is running on H2. N1 is running the app.
If H2 fails, then VMware HA restarts N2 on H1. N1 and N2 end up on the same host.
Subsequently if H2 is back again and if H1 fails, both N1 and N2 fail and from the point of view of VCS-in-guest cluster, it would be as if the entire cluster rebooted.
Note:
This would yield lesser availability than stand-alone VCS-in-guest where when H2 is back again and N2 would have started on H2, thus allowing the application to failover quickly to N2 when H1 fails.
The goal is that VMs of a VCS-in-guest cluster must distribute themselves evenly across hosts, otherwise there is a possibility of losing availability. It is difficult to enforce this through DRS because DRS triggers only periodically, which leaves a window where VMs may not be distributed evenly.