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
How the events are generated
When you configure disk pools in NetBackup, NetBackup connects to the DFM server through the NetApp NetBackup plug-in. The plug-in scans the volumes that are not protected and takes some time to find out the details of unprotected volumes. If the primary server asks for the event list while the event list is being prepared, then the same primary server who triggered this does not receive the events at that time. However, the primary servers which connect to the DFM server after the event list is prepared receive those events. After every 24 hours from the time the first call is made, the current list of events are sent again to all primary servers that are connected to this DFM server. Currently this is a fixed cycle unless NetBackup is restarted. Maximum eight event channels are supported by default which means that maximum eight primary servers are capable of receiving events from DFM. If more than eight primary servers are connected to the DFM server and all are monitored by OpsCenter then it is not predictable which eight primary servers receive those events.
The value for maximum number of event channels is configurable in a file on the NetBackup plug-in host (usually the same as DFM host):
Windows |
C:\Program Files\netapp\NBUPlugin\config\NBUPlugin.cfg |
UNIX |
/usr/NetApp/NBUPlugin/config/NBUPlugin.cfg ([ NBUPlugin:NumEvCh ] Value=8) |
It is recommended that the value for maximum event channels is configured as 8. Increasing the value may affect the DFM performance.
Consider a scenario where one primary server is connected to one DFM server and is monitored by OpsCenter. When NetBackup initially connects to the NetApp NetBackup plug-in, then it does not receive any event until the complete cycle of 24 hours assuming that the event cycle is of 24 hours. After 24 hours, the events are sent to OpsCenter by NBSL. So even if the condition like Volume almost Full has occurred, you see events only after the cycle is complete.
Consider a scenario where multiple primary servers monitored by OpsCenter are connected to one DFM server. In this scenario, the first primary server that connects to the DFM server by NetApp NetBackup plug-in never receives the event for the first cycle. The primary servers which connect later receive events only if they are connected after DFM prepares the event list. No events are sent in the time between when the first primary server connected to DFM server and the time DFM is ready with events. If some primary server connects during that time then it does not receive any events. Which primary servers receive the events depends a lot on when they connect to the NetApp NetBackup plug-in. But after 24 hours, all primary servers should receive the events from NetApp NetBackup plug-in provided that maximum eight primary servers are connected.