Veritas NetBackup™ OpsCenter Administrator's Guide
- Overview of NetBackup OpsCenter
- About OpsCenter
- About OpsCenter components
- About starting the OpsCenter console
- About OpsCenter console components
- About the View pane
- Sizing the Content pane
- About using tables
- Installing OpsCenter
- About planning an OpsCenter installation
- Installing OpsCenter on Windows and UNIX
- About OpsCenter upgrade on Windows and UNIX
- About post-installation tasks
- About uninstalling OpsCenter on Windows and UNIX
- About clustering OpsCenter
- Getting started with OpsCenter
- Administering OpsCenter
- About the services and processes used by OpsCenter
- OpsCenter server scripts on Windows and UNIX
- About OpsCenter database administration
- About backup and restore of OpsCenter and OpsCenter Analytics
- About communication ports and firewall considerations in OpsCenter
- About OpsCenter log files
- Understanding OpsCenter settings
- Setting user preferences
- About managing licenses
- Configuring the data purge period on the OpsCenter Server
- Configuring SMTP server settings for OpsCenter
- Adding host aliases in OpsCenter
- Merging objects (hosts) in OpsCenter
- Modifying tape library information in OpsCenter
- Copying a user profile in OpsCenter
- Setting report export location in OpsCenter
- About managing Object Types in OpsCenter
- About managing OpsCenter users
- About adding AD / LDAP user groups in OpsCenter
- About managing recipients in OpsCenter
- About managing cost analysis and chargeback for OpsCenter Analytics
- Understanding data collection
- About configuring data collection for NetBackup
- About the Breakup Jobs option
- Viewing primary server details and data collection status
- About configuring data collection for NetBackup
- Managing OpsCenter views
- About OpsCenter views
- About managing OpsCenter views
- Managing static views
- Managing dynamic views
- View filters in OpsCenter
- Monitoring NetBackup using OpsCenter
- Controlling the scope of Monitor views
- About monitoring NetBackup using the Overview tab
- About monitoring NetBackup jobs
- Monitor > Services view
- About monitoring Audit Trails
- Managing NetBackup using OpsCenter
- About managing alert policies
- About creating (or changing) an alert policy
- About managing NetBackup storage
- About managing NetBackup devices
- About Operational Restore and Guided Recovery operations
- About Operational Restores from OpsCenter
- About Guided Recovery
- Troubleshooting Guided Recovery
- About managing NetBackup Hosts
- About managing NetBackup Deployment Analysis
- Data compilation for the Capacity License report
- Generating a Capacity Licensing report
- Supporting Replication Director in OpsCenter
- Understanding and configuring OpsCenter alerts
- About using SNMP
- About using SNMP
- Reporting in OpsCenter
- About OpsCenter reports
- Report Templates in OpsCenter
- About managing reports in OpsCenter
- Creating a custom report in OpsCenter
- About managing My Reports
- About managing My Dashboard
- About managing reports folders in OpsCenter
- About managing report schedules in OpsCenter
- About managing time schedules in OpsCenter
- Appendix A. Attributes of NetBackup data
- Appendix B. Man pages for CLIs
- Appendix C. Creating views using CSV, TSV, and XML files
- Appendix D. Error messages in OpsCenter
OpsCenter application log files
Table: OpsCenter application log files shows details about the application log files.
Table: OpsCenter application log files
Log file directory | Log file | Troubleshooting purpose |
---|---|---|
INSTALL_PATH\OpsCenter\server\logs or <INSTALL_PATH>/SYMCOpsCenterServer/logs |
58330-423-*.log |
This log file has minimal information that helps in understanding the flow of each use case. Unlike *148* logs, this log file does not have detailed log information. This log file can be mainly used by Support to diagnose the problem if a particular use case has failed. An example of a failed use case is when you run a report and any of the pre-defined steps like fetching report definition , building query, converting result etc. fail. Each failed use case will have error code and the message. Currently, data collection and reporting component has well defined error code and messages. This log file also has a detailed stack trace for failed use case. By default, the application logging is enabled. You can disable it by configuring the log.conf file. To disable application logging, set the debug level as 0 in Windows: <INSTALL_PATH>\OpsCenter\server\bin\vxlogcfg.exe -a -p 58330 -o <OID> -s DebugLevel=0 UNIX: /<INSTALL_PATH>/SYMCOpsCenterServer/bin/vxlogcfg -a -p 58330 -o <OID> -s DebugLevel=0 To enable application logging later, you can give any value greater than 0. For example, DebugLevel=1 enables application logging. To disable application logging later, modify the value of DebugLevel to 0. |