NetBackup, available in both a centralized and distributed model, is lightweight and non-disruptive. Essentially the only task it performs directly is to parse, serialize, compress and transmit data returned from the NetBackup commands. All configuration information is maintained in the database on the Portal. All communication between the master server and the portal is initiated by the collector. The portal will never try to make a connection with the master server, thus protecting the security of the master server.

For each Backup Exec server, the Backup Manager Data Collector establishes 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 hostname and/or IP address.

The Data Collector uses 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.

The Data Collector uses connection information to the management control system (MCS) database located on the Avamar utility node. This includes the hostname or IP address of the node, and the username and password to gain read-only access to the MCS database views.

For each NetWorker Server, the Backup Manager Data Collector will establish connections to the database using the command, nsradmin. The connection information for each NetWorker 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 hostname and/or IP address.

The Data Collector uses the command line utilities such as mminfo, nsradmin, and nsrinfo to obtain its information from each NetWorker Server. The Data Collector also used ssh to connect to remote NetWorker Servers to retrieve log file details. This information is stored in the Portal database, enabling a global view of all of the backup servers and clients.

For each TSM instance, the Backup Manager Data Collector establishes connections to the database using the command, dsmadmc. The Data Collector Configuration file contains all the connection information for each TSM Instance including such parameters as the TSM user name and password for login, the TSM Instance name, IP address of the TSM Host Server, and the TSM Port.

The Backup Manager Data Collector will use various QUERY and SELECT commands via dsmadmc to obtain its information from each separate TSM Instance. The information is then sent via http(s) to the Portal.

The Backup Manager Data Collector establishes connections to the HPDP Cell Manager Server and collects data using the commands: omnicellinfo, omnicc, omnirpt, and omnimm. The Data Collector Configuration file contains all the connection information.

The Data Collector connects to the Commvault Simpana CommServe database via JDBC to issue SQL queries (including execution of some read-only functions). To collect more detailed information about individual jobs, the Data Collector connects to the CommServe server via WMI and executes the sendLogFiles.exe tool to retrieve the client log files. These are then retrieved from the administrative share. To retrieve this more detailed information, a Windows logon with administrative access to the CommServe server must be supplied.