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
Probe Settings
Table: Probe Settings
Probe Type | Parameters | Description |
---|---|---|
Capacity, HBA, iSCSI, Volume Manager, Multi-pathing | Probe schedule* | A schedule in cron format; for example: */20 9-18 * * * which translates to "every 20 minutes between the hours of 9 a.m. and 6 p.m." |
Memory | Probe schedule* | A schedule in cron format; for example: */20 9-18 * * * which translates to "every 20 minutes between the hours of 9 a.m. and 6 p.m." |
Network | Probe schedule* | A schedule in cron format; for example: */20 9-18 * * * which translates to "every 20 minutes between the hours of 9 a.m. and 6 p.m." |
Process | Probe schedule* | A schedule in cron format; for example: */20 9-18 * * * which translates to "every 20 minutes between the hours of 9 a.m. and 6 p.m." |
Performance | Probe schedule* | For Windows, only CPU performance will be collected. For Linux, both CPU and device performance will be collected. CPU performance includes CPU allocation and usage. Device performance includes throughput and latency for disk partitions. Note: The sysstat utility must be installed on the Linux servers or storage nodes for Linux host performance data collection. A schedule in cron format; for example: */20 9-18 * * * which translates to "every 20 minutes between the hours of 9 a.m. and 6 p.m." |
System | Probe schedule* | A schedule in cron format; for example: */20 9-18 * * * which translates to "every 20 minutes between the hours of 9 a.m. and 6 p.m.". |
Exchange | Collect | Check this box to activate collection on an on-going basis. When it is unchecked, only initial validation will attempt this probe. |
Probe schedule | A schedule in cron format; for example: */20 9-18 * * * which translates to "every 20 minutes between the hours of 9 a.m. and 6 p.m." | |
Active Directory Host | Host name or address | |
Active Directory Port | For example: 389 | |
Active Directory Base DN* | The starting point for the Active Directory. For example: CN=Services,CN=Configuration, DC=contoso2003,DC=com Several tools are available to help you identify the Base DN: http://support.microsoft.com/kb/224543 -http://technet.microsoft.com/en-us/library/cc773354(WS.10).aspx - | |
Active Directory User Name | Active Directory User Name This username must have privileges to search under the base DN within the Active Directory. Typically, this is an Administrator. | |
Password | Active Directory Password | |
SQL Server | Collect | Check this box to activate collection on an on-going basis. When it is unchecked, only initial validation will attempt this probe. |
Probe schedule | A schedule in cron format; for example: */20 9-18 * * * which translates to "every 20 minutes between the hours of 9 a.m. and 6 p.m." | |
Database* | The name of the database within the SQL server. | |
Instance | The system identifier to identify the SQL server database instance--for example: BKUPEXEC. Specify either an instance name or a port. If an instance name is not specified, MSSQLSERVER is substituted. | |
Port | To identify the SQL server instance, provide either an instance name or a database port number; for example: 1433. If a port number is not specified, the port is determined automatically from the instance name. | |
Account* | Database access user name The data collector requires a user account with permissions to execute the stored procedures | |
Password* | Database access password | |
Windows Authentication | Check this box if you want Windows authentication rather than SQL server authentication. | |
Oracle | Collect | Check this box to activate collection on an on-going basis. When it is unchecked, only initial validation will attempt this probe. |
Probe schedule | A schedule in cron format; for example: */20 9-18 * * * which translates to "every 20 minutes between the hours of 9 a.m. and 6 p.m." | |
SID* | The system identifier to identify the database instance. | |
Port* | Database port number; default: 1521 | |
Username* | The Oracle user must have the following role granted: SELECT_CATALOG_ROLE To grant this access, use: GRANT SELECT_CATALOG_ROLE TO 'user' where user is the database Username that you'll provide here. | |
Password* | Database access password | |
Oracle ASM | Collect | Check this box to activate collection on an on-going basis. When it is unchecked, only initial validation will attempt this probe. |
Probe schedule | A schedule in cron format; for example: */20 9-18 * * * which translates to "every 20 minutes between the hours of 9 a.m. and 6 p.m." | |
Account* | The Oracle user privileges required: SYSDBA privilege if 10g sysasm in 11g | |
Password* | Database access password | |
Port* | Database port number; default: 1521 | |
ASM Instance* | The name that identifies the database instance. | |
Collect | Check this box to activate collection on an on-going basis. When it is unchecked, only initial validation will attempt this probe. | |
Probe schedule | Default is once a month. A schedule in cron format; for example: */20 9-18 * * * which translates to "every 20 minutes between the hours of 9 a.m. and 6 p.m." |