Avaya Analytics non-High Availability deployment overview

Last Updated : Mar 20, 2026 |

Avaya Analytics™ supports the non-High Availability (HA) deployment option that you can use in lab and production environments with the following footprints:

  • 100 agents

  • 500 agents

  • 1000 agents

The Avaya Analytics™ non-HA deployment option reduces the number of physical servers required from three to one. This deployment option eliminates the need for vSphere Enterprise Plus license, as Distributed Resource Scheduler (DRS) is not required. With this option, you can also reduce the footprint because you deploy one instance of each application pod.

Footprint details

This table provides the required memory, storage, and vCPU requirements for each component of Avaya Analytics™ non-HA deployment for the respective footprints:

Deployment size

Component

Platform

VMs

vCPU

RAM (GB)

HDD (GB)

IOPS

100 agent

All nodes

ESXi host

4

16

48128

1600

5000

500 agent

All nodes

ESXi host

4

16

53248

2833

5000

1000 agent

All nodes

ESXi host

4

18

62464

4072

5000
Important:

  • See the Avaya Analytics™ High Availability hardware requirements table for the Cluster Control Manager and VM sizes.

  • Deploy the non-HA configuration on a single physical server. For details on CPU requirements, see the Avaya Analytics™ virtual machine CPU requirements section in this chapter.

  • Non-HA configuration supports SAN storage and local disks on Avaya Analytics™. Ensure to keep sufficient space available to meet the data store requirements.

  • Async Messaging is not supported in Avaya Analytics™ non-HA deployment.

VMware licenses and configuration

You must deploy Avaya Analytics™ non-HA in a vCenter data center. The supported VMware version for non-HA deployment is:

  • 8.x

The licenses required for non-HA deployments are:

  • vCenter Server Standard

  • vSphere Standard Edition

Caveats

  • Upgrading to Avaya Analytics™ requires a fresh Avaya Analytics™ on the HA footprint. You can back up and restore the data to the HA deployment.

  • Downgrading from an Avaya Analytics™ HA to a non-HA configuration requires a fresh install of Avaya Analytics™ on the non-HA footprint.

  • Avaya Analytics™ non-HA configuration does not support disaster recovery. It is a standalone configuration.

  • Avaya Analytics™ non-HA configuration does not retain the data for the interval when a measure processor pod is restarted. This caveat is intended to reduce the impact on other measure processor pods.

  • In an Avaya Analytics™ non-HA configuration, the real-time measures are reset to zero when you restart the interval controller pod.

  • During a cluster node shutdown and restart in an Avaya Analytics™ non-HA configuration, the data produced by the measure processors on that node is not retained.

  • In an Avaya Analytics™ non-HA configuration, historical data gets lost if the node with the database is shut down and not restarted within an hour.

  • In an Avaya Analytics™ non-HA configuration, real-time reporting stops working if the data publisher service or Redis is running on the node that is restarted. Real-time reporting does not work until the node is fully recovered.

  • You can install a single Avaya Analytics™ deployment on a VMware cluster.