Please enter search query.
Search <book_title>...
NetBackup IT Analytics Data Collector Notes and Troubleshooting
Last Published:
2024-09-04
Product(s):
NetBackup IT Analytics (11.3)
- Data Collector Troubleshooting
- Resolving Data Collectors connections issues - Linux specific
- Resolving Data Collectors connections issues - Windows specific
- Portal upgrade / data collector 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
- Firewall Configuration: Default Ports
- CRON Expressions and Probe Schedules
- Clustering Data Collectors with VCS and Veritas NetBackup (RHEL)
- Clustering Data Collectors with VCS and Veritas NetBackup (RHEL)
- Prerequisites
- Getting started with Data Collector clustering
- Main.cf
- Upgrading a clustered Data Collector
- Manage cluster configuration during NetBackup upgrade (RHEL)
- Considerations when Data Collector is pointing to Alta Domain Management
- Clustering Data Collectors with VCS and Veritas NetBackup (Windows)
- Install and configure NetBackup IT Analytics Data Collector on MSCS environment
- Firewall Configuration: Default Ports
- Maintenance Scenarios for Message Relay Server Certificate Generation
Cluster Data Collectors with MSCS on Windows
Assumptions
Microsoft Cluster Server (MSCS) is already provisioned.
NetBackup primary server is already clustered under MSCS and online. on Node1.
A disk of at-least 100 GB size is attached to all nodes in the cluster - to be used for installing NetBackup IT Analytics Data Collector.
Installing and configuring NetBackup IT Analytics Data Collector in MSCS
Steps to be performed on Node1:
- Attach disk of minimum size of 100GB on Node1 for NetBackup IT Analytics.
- Create storage resource for the disk in the cluster.
- Get the storage resource online on Node1 and identify the drive letter.
- Optional: Add Agent URL to
C:\Windows\System32\drivers\etc\hostsfile. This step is required if the agent URL is not updated on the DNS.Example:
10.xx.yy.zz itanalyticsportal.example.com itanalyticsportal 10.xx.yy.zz itanalyticsagent.example.com itanalyticsagent
- Install and Configure NetBackup IT Analytics Data Collector on new drive.
See Install Data Collector Software on Windows in one of the Data Collector installation guides.
- Verify that services Aptare Agent, Aptare Agent Kafka, and Aptare Agent Zookeeper are created on services panel and are online.
- Execute
checkinstall.batutility and ensure it is returning SUCCESS. Thecheckinstall.batutility will be available at[Drive:]/veritas/AnalyticsCollector /mbs/bin. - Change the Startup type for Aptare Agent, Aptare Agent Kafka, and Aptare Agent Zookeeper services from Automatic to Manual from services panel.
- Stop the services for Aptare Agent, Aptare Agent Kafka, and Aptare Agent Zookeeper on Node1.
- Move the storage resource to Node 2 on the cluster.
Steps to perform on Node 2:
- Ensure to move the NetBackup IT Analytics shared disk from Node 1 to Node 2. Go to FailOver cluster manager > Storage > Disks > select ITA Disk.
- On the right side below Actions, select Move Available Storage > Select Node > Select Node 2.
- Optional: Add Agent URL to
C:\Windows\System32\drivers\etc\hostsfile. This step is required if the agent URL is not updated on the DNS.Example:
10.xx.yy.zz itanalyticsportal.example.com itanalyticsportal 10.xx.yy.zz itanalyticsagent.example.com itanalyticsagent
- Create services for Aptare Agent, Aptare Kafka, and Aptare Zookeeper by executing:
For Aptare Agent: <Shared disk Drive>:\Veritas\AnalyticsCollector\mbs\bin\installservice.bat.
For APTARE Agent ZooKeeper Service: <Shared disk Drive>:\Veritas\AnalyticsCollector\mbs\bin\setupZookeeperService.bat.
For APTARE Agent Kafka Service: <Shared disk Drive>:\Veritas\AnalyticsCollector\mbs\bin\setupKafkaService.bat.
Change the service type from Automatic to manual from services panel.
Start the services from
services.msc.
- Ensure
checkinstallutility is returning SUCCESS. Thecheckinstall.batutility will be available at[Drive:]/veritas/AnalyticsCollector/mbs/bin. - Stop the services for Aptare Agent, Aptare Agent Kafka, and Aptare Agent Zookeeper on Node 2.
