Verify Cross-Domain Configurationfor VMware HA Cluster

VMware HA Cluster

Managing your own Cloud infrastructure with hundreds or thousands of VMware ESX/ESXi servers while allowing high availability, resiliency and data protection through advanced vSphere features (such as vSphere Cluster HA, vMotion, VMware SRM and more) is essential to your business.

Meeting those goals while keeping up with emerging business needs creates an extremely challenging dynamic virtualization environment. The continuous stream of changes (servers, storage, databases and network) puts administrators in a constant chase of configuration and best practice compliance. Such changes, either managed within or without vCenter form configuration gaps that can introduce single-points-of-failures into the environment, putting your entire system’s availability, fault tolerance, replication and data protection at serious risk.

vSphere Storage and Replication Configuration

AvailabilityGuard verifies that your underlying storage devices are accessible and configured to provide equal levels of availability and service. AvailabilityGuard assures you that upon a host failure your clusters will successfully relocate workload to other hosts and be able to react to VM failures — whether at the OS or application level. When VMware SRM is used, you can be assured that your SRM is set up correctly to manage the replication process, to make DR LUNs accessible, and to start the services at the remote site, thereby ensuring that multi-site fail-over and DR work according to plan.

Samples

  • LUNS inaccessible to cluster nodes (local or remote nodes), or accessible to unauthorized hosts
  • Fabric single-point-of-failure or masking/zoning misconfigurations that will fail fail-over (also within the Blade system)
  • Incorrect replication settings for EMC, HDS, IBM, HP, NetApp and other storage platforms.
  • Data misplaced on incorrect storage tier, or on un-shared volumes.
  • Incorrect storage disk group (DG) configuration, SRM protection groups or network mappings.
  • And more.

VM and Application Level Settings

Your ESX Cluster environment includes many components such as Virtual Machines, Virtual File Systems, Database and Application Servers, guest OS clustering and more. With so many components and with a flood of routine changes being made to the environment, the risk of creating issues that may lead to failed switch-overs is substantial. AvailabilityGuard is here to find those misconfigurations and assure you that all cluster configurations and settings are aligned and well-orchestrated, so your ESX clusters perform as designed, no matter what.

Samples:

  • Single-points-of-failure – clusters, business services or same-function VMs running on the same single physical hardware.
  • Virtual SCSI devices and RDM availability best practice violations
  • App HA best practices
  • VMware Tools settings that impact availability, data protection, backup, time sync, etc..
  • Application best practices for VMware VMs (SQL/Oracle, Tomcat, WebLogic, Java and more)
  • And more.

ESX Cluster Node

AvailabilityGuard’s intelligent comparison engine empowers the VMware administrator to proactively identify and fix inconsistencies between cluster nodes that could lead to unexpected behavior at and following a cluster fail-over.

Samples:

  • Differences in OS version, ESX options, services, network options, domain, etc.
  • Differences in FC Adapter settings, NIC configuration, etc.
  • Differences in multipath configuration – number of paths, path selection policy (PSP), Storage Array Type Plug-in (SATP)
  • Differences in domain configuration, DNS, time and ntp settings, etc.
  • And more.

Eliminate vSphere Configuration Vulnerabilities

Easily verify that your vSphere HA and ESX servers configurations comply with VMware guidelines and with community-driven best practices. Just let AvailabilityGuard run its smart analysis that includes comprehensive investigation of ESX Server options, Datastores, vMotion and DRS configuration.

Samples:

  • vSphere HA and Fault Tolerance (FT) guidelines (Host Monitoring, VM Monitoring, Restart Priority, Admission Control, DPM, Affinity rules and more)
  • Virtual networking best practices for successful fail-over (port groups, VLAN, management interfaces and more)
  • Snapshot and swap file analysis
  • DRS and SDRS best practice breaches
  • NFS and VMFS datastore misconfigurations
  • And more.