NetBackup IT Analytics Data Collector Installation Guide for the Cloud
- Pre-Installation Setup for Amazon Web Services (AWS)
- Pre-Installation setup for Amazon Web services (AWS)
- Prerequisites for adding Data Collectors (Amazon Web services)
- Prerequisite Amazon Web services (AWS) configurations
- Configure an S3 bucket to receive billing reports
- Select cost allocation tags
- Create an AWS IAM user
- Mandatory probe user privileges
- Link AWS accounts for Collection of consolidated billing data
- Installation overview (Amazon Web Services - AWS)
- Add an Amazon Web Services (AWS) policy
- Pre-installation setup for Google Cloud Platform
- Pre-Installation Setup for OpenStack Ceilometer
- Pre-Installation Setup for OpenStack Swift
- Pre-Installation Setup for Microsoft Azure
- Pre-Installation setup for Microsoft Azure
- Setting up credentials for Microsoft Azure Data Collection
- Install the Azure PowerShell client on a Windows computer
- Find your tenant and subscription ID
- Register a new application for the Data Collector
- Create a principal and assign role to the application
- Prerequisites for Adding Data Collectors (Microsoft Azure)
- Installation overview (Microsoft Azure)
- Add a Microsoft Azure Data Collector policy
- Installing the Data Collector Software
- Validating Data Collection
- Uninstalling the Data Collector
- Manually Starting the Data Collector
- Appendix A. Firewall Configuration: Default Ports
Using the CLI check install utility
This legacy utility performs both the Test Connection function and On-Demand data collection run from a command line interface launched from the Data Collector server.
Note:
NetBackup IT Analytics does not recommend using the CLI Checkinstall utility for any Data Collector subsystem vendor which supports On-Demand runs.
The following directions assume that the Data Collector files have been installed in their default location:
Windows (C:\Program Files\Aptare) or Linux (/opt/aptare).
If you have installed the files in a different directory, make the necessary path translations in the following instructions.
Note:
Some of the following commands can take up to several hours, depending on the size of your enterprise.
To run Checkinstall
- Open a session on the Data Collector server.
Windows: Open a command prompt window.
Linux: Open a terminal/SSH session logged in as root to the Data Collector Server.
- Change to the directory where you'll run the validation script.
Windows: At the command prompt, type:
cd C:\Program Files\Aptare\mbs\bin <enter>
Linux: In the SSH session, type:
cd /opt/aptare/mbs/bin <enter>
- Execute the validation script.
Windows: At the command prompt, type: checkinstall.bat <enter>
Linux: In the SSH session. type: ./checkinstall.sh <enter>
The checkinstall utility performs a high-level check of the installation, including a check for the domain, host group and URL, Data Collector policy and database connectivity. This utility will fail if a Data Collector policy has not been configured in the Portal. For a component check, specifically for Host Resources, run the hostresourcedetail.sh|batutility.
Checkinstall includes an option to run a probe for one or more specific devices. Note that certain Data Collectors will not allow individual selection of devices. Typically these are collectors that allow the entry of multiple server addresses or ranges of addresses in a single text box.
These collectors include: Cisco Switch, EMC Data Domain, EMC VNX arrays, HP 3PAR, IBM mid-range arrays, IBM XIV arrays and VMware.
Data Collectors that probe all devices that are attached to a management server also do not allow individual selection of devices: EMC Symmetric, File Analytics, Hitachi arrays and IBM VIO.
- If the output in the previous steps contains the word FAILED, then contact Support and have the following files ready for review: /opt/aptare/mbs/logs/validation/
C:\Program Files\Aptare\mbs\logs\validation\