NetBackup IT Analytics User Guide
- Introduction
- Understand the Portal
- About the Admin tab
- Explore your inventory
- Hierarchy toolbar to organize your data
- Show objects
- Use attributes to organize your data
- Pin reports - saving reports with inventory objects
- Assign attributes in the inventory list view
- Get acquainted with reports
- About badging
- Generate and maintain reports
- Select Report Scope
- Group hosts by attributes
- Search for hosts in the report Scope Selector
- Backup Manager advanced scope selector settings
- Solution reports scope selector settings
- Units of Measure in Reports
- Customize report filter logic
- Sort columns in reports
- Convert tabular report to chart
- Distribute, share, schedule, and alert
- Scheduling Exported Reports and Dashboards
- Organize reports
- Work with the dynamic template designer
- Dynamic Template Designer Quick Start
- Converting to a Homogeneous, Product-Specific Template
- Dynamic Template Function Configurations
- Create Fields with the Field Builder
- Scope Selector Component - Custom Filter
- Configure a Bar Chart Dynamic Template
- Steps to Create a Bar Chart Dynamic Template
- Configure an Area/Stacked Area Chart Dynamic Template
- Line Charts for Performance Metrics
- Line Chart Field Requirements
- One Object Per Line Chart, One or More Metrics Per Chart
- Multiple Objects Per Line Chart, One Metric Per Chart
- Example of a Stacked Bar Chart Dynamic Template
- Create a Sparkline Chart in a Tabular Dynamic Template
- Adding or Editing Methods
- Validate and Save a Method
- Work with the SQL template designer
- Database Published Views
- Create a SQL Template
- Configure SQL Template Scope Selector Components
- Sample SQL Queries
- Configure SQL Template Scope Selector Components
- Format the SQL Template Output
- Configure a Table in the SQL Template Designer
- Advanced SQL Report Template Options
- Export/Import SQL Templates
- Pipelined functions for report query building
- APTlistOfDates
- aptStringConcat
- getServerAttributeValue
- getObjectAttributeValue
- getChildServerGroupContextById
- getServerGroupContextById
- secsToHoursMinSecs
- APTgetTapeDriveStatusName
- getFullPathname
- listJobSummaryAfterRestart
- listJobSummaryAfterRestartNBW
- listJobSummaryAfterRestart for NetWorker Backup Jobs
- listOfBackupWindowDates
- listChargebackCatByVOLSDetail
- listChargebackCatByNcVolDetail
- listChargebackCatByFSDetail (for HNAS)
- listChargebackCatByFSDetail (for EMC Isilon)
- listChargebackByLUNSummary
- listChargebackByLUNDetail
- listChargebackCatByLUNSummary
- listChargebackCatByLUNDetail
- Alert configuration
- Manage hosts, backup servers, and host groups
- Manage attributes and objects
- Provide Portal access and user privileges
- Setting / Resetting passwords
- Managing user group home pages (Administrator)
- Configure master schedules and backup windows
- Add, edit, and move policies
- Add/Edit a threshold policy
- Capacity Chargeback policy types
- Solutions administration
- Manage and monitor data collection
- About data collection tasks
- Add/Edit data collectors
- Review collectors and collection status
- Upgrade Data Collectors
- Work with Capacity Manager host data collection
- Host Access Privileges, Sudo Commands, Ports, and WMI Proxy Requirements
- Host access requirements
- Manage credentials
- Configure host discovery policies to populate the host discovery and collection view
- Discovery processes
- Validate host connectivity
- Search and export in host discovery and collection
- Propagate probe settings: Copy probes, paste probes
- Discovery policies for Veritas NetBackup
- About Discovery types
- View and manage system notifications
- Customize with advanced parameters
- Use cases for advanced parameters
- Access control advanced parameters
- General Data Collection advanced parameters
- Cloud data collection advanced parameters
- Host discovery and collection advanced parameters
- Backup Manager advanced parameters
- Capacity Manager advanced parameters
- File Analytics advanced parameters
- Virtualization Manager advanced parameters
- Manage your Portal environment
- Analyze files
- Troubleshoot the Portal
- Retrieving log files
- Debug
- Attribute inheritance overrides
- Understanding report data caching
Add/Edit data collectors
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 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.
To add a Data Collector
- Select Admin > Data Collection > Collector Administration. 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.
- Click Add Collector.
To Edit a Data Collector
- Search for Collector by name. Search returns results at the folder level and within the folder.
Alternatively, select Admin > Data Collection > Collector Administration to browse for a collector. A list of currently configured Portal Data Collectors is displayed.
- Select a Data Collector from the list.
- Click Edit.
- Enter or modify fields as necessary.
- Generate a key file if required.
Field | Description |
---|---|
Collector Name* | The collector name cannot include a space and is case sensitive. The names should match exactly as entered in the Data Collector configuration screen and the Data Collector Installer screen. 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 “To change the User ID and Passcode on the Data Collector Server”. |
Passcode* | Edit the passcode assigned to this Data Collector. It can be any character sequence. Unlike other system passwords (which are encrypted and then saved) this Data Collector passcode is not encrypted prior to saving in the 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. You can use the following OS-specific special characters in the passcode. Make sure the special characters you include are supported on the OS where the Data Collector is installed.
|
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. |
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. |
Generate Key | This creates a key file required for asymmetric encryption, also known as public-key cryptograph. This provides additional security when data is collected. Click to generate the key file and download it to your local system. This is required for new installations and optional for upgrade scenarios. Note: When generating a replacement key, for example a key is lost or data has been corrupted the following applies:
|
To change the name of the data collector
The Data Collector uses a name and a passcode to identify itself with the Data Receiver. If this name or passcode is changed on the Portal, it must be changed on the Data Collector server. If this does not occur, collection will stop.
- Search for Collector by name. Search returns results at the folder level and within the folder.
Alternatively, select Admin > Data Collection > Collector Administration to browse for a collector. A list of currently configured Portal Data Collectors is displayed.
- Select a Data Collector from the list.
- Click Edit.
- Click Change
- Enter the new name.
To change the User ID and Passcode on the Data Collector Server
- Find and update the User ID and Passcode 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.