VSE+ Training - APTARE IT Analytics

Architecture
APTARE Terminology
Term Description
Apache Web Server

Portal Tomcat Portal Tomcat servlet that manages user’s requests from Portal UI browsers.

Data Receiver (Tomcat) Tomcat servlet that receives collection data from agents or data collectors.

Portal UI Browser “application” to run reports and administrate the application.

Data Collector Collector for all other types of data – TSM, Arrays, Hosts, VMWare, Switches, etc.

WMI Proxy Server Service that executes WMI commands to probe Windows hosts.

Domain Realm. Private subset of the data. Used to implement security controls for multi-
tenancy systems.

2 Copyright © 2019 Veritas Technologies, LLC

 APTARE Architecture

3 Copyright © 2019 Veritas Technologies, LLC

Deployment Architecture In The Data Center

HDS
Storage Array
EMC
Storage Array

IBM
Storage Array
HP Storage
Array Data
Collector
SAN Portal
NetApp
Storage Fabric
Virtual
Infrastructure
Linux/UNIX
Windows
Hosts
Data
Protection
Assets

4 Copyright © 2019 Veritas Technologies, LLC

APTARE Architecture Components

Data Collector

APTARE
Portal Server

Portal Server Software Reporting Database

Oracle

5 Copyright © 2019 Veritas Technologies, LLC

APTARE Server Software Components

Open-Source and Third-Party Software to provide

framework components.

APTARE binaries:
• The Portal engine drives the Portal user interface.
• The Data Receiver accepts data from the Data Collector, then saves the data to
the Reporting Database.
• The stored procedures retrieve data from the Reporting Database, input data
Portal Server into the Reporting Database, and perform calculations and analysis.
Software

Database SQL Scripts to instruct the Oracle SQL scripts to

create the object module and database schema.

6 Copyright © 2019 Veritas Technologies, LLC

 Reporting Database
You can install the Reporting Database on a standalone server or on the same server
as the Portal Server.

The preferred configuration is to have the database on the same server as the Portal.

The Reporting Database stores all report data (as metadata) that it receives from
Reporting Database the Data Receiver.
Oracle
Data is managed in the Reporting Database with automatic purging scripts that run
with specific retention periods per product and even data type.

Because the Reporting Database only stores metadata, the amount of data on the
Reporting Database is relatively small (GBs).

7 Copyright © 2019 Veritas Technologies, LLC

 Data Collectors
The Data Collector then sends this data (http or https) to another Java
application, the Data Receiver. The Data Receiver runs on the Portal
Server and stores the data that it receives in the Reporting Database.
When you use the Portal to generate a report, the Portal requests this
information from the Reporting Database, then returns the results in
one of the many available reports.
The Data Collector obtains all of its monitoring rules from
a Data Collector Configuration File. This file resides in the
Reporting Database in XML format. When the Data
Collector first starts, it downloads this file from the
Reporting Database.
The Data Collector uses this file to determine the list of
backup servers, hosts, or storage arrays that are to be
monitored and included in its data collection process.

A Data Collector is a centralized and

remotely managed data collection A single installation of the Data
mechanism. Data Collector Collector supports any number of
servers. The only real limitation is the
This Java application interacts with memory and CPU processing power
backup servers, storage arrays, of the server on which the Data
switches, etc to gathering Collector resides.
information.

8 Copyright © 2019 Veritas Technologies, LLC

Scale Out Through Multiple Collectors

Data
SAN Collector
Fabric

Data
SAN Collector
Fabric

Portal

9 Copyright © 2019 Veritas Technologies, LLC

 Multi-Tenancy & Security

10 Copyright © 2019 Veritas Technologies, LLC

Multi-Tenancy & Security
• Multi-Tenancy: • Security
– From it's inception, the solution was designed for – Data at rest is encrypted AES-128
multi-tenancy – Only Decrypted at time of use
– Security is implemented at the database layer – Never persisted in decrypted state
– Database interaction through parameterized – SSL supported for all transmission between
views. user/portal & portal/collector
– Almost all queries leverage the parameterized
views

11 Copyright © 2019 Veritas Technologies, LLC

Managed Service Architecture

12 Copyright © 2019 Veritas Technologies, LLC

 Thank you!

Copyright © 2019 Veritas Technologies, LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies or its affiliates
in the U.S. and other countries. Other names may be trademarks of their respective owners.
This document is provided for informational purposes only and is not intended as advertising. All warranties relating to the information in this document, either express or
implied, are disclaimed to the maximum extent allowed by law. The information in this document is subject to change without notice.