NetBackup IT Analytics Data Collector Installation and Configuration Guide
- Section I. Introduction
- Introduction
- Install and configure a Data Collector
- Overview
- Step-1: Choose operating system and complete prerequisites
- Step-2: HTTPS requirement
- Step-3: Add Data Collector on NetBackup IT Analytics Portal
- Step-4: Install the Data Collector
- Step-5: Verify the Data Collector is online from the Portal
- Step-6: Confirm that the Data Collector is updated
- Step-7: Configure the data collection policy
- Step-8: Confirm that the data collection policy is collecting data
- Installing the Data Collector software
- Introduction
- Considerations to install Data Collector on non-English systems
- Install Data Collector Software on Windows
- Install Data Collector software on Linux
- Configure Data Collector manually for Cohesity NetBackup
- Install Data Collector binaries on Windows (without configuration)
- Install Data Collector binaries on Linux host (without configuration)
- Configure SSL
- SSL/TLS certificate configuration
- SSL implementation overview
- Obtain an SSL certificate
- Update the web server configuration to enable SSL on the Portal server
- Enable / Disable SSL for a Data Collector
- Enable / Disable SSL for emailed reports
- Test and troubleshoot SSL configurations
- Keystore file locations on the Data Collector server
- Import a certificate into the Data Collector Java keystore
- Keystore on the portal server
- Add a virtual interface to a Linux server
- Add a virtual / secondary IP address on Windows
- Section II. Data Protection
- Configuration for Veritas Backup Exec
- Introduction
- Architecture overview (Veritas Backup Exec)
- Backup Exec terminology
- Prerequisites for adding data collectors (Veritas Backup Exec)
- Installation overview (Veritas Backup Exec)
- Enable TCP/IP for the SQL server
- Configure a Windows user
- Add Backup Exec servers
- Importing Backup Exec Server information
- Add a Veritas Backup Exec Data Collector policy
- Configuration for Cohesity DataProtect
- Configuration for Commvault Simpana
- Introduction
- Architecture overview (Commvault Simpana)
- Prerequisites for adding Data Collectors (Commvault Simpana)
- Upgrade troubleshooting: Microsoft SQL Server and Java 11
- Installation overview (Commvault Simpana)
- Open TCP/IP access to the Commvault database
- Set up a read-only user in the CommServe server
- Load historical data prior to initial data collection
- Add Commvault Simpana servers
- Add a Commvault Simpana Data Collector policy
- Configuration for EMC Avamar
- Introduction
- Architecture overview (EMC Avamar)
- Prerequisites for adding Data Collectors (EMC Avamar)
- Installation overview (EMC Avamar)
- Add EMC Avamar servers
- Adding an EMC Avamar Data Collector policy
- Testing the collection
- Add/Configure an Avamar Server within the Data Collector policy window
- Import EMC Avamar server information
- Export EMC Avamar server information
- Configuration for EMC Data Domain backup
- Architecture overview (EMC Data Domain Backup)
- Prerequisites for adding Data Collectors (EMC Data Domain Backup)
- Installation overview (EMC data domain Backup)
- Add EMC data domain servers
- Add an EMC data domain backup Data Collector policy
- Adding/Configuring an EMC data domain server within the Data Collector policy window
- Configure a data domain server for file-level compression collection
- Configuration for Dell EMC NetWorker backup & recovery
- Configuration of Dell EMC PowerProtect Data Manager (PPDM)
- Importing generic backup data
- Configuration for generic backup
- Introduction
- Generic backup data collection
- Prerequisites for adding Data Collectors (Generic Backup)
- Installation overview (generic backup)
- Add generic backup servers
- Add a generic backup Data Collector policy
- Adding/Editing a generic backup server within the Data Collector policy
- Manually load the CSV file (generic backup)
- CSV format specification
- Configuration for HP Data Protector
- Introduction
- Architecture overview (HP Data Protector)
- Prerequisites for adding Data Collectors (HP Data Protector)
- Installation overview (HP Data Protector)
- Identify HP Data Protector collection requirements
- Cell Manager commands for data collection
- Preparing for centralized data collection on a remote Cell Manager
- Configure the Data Collector server in Cell Manager (HP Data Protector)
- Configure an HP Data Protector admin user
- Validate HP Data Protector setup
- Add HP Cell Manager servers to NetBackup IT Analytics
- Add an HP Data Protector Data Collector policy
- Add/Edit a HP Data Protector server within the Data Collector policy
- Tune the configuration
- Configuration for IBM Spectrum Protect (TSM)
- Introduction
- Architecture overview (IBM Spectrum Protect -TSM)
- Prerequisites for adding data collectors (IBM Spectrum Protect - TSM)
- Installation overview (IBM Spectrum Protect - TSM)
- Add IBM Spectrum Protect (TSM) servers
- Adding an IBM Spectrum Protect (TSM) Data Collector policy
- Add/Configure an IBM Spectrum Protect (TSM) server within the Data Collector policy
- Import IBM Spectrum Protect (TSM) information
- Export IBM Spectrum Protect (TSM) server information
- Configuration for NAKIVO Backup & Replication
- Configuration for Oracle Recovery Manager (RMAN)
- Configuration for Rubrik Cloud Data Management
- Configuration for Veeam Backup & Replication
- Introduction
- Prerequisites for adding data collectors (Veeam Backup & Replication)
- Verifying Data Collector servers can connect to Veeam servers
- Known issues and limitations (Veeam Backup & Replication)
- Installation overview (Veeam Backup & Replication)
- Add a Veeam Backup & Replication Data Collector policy
- Configuration for Veritas Backup Exec
- Section III. Storage (Capacity)
- Configuration for Compute Resources
- Configuration for DELL EMC Elastic Cloud Storage (ECS)
- Configuration for Dell EMC Unity
- Pre-installation setup for Dell PowerStore
- Configuration for EMC data domain storage
- Configuration for EMC Isilon
- Configuration for EMC Symmetrix
- Configuration for EMC VNX Celerra
- Configuration for EMC VNX CLARiiON
- Configuration for EMC VPLEX
- Configuration for EMC XtremIO
- Configuration for FUJITSU ETERNUS Data Collector
- Configuration for Hitachi Block
- Pre-Installation setup for Hitachi Block
- Prerequisites for adding Data Collectors (Hitachi Block)
- Installation overview (Hitachi Block Storage)
- Adding a Hitachi Block Storage Data Collector policy
- Configuring a Hitachi Device manager user
- Configuring a Collector for Hitachi NAS block storage
- Adding an HP command view advanced Data Collector policy
- Configuration for Hitachi Content Platform (HCP)
- Pre-Installation setup for Hitachi Content Platform (HCP)
- Prerequisites for adding Data Collectors (Hitachi Content Platform)
- Installation overview (Hitachi Content Platform)
- Add a Hitachi Content Platform (HCP) Data Collector policy
- Setting up permissions for an HCP local user or active directory user
- Hitachi content platform system management console
- Hitachi content platform tenant management console
- Configuration for Hitachi NAS
- Configuration for Hitachi Vantara All-Flash and Hybrid Flash Storage
- Configuration of Host inventory
- Host Access Privileges, Sudo Commands, Ports, and WMI Proxy Requirements
- Host Inventory pre-installation setup
- Plan host Data Collection
- WMI Proxy requirements for Windows host Data Collection
- Host access requirements
- Verify command paths
- Host Inventory configuration steps
- Host Inventory setup overview
- Host Inventory maintenance overview
- Before discovering hosts
- Configure / Search the host Inventory
- Manage credentials
- Manage WMI proxy
- Manage paths
- Manage access control
- Host Inventory management
- Configure host Discovery policies to populate the host Inventory
- Execute and monitor host Discovery
- Validate host connectivity
- Show errors
- Filter the host Inventory - hide / un-hide, remove
- Host Inventory search and host Inventory export
- Export the host Inventory
- Configure and edit host probes
- Propagate Probe Settings: Copy Probes, Paste Probes
- Configuration for HP 3PAR
- Configuration for HP EVA
- Configuration for HPE Nimble Storage
- Configuration for HPE StoreOnce
- Configuration for IBM Enterprise
- Configuration for IBM COS
- Configuration for IBM SVC
- Configuration for IBM XIV
- Configuration for Microsoft Windows server
- Configuration for NetApp-7
- Configuration for NetApp StorageGRID
- Configuration for NetApp Cluster
- Configuration for NetApp E-Series
- Configuration for NEC HYDRAstor
- Configuration for Pure Storage FlashArray
- Section IV. Compute (Virtualization and Host Collection)
- Configuration for VMware
- Configuration for IBM VIO
- Pre-Installation setup for IBM VIO
- Prerequisites for adding data collectors (IBM VIO)
- Installation overview (IBM VIO)
- Adding servers for the IBM VIO Data Collector policy
- VIO servers (IBM Virtual I/O Servers)
- LPAR clients (IBM Logical Partitioning Clients) managed by VIO servers
- HMC (IBM Hardware Management Console)
- Add an IBM VIO Data Collector policy
- Configuration for Microsoft Hyper-V
- Section V. Cloud
- Configuration 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
- Configuration for Google Cloud Platform
- Configuration for OpenStack Ceilometer
- Configuration for OpenStack Swift
- Configuration 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
- Configuration for Amazon Web Services (AWS)
- Section VI. Fabric
- Configuration for Brocade switch
- Pre-Installation setup for Brocade switch
- Prerequisites for adding Data Collectors (Brocade switch)
- Upgrade troubleshooting: Brocade BNA SMI-S (CIM) server and Java 11
- Supported switches
- Brocade switches: Default ports and firewall considerations
- Installation overview (Brocade switch)
- Brocade switch Data Collector policy
- Configuration for Cisco switch
- Pre-Installation setup for Cisco switch
- Prerequisites for adding Data Collectors (Cisco switch)
- Upgrade troubleshooting: Cisco DCNM SMI-S (CIM) server and Java 11
- Cisco switches: Default ports and firewall considerations
- Installation overview (Cisco switch)
- Cisco switch Data Collection policy
- Before you start Cisco switch Data Collection
- Configuration for Brocade Zone alias
- Configuration for Cisco Zone alias
- Configuration for Brocade switch
- Section VII. File Analytics
- Configuration for File Analytics
- Pre-Installation setup for File Analytics
- File Analytics Data Collection overview
- File Analytics Data Collection architecture
- File Analytics Data Collector policies
- Prerequisites for adding Data Collectors (File Analytics)
- CIFS shares
- Host Discovery and Collection File Analytics probe
- Adding a File Analytics Data Collector policy
- Set up FIPS compliant Data Collector for File Analytics
- File Analytics Export Folder Size and Folder Depth
- Configuration for File Analytics
- Section VIII. Data Collection Validation and Troubleshooting
- Validate data collection
- Data Collector Troubleshooting
- Resolving Data Collectors connections issues - Linux specific
- Resolving Data Collectors connections issues - Windows specific
- Portal upgrade performance issues
- Verify the Data Collector configuration
- Verify Connectivity
- Configuring web proxy updates
- Collecting missed events for Veritas Backup Exec
- Substituting ODBC for JDBC to connect to SQL server for Veritas Backup Exec
- Useful Data Collection scripts for capacity
- Host resources troubleshooting
- Host resources: Check the status of the WMI proxy server
- Host resources: Post-Installation verification
- Host resources: Check host connectivity using standard SSH
- Host resources: Check host connectivity
- Host resources: Check host connectivity using Host Resource Configuration file
- Host resources: Generating host resource configuration files
- Host resources: Check the execution of a command on a remote server
- Host resources Data Collection
- Host resources: Collection in stand-alone mode
- Configuring parameters for SSH
- Identifying Windows file system access errors (File Analytics)
- Collect from remote shares (File Analytics)
- Adding a certificate to the Java keystore
- Uninstalling the Data Collector
- Appendix A. Firewall Configuration: Default Ports
- Appendix B. Load historic events
- Introduction
- Load Commvault Simpana events
- Load Dell PowerProtect Data Manager jobs
- Load EMC Avamar events
- Load EMC NetWorker events
- Load HP Data Protector events
- Load IBM Spectrum Protect (TSM) events
- Load Oracle Recovery Manager (RMAN) events
- Load Veeam Backup & Replication events
- Load Veritas NetBackup events
- Load Veritas Backup Exec events
- Corrections in duplication of clients
- Cohesity
- Dell EMC NetWorker Backup & Recovery
- Appendix C. CRON Expressions for Policy and Report Schedules
- Appendix D. Maintenance Scenarios for Message Relay Server Certificate Generation
Host resources: Check the status of the WMI proxy server
Use the following utility to verify that the WMI Proxy Server is up and running.
The WMI Proxy logs are written to:
C:\Program Files\Aptare\WMIProxyServer\logs\aptarewmiserver.log
Either or must have been run before running . Otherwise, will not have access to the proxy server settings that are saved in the collector configuration file.
checkwmiproxy.[sh|bat] [wmiProxyServer wmiProxyPort remoteWinHost DomainOfUserId UserId Password "Command"]
Where:
wmiProxyServer is the name of the WMI Proxy Server
wmiProxyPort is the proxy's port (default is 1248)
checkwmiproxy.[sh|bat]
By default, this utility will look for the WMI Proxy Server details in the Host Resources Collector section of the collector configuration file. If it does not find a Host Resources Collector section, the will terminate with an error and a recommendation to pass explicit parameters, as shown in the usage statement above.
[root@aptaredev3 bin]# ./checkwmiproxy.sh MetaDataChildThread.init(). Going to initialize. Will try to connect to the APTARE WMI Proxy at 172.16.1.152:1248 APTARE WMI Proxy Version: APTAREWMIServer 6.5.01 06/25/07 21:00:00 Connection to APTARE WMI Proxy server successfully validated.
This utility also can be used to execute remote WMI queries, as shown in the following example.
[root@aptaredev3 bin]# ./checkwmiproxy.sh 172.16.1.152
Administrator password 172.16.1.152 "select * from Win32_OperatingSystem"
MetaDataChildThread.init(). Going to initialize.
Will try to connect to the APTARE WMI Proxy at 172.16.1.152:1248
APTARE WMI Proxy Version: APTAREWMIServer 6.5.01 06/25/07 21:00:00
Connection to APTARE WMI Proxy server successfully validated.
APTAREWMIServer Response:
instance of Win32_OperatingSystem
{
BootDevice = "\\Device\\HarddiskVolume1";
BuildNumber = "3790";
BuildType = "Multiprocessor Free";
Caption = "Microsoft(R) Windows(R) Server 2003, Standard Edition";
CodeSet = "1252";
CountryCode = "1";
CreationClassName = "Win32_OperatingSystem";
CSCreationClassName = "Win32_ComputerSystem";
CSDVersion = "Service Pack 1";
CSName = "APTARESTGRPT1";
CurrentTimeZone = -420;
DataExecutionPrevention_32BitApplications = TRUE;
DataExecutionPrevention_Available = TRUE;
DataExecutionPrevention_Drivers = TRUE;
DataExecutionPrevention_SupportPolicy = 2;
Debug = FALSE;
Description = "aptarestgrpt1";
Distributed = FALSE;
EncryptionLevel = 168;
ForegroundApplicationBoost = 2;
FreePhysicalMemory = "160264";
FreeSpaceInPagingFiles = "1967860";
FreeVirtualMemory = "2084508";
InstallDate = "20070212110938.000000-480";
LargeSystemCache = 1;
LastBootUpTime = "20080507115419.343750-420";
LocalDateTime = "20080520142117.484000-420";
Locale = "0409";
Manufacturer = "Microsoft Corporation";
MaxNumberOfProcesses = 4294967295;
MaxProcessMemorySize = "2097024";
Name = "Microsoft Windows Server 2003 R2 Standard
Edition|C:\\WINDOWS|\\Device\\Harddisk0\\Partition1";
NumberOfLicensedUsers = 10;
NumberOfProcesses = 90;
NumberOfUsers = 8;
Organization = "Aptare";
OSLanguage = 1033;
OSProductSuite = 272;
OSType = 18;
OtherTypeDescription = "R2";
PAEEnabled = TRUE;
Primary = TRUE;
ProductType = 3;
QuantumLength = 0;
QuantumType = 0;
RegisteredUser = "Aptare";
SerialNumber = "69712-OEM-4418173-93136";
ServicePackMajorVersion = 1;
ServicePackMinorVersion = 0;
SizeStoredInPagingFiles = "2039808";
Status = "OK";
SuiteMask = 272;
SystemDevice = "\\Device\\HarddiskVolume1";
SystemDirectory = "C:\\WINDOWS\\system32";
SystemDrive = "C:";
TotalVirtualMemorySize = "3256472";
TotalVisibleMemorySize = "1363400";
Version = "5.2.3790";
WindowsDirectory = "C:\\WINDOWS";
};