Backup solutions and versions — NetBackup IT Analytics 11.8 | Cohesity Documentation

Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist

Backup solutions and versions — NetBackup IT Analytics 11.8 | Cohesity Documentation

Backup solutions and versions

Note:

Refer to the Software and Hardware Disclaimer supported and tested by Cohesity.

See Software and hardware disclaimer.

Table: Supported Backup Solutions

Backup Solution	Version	Notes and Access Requirements
Cohesity DataProtect	6.6.x , 6.8.x, 7.1.2 U3, 7.2.1, 7.2.2, 7.3, and 7.4.	REST API on Port 80 or 443
Commvault Simpana	11.x (up to 11.28)	At a minimum, read-only (db_datareader) database access with execute permission is required for the following functions: dbo.GetDateTime dbo.GetUnitTime dbo.GetJobFailureReason dbo.JMGetLocalizedMessageFunc Windows user name and password with administrative access to CommServe Server for WMI (to collect job detail logs). Port 1433 for the MSSQL Server database instance This is usually 1433, but it can be any port. Other Ports, if collecting skipped files details: File sharing: port 445 WMI control channel: TCP port 135 DCOM TCP/UDP: any port greater than 1023
Dell EMC NetWorker Backup & Recovery	19.1 through 19.13	Port 9090 (Used for NetWorker REST API connection) EMC NetWorker data collection policies are implemented based on vendor version number. For EMC NetWorker versions post 9.2.1.x, collection is done using the policy titled: DELL EMC NetWorker Backup & Recovery.
Dell PowerProtect Data Manager	19.15.xx to 19.18.xx	REST API on Port 8443 User with Administrator role.
EMC Avamar	4.x, 5.0, 6.0, 6.1, 7, 7.2, 7.3, 7.5, 18.1, 18.2, 19.1, 19.2, 19.3, 19.4, 19.10	Ports 5555 and 22 (SSH)
EMC Data Domain	5.0, 5.1, 5.2, 5.4, 5.5, 5.6, 5.7, 6.0, 6.1, 6.2, 7.1, 7.2, 7.6, 7.7, 7.10, 8.1	Port 22 (SSH)
HP Data Protector	8.1, 9.0	Port 5555 WMI Proxy range of ports, Linux SSH 22 A WMI Proxy is only needed if collecting from Windows hosts and when the Data Collector is on a server that is different from the Cell Manager server. The HP Data Protector (HPDP) client software version must match the specific version (major and minor) of the HPDP server being probed. If the Data Collector is installed on a Linux OS, a WMI Proxy Server must be installed on a Windows system in order to collect data from a Cell Manager that is installed on a Windows system.
IBM Spectrum Protect (TSM)	6.1, 6.2, 6.3, 7.1, 8.1	TSM instances running on z/OS are not supported. TSM v6.3 is not supported on a Windows 2012 Data Collector. Typically, Port 1500
IBM Spectrum Protect Plus	10.1.6 and 10.1.7	Port: 443 IBM Spectrum Protect Plus user with self-service role for all resource groups.
NAKIVO Backup & Replication	9.1.1	Director Web UI port used during installation (Default: 4443)
Oracle Recovery Manager (RMAN)	11g, 12c	Typically Port 1521
Rubrik Cloud Data Management	v 7.0.4 and above	Port 443
Veeam Backup & Replication	11.0 12.0	Port 9392
Veritas NetBackup including: Sun StorageTek ACSLS Manager SLP	8.1, 8.2, 8.3, 9.0, 9.0.0.1, 9.1, 9.1.0.1, 10.0, 10.1, 10.1.1, 10.2, 10.3, 10.4, 10.5, 11.0, 11.1, and 11.1.0.2. SLP, NetBackup v7.7 and higher.	The Data Collector makes calls to various NetBackup CLI (Command Line Interface) commands, such as bpdbjobs. These commands are a standard component of the NetBackup product and IT Analytics requires that they are operational as per the NetBackup specifications. NetBackup Application data collection is supported on NetBackup BYOD and Appliances form factors like NetBackup Appliances (equivalent versions 2.7.x version onwards), Flex, and Flex Scale Appliances. Centralized data collection is supported using CLI method as well as SSH/WMI interface. For centralized data collection: See Centralized NetBackup Data Collection requirements.
ExaGrid Subsystem TieredBackupStorage	6.4 and above	Dev Mgr/API/CLI: SNMP Server Identification Access Requirements: SNMP Enabled on each appliance Default or custom Community Sting Standard SNMP UDP ports 161 & 162 must be accessible on each appliance Each appliance's SNMP "Appliance Location" should be set to the same value as the ExaGrid "system"/"site" name as seen in the navigation tree All access is read-only Add each ExaGrid appliance's IP/name to the Connector configuration dialog Ports: Standard SNMP UDP ports 161 & 162 must be accessible on each ExaGrid Appliance

Feedback

Was this page helpful?

Feedback

Was this page helpful?