InfoScale™ 9.0 Virtualization Guide - Linux on ESXi
- Section I. Overview
- Section II. Deploying Veritas InfoScale products in a VMware environment
- Getting started
- Understanding Storage Configuration
- Getting started
- Section III. Use cases for Veritas InfoScale product components in a VMware environment
- Application availability using Cluster Server
- Multi-tier business service support
- Improving data protection, storage optimization, data migration, and database performance
- Protecting data with InfoScale™ product components in the VMware guest
- Optimizing storage with InfoScale™ product components in the VMware guest
- About Flexible Storage Sharing
- Migrating data with InfoScale™ product components in the VMware guest
- Improving database performance with InfoScale™ product components in the VMware guest
- Setting up virtual machines for fast failover using InfoScale Enterprise on VMware disks
- About setting up InfoScale Enterprise on VMware ESXi
- Section IV. Reference
Recommendations for improved resiliency of InfoScale clusters in virtualized environments
Arctera recommends that you configure the following settings to improve the resiliency of InfoScale cluster configurations in virtualized environments:
Peerinact: Set the default LLT tunable parameter peerinact to 32 seconds instead of 16 seconds. Doing so helps improve the stability of the cluster in virtualized environments, where multiple external factors as described further in this list, can affect the stability of the cluster.
Provisioning ratio: The CPU and memory provisioning ratio affects the stability of the InfoScale cluster. To ensure maximum stability, set the ratio to the lowest value possible. For critical solutions that require maximum resiliency, the ratio must be set to 1:1.
CPU load on host operating systems: Although the provisioning ratio is low, the CPU load on the host operating systems still plays a part in cluster stability. If the load on the host operating system is very high, it can affect how vCPUs on the guest VMs are scheduled, because vCPUs are processes from the perspective of the host servers.
CPU requirement of the actual workload on guests: When the total CPU requirement for workloads exceeds the available physical CPU capacity, it causes node evictions due to heartbeat timeouts.
External events: External events like live migration of the guest VMs, virtualized disk backups, and so on, are known to add CPU load on the host servers. To reduce this additional load on the CPU, watch the stun duration in your environment caused by these events, and increase the peerinact value, if required. Increase the peerinact value only in these conditions and not in any other circumstances.
Hypervisor: Always follow the best practices for the hypervisor.
For details, refer to the VMware article at: