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
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. IT Analytics Foundation License Inclusions and Implementation Guide
  3. Section III. Data Collector Policy Configuration and Reports
  4. Configure Backup Exec
  5. Architecture overview (Veritas Backup Exec)
IT Analytics Foundation License Inclusions and Implementation Guide

Architecture overview (Veritas Backup Exec)

The following diagram provides an example of how the Data Collector could be deployed in your environment.

Figure 1 Data Collector in a Veritas Backup Exec Environment

For each Backup Exec server, the Data Collector will establish connections to the Backup Exec database. The connection information for each Backup Exec server is retrieved from the Portal or from a locally stored, encrypted file. This connection information includes parameters such as the Administrator user name, domain name and password, server host name and/or IP address.

The Data Collector will use database commands via TCP/IP to obtain its information from each Backup Exec server. The information is stored in the Portal database, enabling a global view of all of the backup servers and clients.

Feedback

Was this page helpful?
Previous

Introduction

Next

Backup Exec terminology

Feedback

Was this page helpful?