APTARE IT Analytics Data Collector Installation Guide for Backup Manager
- Introduction
- Pre-Installation setup for Commvault Simpana
- Open TCP/IP access to the Commvault database
- Set up a read-only user in the CommServe server
- Pre-Installation setup for Cohesity DataProtect
- Pre-Installation setup for EMC Avamar
- Import EMC Avamar server information
- Pre-Installation setup for EMC Data Domain backup
- Pre-Installation setup for EMC NetWorker
- Architecture overview (EMC NetWorker)
- Pre-Installation setup for Dell EMC NetWorker backup & Recovery
- Pre-Installation setup for generic backup
- CSV format specification
- Pre-Installation setup for HP Data Protector
- Architecture overview (HP Data Protector)
- Configure the Data Collector server in Cell Manager (HP Data Protector)
- Pre-Installation setup for IBM Spectrum Protect (TSM)
- Architecture overview (IBM Spectrum Protect -TSM)
- Import IBM Spectrum Protect (TSM) information
- Pre-Installation setup for NAKIVO Backup & Replication
- Pre-Installation setup for Veritas Backup Exec
- Pre-Installation setup for Veritas NetBackup
- Prerequisites to use SSH and WMI (Veritas NetBackup)
- Prerequisites for NetBackup collection over SSH (Kerberos option)
- Veritas NetBackup 8.1 (or later) requirements for centralized collection
- Configuring file analytics in NetBackup Data Collector policy
- Pre-Installation setup for Veritas SaaS backup
- Pre-Installation setup for Oracle Recovery Manager (RMAN)
- Pre-Installation setup for Rubrik Cloud Data Management
- Pre-Installation setup for Veeam Backup & Replication
- Discovery policies for Veritas NetBackup
- About Discovery types
- About SNMP probes
- Installing the Data Collector software
- Validate data collection
- Manually start the Data Collector
- Uninstall the Data Collector
- Appendix A. Load historic events
- Load Veritas NetBackup events
- Appendix B. Firewall configuration: Default ports
Upgrade troubleshooting: Microsoft SQL Server and Java 11
With the introduction of support for Java 11, older versions of MS SQL Server may encounter compatibility issues. The following section covers potential workarounds. Collection occurs from the Microsoft SQL Server database used by the system the data collector is collecting from. The version of Java used by APTARE IT Analytics disables some insecure TLS algorithms by default. If collection fails with the following error in the collector logs, the version of MS SQL Server may be incompatible and not allow collection using the TLS algorithms enabled by default with Java 11.
Failed to establish JDBC connection to: jdbc:jtds:sqlserver://... java.sql.SQLException: Network error IOException: null at net.sourceforge.jtds.jdbc.JtdsConnection.<init> (JtdsConnection.java:437)
Upgrade MS SQL Server to the latest version to enable secure collection. Your MS SQL Server version may not be supported. If upgrade is not possible, a workaround can be attempted to restore compatibility. If the following steps do not resolve the issue, your version of MS SQL Server is not supported.
Use the following steps to modify the enabled algorithms to attempt communication with the data collector. Note that using this workaround will reduce the security of your collection. The default list of disabled algorithms is taken from Java 11.0.6 and may change in later versions.
Edit <collector install dir>/java/conf/security/java.security.
Search for jdk.tls.disabledAlgorithms.
Copy the existing lines and comment (to have a backup for easy restore).
#jdk.tls.disabledAlgorithms=SSLv3, RC4, DES, MD5withRSA, DH keySize < 1024, \ # EC keySize < 224, 3DES_EDE_CBC, anon, NULL jdk.tls.disabledAlgorithms=SSLv3, RC4, DES, MD5withRSA, DH keySize < 1024, \ EC keySize < 224, 3DES_EDE_CBC, anon, NULL
One at a time, remove an algorithm from the jdk.tls.disabledAlgorithms and test the collection, starting at the last algorithm and working backward. Stop once you reach an algorithm containing 'keySize <'.
Remove one algorithm - for example NULL
jdk.tls.disabledAlgorithms=SSLv3, RC4, DES, MD5withRSA, DH keySize < 1024, \ EC keySize < 224, 3DES_EDE_CBC, anon
Save the file.
Run checkinstall and verify collection succeeds.
If checkinstall does not succeed, restore jdk.tls.disabledAlgorithms to its original state.
Change to DH keySize<768 - for example.
jdk.tls.disabledAlgorithms=SSLv3, RC4, DES, MD5withRSA, DH keySize < 768, \ EC keySize < 224, 3DES_EDE_CBC, anon, NULL
Save the file.
Run checkinstall and verify collection succeeds.
If a working configuration is found, restart the collector service.