Previous Topic: Recommendations for Preserving Data IntegrityNext Topic: Data Collectio in a Two-Tier Deployment


Data Collection

CA Network Flow Analysis supports two types of deployment architectures:

The product components work together in both architectures to collect, process, and store flow data; display the data in reports; and generate traps, events, and scheduled reports.

Two-Tier Architecture

A two-tier architecture deployment consists of the NFA console and one or more new Harvesters. A new Harvester handles traditional Harvester tasks and the tasks that a DSA performs in a three-tier deployment.

The deployment footprint is reduced, so you have fewer component types to upgrade and maintain. Data handling requires fewer steps and files are not transferred as frequently.

A stand-alone deployment always uses the two-tier architecture: the stand-alone server hosts the NFA console and new Harvester software.

Three-Tier Architecture

A three-tier architecture deployment consists of the NFA console, one or more Harvesters, and one or more DSAs.

You may prefer the three-tier architecture if your DSA servers have lower latency than the Harvester servers. Harvester servers also have lighter storage demands.

The three-tier architecture is available only on certain types of distributed deployments, as described in the CA Network Flow Analysis Upgrade Guide topic "Software Versions That Are Supported for Upgrade."