NetBackup IT Analytics System Administrator Guide
- Introduction
- Preparing for updates
- Backing up and restoring data
- Monitoring NetBackup IT Analytics
- Accessing NetBackup IT Analytics reports with the REST API
- Defining NetBackup estimated tape capacity
- Automating host group management
- Categorize host operating systems by platform and version
- Bulk load utilities
- Automate NetBackup utilities
- Scheduling utilities to run automatically
- Attribute management
- Importing generic backup data
- Backup job overrides
- Managing host data collection
- System configuration in the Portal
- Custom parameters
- Performance profile schedule customization
- LDAP and SSO authentication for Portal access
- Change Oracle database user passwords
- Integrate with CyberArk
- Tuning NetBackup IT Analytics
- Working with log files
- Portal and data collector log files - reduce logging
- Data collector log file naming conventions
- Portal log files
- Defining report metrics
- SNMP trap alerting
- SSL certificate configuration
- Configure virtual hosts for portal and / or data collection SSL
- Keystore on the portal server
- Portal properties: Format and portal customizations
- Data retention periods for SDK database objects
- Data aggregation
- Troubleshooting
- Appendix A. Kerberos based proxy user's authentication in Oracle
- Appendix B. Configure TLS-enabled Oracle database on NetBackup IT Analytics Portal and data receiver
- Appendix C. NetBackup IT Analytics for NetBackup on Kubernetes and appliances
Starting and stopping portal server software
Restarting the Portal Server does not have a negative impact on the Data Collector, assuming that the Data Collector established an initial connection to the Portal Server. You do not need to restart the Data Collector after you restart the Portal Server. If the Data Collector is sending data at the time that the Portal Server becomes unavailable, the Data Collector receives an error, and then tries to send the information again. The Data Collector continues to retry and sends alerts until it can reconnect and retransmit.
When you start the Portal Server software, you will start all services that are not already running. How you start and stop the Portal Server software depends on your operating system. Choose the procedure that represents your operating system:
To start Portal Server software on Windows
- Locate the script to start the Portal Server software:
C:\opt\aptare\utils\startportal.bat
- Double-click to start the software.
- Verify the following services are running using the Windows Services Control panel:
APTARE Agent Tomcat
APTARE Apache
APTARE Portal Tomcat
Oracle Service SCDB
OracleSCDBTNSListener
To stop Portal Server software on Windows
- Locate the script to stop the Portal Server software:
C:\opt\aptare\utils\stopportal.bat
- Double-click to stop the software.
- Verify the following services are stopped using the Windows Services Control panel:
APTARE Portal Tomcat
To start Portal Server software on Linux
- As user root, run one of the following commands:
# cd /opt/aptare/bin ./tomcat-portal start|restart
Individual component startup scripts can be found in the /opt/aptare/bin directory. Startup log files can be found in the /opt/aptare/logs directory.
To stop Portal Server software in Linux
- As user root, run the following commands:
# cd /opt/aptare/bin ./tomcat-portal stop
Individual component startup/shutdown scripts can be found in the /opt/aptare/bin directory. Shutdown log files can be found in the /opt/aptare/logs directory.