NetBackup IT Analytics Data Collector Notes and Troubleshooting
- Data Collector Troubleshooting
- Resolving Data Collectors connections issues - Linux specific
- Resolving Data Collectors connections issues - Windows specific
- Portal upgrade performance issues
- Verify the Data Collector configuration
- Verify Connectivity
- Configuring web proxy updates
- Collecting missed events for Veritas Backup Exec
- Substituting ODBC for JDBC to connect to SQL server for Veritas Backup Exec
- Useful Data Collection scripts for capacity
- Host resources troubleshooting
- Host resources: Check the status of the WMI proxy server
- Host resources: Post-Installation verification
- Host resources: Check host connectivity using standard SSH
- Host resources: Check host connectivity
- Host resources: Check host connectivity using Host Resource Configuration file
- Host resources: Generating host resource configuration files
- Host resources: Check the execution of a command on a remote server
- Host resources Data Collection
- Host resources: Collection in stand-alone mode
- Configuring parameters for SSH
- Identifying Windows file system access errors (File Analytics)
- Collect from remote shares (File Analytics)
- Adding a certificate to the Java keystore
- Override default Java Heap memory (XMX) value for Data Collector utilities
- Firewall Configuration: Default Ports
- CRON Expressions for Policy and Report Schedules
- Clustering Data Collectors with VCS and Veritas NetBackup (RHEL)
- Clustering Data Collectors with VCS and Veritas NetBackup (Windows)
- Install and configure NetBackup IT Analytics Data Collector on MSCS environment
- Firewall Configuration: Default Ports
- Maintenance Scenarios for Message Relay Server Certificate Generation
Override default Java Heap memory (XMX) value for Data Collector utilities
You may require to override the default Java Heap Memory (XMX) value to avoid performance degradation or potential "OutOfMemoryError" exceptions. The following procedure provides the override steps for Windows and Linux hosts.
To override the default XMX value for Data Collector Windows batch scripts, uncomment the XMX variable in dc_override_config.bat present in the mbs\conf directory and provide the updated XMX value. The comment in the batch file will guide you to identify the variable to be overridden for the script you are interested.
Example: Override XMX value for checkinstall.bat script
Update XMX value in dc_override_config.bat
:: checkinstall.bat
XMX_CHECK_INSTALL=-Xmx17gThe backup of the dc_override_config.bat is saved to the mbs\conf directory with the name dc_override_config.bat_bkp.
Note:
Use :: only for comment and at the beginning of the line.
To override the default XMX value for Data collector Linux batch scripts, uncomment the XMX variable in dc_override_config.sh present in the mbs/conf directory and provide the updated XMX value. The comment in the shell script file will guide you to identify the variable to be overridden for the script you are interested.
Example: Override XMX value for checkinstall.sh script
Update XMX value in dc_override_config.sh
#checkinstall.sh
XMX_CHECK_INSTALL=-Xmx17gThe backup of the dc_override_config.sh is saved to the mbs\conf directory with the name dc_override_config.sh_bkp.
Note:
Use # only for comment and at the beginning of the line.