Pre-Installation Setup for CommVault Simpana > Adding/Editing Data Collectors (CommVault Simpana)
  
Version 9.2.01
Adding/Editing Data Collectors (CommVault Simpana)
To enable the Data Collector server to pass data to the Portal server, a corresponding Data Collector must be created in the Portal, along with Data Collector Policies for each of the vendor-specific enterprise objects. Data Collector Policies are specific to the type of data that is being collected; however, multiple types of policies often can be combined within one Data Collector.
The first step is to create a Data Collector. Once created, you can add enterprise object policies to it. Often one Portal Data Collector is sufficient for adding Data Collector policies for a variety of enterprise objects such as backup servers, arrays, and switches.
For information about upgrading data collectors, refer to the Installation and Upgrade Guides for Windows or Linux.
Note: For upgrading TSM Data Collectors from ANY release previous to 9.2.01, you must uninstall and then perform a fresh install of the TSM Data Collectors. This is different from the upgrade methods for other collectors.
To Add a Portal Data Collector
1. Select Admin > Data Collection > Collectors. The list of currently configured Portal Data Collectors is displayed. If a Data Collector has already been created, rather than creating a new Data Collector, you may want to add your collection policies to an existing Data Collector.
2. Click Add and select Collector to create a new Data Collector. Refer to the details listed in To Edit a Portal Data Collector.
To Edit a Portal Data Collector
1. Select Admin > Data Collection > Collectors. The list of currently configured Portal Data Collectors is displayed.
2. Select a Data Collector from the list.
3. Click Edit.
4. Enter or modify fields as necessary.
Field
Description
Sample Values
Collector Name*
The collector name cannot include a space.
Click Change to edit the unique name assigned to this Data Collector. The Data Collector will use this value for authentication purposes.
Changing the Collector ID or passcode requires manual changes to the corresponding Data Collector server. Collection will break if these corresponding changes are not made. See User ID and Passcode on the Data Collector Server.
BUEdc1
TSMdc1
HRdc1
Passcode*
Click Change to edit the passcode assigned to this Data Collector. It can be any character sequence.
Unlike other StorageConsole passwords (which are encrypted and then saved) this Data Collector passcode is not encrypted prior to saving in the StorageConsole database and may appear as clear case in certain files. It simply is intended as a “handshake” identification between the data collector and the policy.
Changing the Collector ID or passcode requires manual changes to the corresponding Data Collector server. Collection will break if these corresponding changes are not made. See User ID and Passcode on the Data Collector Server.
Password1
Short Notes
Descriptive notes associated with this Data Collector.
 
Enable SSL
Both secure (SSL) and non-secure Data Collectors can send data to the same Portal. Check this box to select the secure communication protocol (https) that the Data Collector will use.
This check box will not appear in the dialog box if SSL is not enabled in your environment. The Portal data receiver must be listening for https traffic; for example:
https://agent.mycollector.com
 
Auto-upgrade aptare.jar
Indicate if you want this configuration file upgraded automatically.
This part of the Data Collector is responsible for event and metadata processing threads. The .jar file contains the processing and parsing logic for data collection. The latest versions can be downloaded automatically and applied to the collector during upgrades. It is recommended that this setting be set to Yes.
Yes
Auto-upgrade Upgrade Manager
Indicate if you want this configuration bundle upgraded automatically.
This data collector component is responsible for managing Data Collector upgrades. The latest versions can be downloaded automatically and applied to the collector during upgrades. It is recommended that this setting be set to Yes.
Yes
User ID and Passcode on the Data Collector Server
Warning: Any Portal changes to the Data Collector Policy User ID and Passcode require manual modifications on the Data Collector server. Corresponding changes must be made to files on the Data Collector server so that it can continue to communicate with the Portal.
To change the User ID and Password on the Data Collector Server
1. Find and update the User ID and Password in each of the OS-specific files listed below. These entries are typically in the last line of a long string of configuration settings.
Windows:
\<HOME>\mbs\bin\updateconfig.bat
\<HOME>\mbs\conf\wrapper.conf
Example:
\opt\aptare\mbs\bin\updateconfig.bat
\opt\aptare\mbs\conf\wrapper.conf
Linux:
/<HOME>/mbs/bin/updateconfig.sh
/<HOME>/mbs/conf/startup.sh
Example:
/opt/aptare/mbs/bin/updateconfig.sh
/opt/aptare/mbs/conf/startup.sh
Note: Restart the Data Collector to trigger the updates.