Views:

Multiple standalone Deep Discovery Analyzer appliances can be deployed and configured to form a cluster that provides fault tolerance, improved performance, or a combination thereof.

Depending on your requirements and the number of Deep Discovery Analyzer appliances available, you may deploy the following cluster configurations:

Table 1. Cluster Configurations

Cluster Configuration

Description

High availability cluster

In a high availability cluster, one appliance acts as the active primary appliance, and one acts as the passive primary appliance. The passive primary appliance automatically takes over as the new active primary appliance if the active primary appliance encounters an error and is unable to recover.

Load-balancing cluster

In a load-balancing cluster, one appliance acts as the active primary appliance, and any additional appliances act as secondary appliances. The secondary appliances process submissions allocated by the active primary appliance for performance improvement.

Note:

For all Deep Discovery Analyzer functions to operate properly in a load-balancing environment, make sure the primary and secondary appliances can communicate with each other.

High availability cluster with load balancing

In a high availability cluster with load balancing, one appliance acts as the active primary appliance, one acts as the passive primary appliance, and any additional appliances act as secondary appliances. The passive primary appliance takes over as the active primary appliance if the active primary appliance encounters an error and is unable to recover. The secondary appliances process submissions allocated by the active primary appliance for performance improvement.

For details, see the Deep Discovery Analyzer Installation and Deployment Guide.

The following table lists the available configuration modes and associated appliance behavior.

Table 2. Cluster Configuration Modes

Configuration Mode

Description

Primary (Active)

  • Management console is fully accessible

  • Retains all configuration settings

Primary (Passive)

  • Management console is unavailable

  • Automatically configured based on the settings of the active primary appliance

  • On standby

  • Takes over as the active primary appliance if the active primary appliance encounters an error and is unable to recover

  • Does not process submissions

Secondary

  • Automatically configured based on the settings of the active primary appliance

  • Identifies the active primary appliance using its IP address or virtual IP address

  • Processes submissions allocated by the active primary appliance for performance improvement

  • Management console only shows screens with configurable settings:

    • Virtual Analyzer > Sandbox Management > Network Connection

    • Virtual Analyzer > Sandbox Management > Sandbox for macOS

    • Administration > Updates > Hotfixes / Patches

    • Administration > Updates > Firmware

    • Administration > Integrated Products/Services > SAML Authentication

    • Administration > System Settings > Network

    • Administration > System Settings > Network Interface

    • Administration > System Settings > HTTPS Certificate

    • Administration > System Settings > Cluster

    • Administration > Accounts / Contacts > Accounts

    • Administration > System Logs

    • Administration > System Maintenance > Network Services Diagnostics

    • Administration > System Maintenance > Power Off / Restart

    • Administration > System Maintenance > Debug

    • Administration > License

Note:

In environments that use a load-balancing cluster or a High Availability cluster with load balancing, Deep Discovery Analyzer automatically slows down Virtual Analyzer throughput on the active primary appliance to prevent exhaustion of system resources