NetBackup IT Analytics User Guide
- Introduction
- Understand the Portal
- About the Admin tab
- Explore your inventory
- Hierarchy toolbar to organize your data
- Show objects
- Use attributes to organize your data
- Pin reports - saving reports with inventory objects
- Assign attributes in the inventory list view
- Get acquainted with reports
- About badging
- Generate and maintain reports
- Select Report Scope
- Group hosts by attributes
- Search for hosts in the report Scope Selector
- Backup Manager advanced scope selector settings
- Solution reports scope selector settings
- Units of Measure in Reports
- Customize report filter logic
- Sort columns in reports
- Convert tabular report to chart
- Distribute, share, schedule, and alert
- Scheduling Exported Reports and Dashboards
- Organize reports
- Work with the dynamic template designer
- Dynamic Template Designer Quick Start
- Converting to a Homogeneous, Product-Specific Template
- Dynamic Template Function Configurations
- Create Fields with the Field Builder
- Scope Selector Component - Custom Filter
- Configure a Bar Chart Dynamic Template
- Steps to Create a Bar Chart Dynamic Template
- Configure an Area/Stacked Area Chart Dynamic Template
- Line Charts for Performance Metrics
- Line Chart Field Requirements
- One Object Per Line Chart, One or More Metrics Per Chart
- Multiple Objects Per Line Chart, One Metric Per Chart
- Example of a Stacked Bar Chart Dynamic Template
- Create a Sparkline Chart in a Tabular Dynamic Template
- Adding or Editing Methods
- Validate and Save a Method
- Work with the SQL template designer
- Database Published Views
- Create a SQL Template
- Configure SQL Template Scope Selector Components
- Sample SQL Queries
- Configure SQL Template Scope Selector Components
- Format the SQL Template Output
- Configure a Table in the SQL Template Designer
- Advanced SQL Report Template Options
- Export/Import SQL Templates
- Pipelined functions for report query building
- APTlistOfDates
- aptStringConcat
- getServerAttributeValue
- getObjectAttributeValue
- getChildServerGroupContextById
- getServerGroupContextById
- secsToHoursMinSecs
- APTgetTapeDriveStatusName
- getFullPathname
- listJobSummaryAfterRestart
- listJobSummaryAfterRestartNBW
- listJobSummaryAfterRestart for NetWorker Backup Jobs
- listOfBackupWindowDates
- listChargebackCatByVOLSDetail
- listChargebackCatByNcVolDetail
- listChargebackCatByFSDetail (for HNAS)
- listChargebackCatByFSDetail (for EMC Isilon)
- listChargebackByLUNSummary
- listChargebackByLUNDetail
- listChargebackCatByLUNSummary
- listChargebackCatByLUNDetail
- Alert configuration
- Manage hosts, backup servers, and host groups
- Manage attributes and objects
- Provide Portal access and user privileges
- Setting / Resetting passwords
- Managing user group home pages (Administrator)
- Configure master schedules and backup windows
- Add, edit, and move policies
- Add/Edit a threshold policy
- Capacity Chargeback policy types
- Solutions administration
- Manage and monitor data collection
- About data collection tasks
- Add/Edit data collectors
- Review collectors and collection status
- Upgrade Data Collectors
- Work with Capacity Manager host data collection
- Host Access Privileges, Sudo Commands, Ports, and WMI Proxy Requirements
- Host access requirements
- Manage credentials
- Configure host discovery policies to populate the host discovery and collection view
- Discovery processes
- Validate host connectivity
- Search and export in host discovery and collection
- Propagate probe settings: Copy probes, paste probes
- Discovery policies for Veritas NetBackup
- About Discovery types
- View and manage system notifications
- Customize with advanced parameters
- Use cases for advanced parameters
- Access control advanced parameters
- General Data Collection advanced parameters
- Cloud data collection advanced parameters
- Host discovery and collection advanced parameters
- Backup Manager advanced parameters
- Capacity Manager advanced parameters
- File Analytics advanced parameters
- Virtualization Manager advanced parameters
- Manage your Portal environment
- Analyze files
- Troubleshoot the Portal
- Retrieving log files
- Debug
- Attribute inheritance overrides
- Understanding report data caching
NetBackup IT Analytics components
When you install NetBackup IT Analytics, you are installing the following components:
Portal Server. The physical server on which the NetBackup IT Analytics Portal Server software resides.
Portal Server Software. The binaries, SQL scripts, configuration files, and open-source and third-party software products needed to retrieve and render reporting data from the Reporting Database.
Reporting Database. The Oracle database stores all report data. The Reporting Database is usually installed on the Portal Server, but you can just as easily install it on a separate server, preferably a dedicated database server. These binaries are installed during the first step of the installation procedure.
Data Collectors. The software that collects report data about your backup servers and storage arrays. The Data Collector is usually installed on a separate server.
Because of the relationship between the Portal Server, the Portal Server software, and the Reporting Database, you need to install these Portal Server components at the same time. However, you can install the Data Collector separately.
When you install Portal Server software, you install a compilation of software:
Open-Source and Third-Party Software to provide framework components.
Binaries to provide intelligence and functionality. These binaries include the Portal engine, the Data Receiver, and stored procedures.
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 into the Reporting Database, and perform calculations and analysis.
Database SQL Scripts to instruct the Oracle SQL scripts to create the object module and database schema.
The Reporting Database stores all report data (as metadata) that it receives from the Data Receiver. 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. If you use a Managed Services Provider, the Reporting Database and Portal Server are usually off site and hosted by that third-party provider.
Data is managed in the Reporting Database with automatic purging scripts that run, with specific retention periods per product and even data type. Some reports are more valuable when they have access to historical data. Because the Reporting Database only stores metadata, the amount of data on the Reporting Database is relatively small (GBs).
A Data Collector is a centralized and remotely managed data collection mechanism. This Java application is responsible for interfacing with enterprise objects, such as backup servers, storage arrays, and switches, gathering information related to storage backup and recovery, and capacity management.
The Data Collector continuously collects data and sends this data, using an http or https connection, 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 single installation of the Data Collector supports any number of servers. The only real limitation is the memory and CPU processing power of the server on which the Data Collector resides.