Veritas NetBackup™ OpsCenter Administrator's Guide
- Overview of NetBackup OpsCenter
- About OpsCenter
- About OpsCenter components
- About starting the OpsCenter console
- About accessing the OpsCenter console
- Logging on to the OpsCenter console as a default admin user
- About OpsCenter console components
- About the View pane
- Sizing the Content pane
- About using tables
- Customizing tables for your needs
- Installing OpsCenter
- About planning an OpsCenter installation
- About the OpsCenter licensing model
- Managed NetBackup master server considerations
- About designing your OpsCenter Server
- About planning an OpsCenter Agent deployment
- Installing OpsCenter on Windows and UNIX
- About installing OpsCenter on Windows
- About installing OpsCenter on UNIX
- About installing OpsCenter silently on Windows
- About OpsCenter upgrade on Windows and UNIX
- About post-installation tasks
- About uninstalling OpsCenter on Windows and UNIX
- About clustering OpsCenter
- Clustering OpsCenter on Windows
- Uninstalling OpsCenter from the Windows cluster
- About planning an OpsCenter installation
- OpsCenter Getting Started feature
- Administering OpsCenter
- About OpsCenter services and processes used by OpsCenter
- OpsCenter server scripts on Windows and UNIX
- About OpsCenter database administration
- OpsCenter database commands
- Moving OpsCenter server to a different computer
- About backup and restore of OpsCenter and OpsCenter Analytics
- About communication ports and firewall considerations in OpsCenter
- About OpsCenter log files
- About OpsCenter log files on Windows servers
- About OpsCenter log files on UNIX servers
- 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 data collection in OpsCenter
- About managing OpsCenter Agents
- About managing OpsCenter Data Collectors
- About configuring data collection for NetBackup
- About the Breakup Jobs option
- Viewing master server details and data collection status
- Collecting data from PureDisk
- Managing OpsCenter views
- About OpsCenter views
- About managing OpsCenter 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
- OpsCenter Alert conditions
- Adding an alert policy
- About managing NetBackup storage
- Manage > Storage > Storage Unit view
- Manage > Storage > Storage Unit Group view
- Manage > Storage > Storage Lifecycle Policy view
- About managing NetBackup devices
- Manage > Devices > Drive view
- Manage > Devices > Robot view
- Manage > Devices > Disk Pool view
- Manage > Devices > SAN Client view
- Manage > Devices > FT Server view
- About Operational Restore and Guided Recovery operations
- About Operational Restores from OpsCenter
- Files and Directories Restore Wizard
- Select Files or Directories panel
- Summary panel
- About OpsCenter Guided Recovery
- Troubleshooting Guided Recovery
- About Operational Restores from OpsCenter
- 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 Custom Report Wizard parameters
- 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. Additional information on PureDisk data collection
- Appendix B. Attributes of NetBackup data
- Appendix C. Man pages for CLIs
- Appendix D. Creating views using CSV, TSV, and XML files
- Appendix E. Error messages in OpsCenter
OpsCenter Alert conditions
OpsCenter comes with a set of predefined alert conditions. You can create alert policies based on these alert conditions to detect when something goes wrong in your NetBackup environment and troubleshoot NetBackup. The alerts help you to anticipate and handle problems before they occur. You can receive these alerts by logging on to OpsCenter, and also by email or SNMP traps. You can specify email and SNMP recipients while creating an alert policy.
Alert conditions can be divided into the following categories:
Event-based alert conditions
For these alert conditions, OpsCenter retrieves data from NetBackup based on notifications from NBSL.
Periodic alert conditions
For these alert conditions, OpsCenter retrieves data from NetBackup based on a wait time (of up to 15 minutes).
Table: Alert conditions in OpsCenter lists the alert conditions, alert category, and descriptions.
Table: Alert conditions in OpsCenter
High job failure rate
An alert is generated when the job failure rate becomes more than the specified rate.
An alert is generated when a job hangs (runs for more than the specified time) for a selected policy or a client for a specified period. The Hung Job condition is checked every 15 minutes. Depending upon when a job starts within a check cycle, an alert may not occur.
For Hung Job alert, you can configure OpsCenter to ignore the time for which a job is in a queued state. While checking the Hung Job condition, OpsCenter considers the start time of a job by default. This also includes the time for which a job is in a queued state. A job may not always be in an active state after it starts. Due to unavailability of resources, a job may first be in a queued state before it becomes active.
If you configure OpsCenter to ignore the queued time for a job, OpsCenter considers the time when a job becomes active while checking the Hung Job condition. Note that the active start time of the first attempt is considered.
For example, suppose a policy is created with a job threshold of 25 minutes. A job starts 10 minutes after a first check cycle and ends 13 minutes after the third check cycle is done. This time is a total execution of 33 (5 + 15 + 13) minutes, but an alert is not raised.
In this case, the policy is checked four times. The job was not yet started during the first check, was running less than the threshold during the second (job duration = 5 minutes) and third checks (job duration = 20 minutes), and the job completes (job duration = 33) before the fourth check.
If a job starts at 4 minutes after a first check, an alert is raised at the third check, since the job has executed for 26 minutes (11 + 15 minutes).
An alert is generated when a job of specified type, of the specified policy or client ended in the specified status.
An alert is generated when a job of a specified type of the specified policy or client moves to an Incomplete state.
An alert is generated when any of the selected media is frozen.
An alert is generated when any of the selected media is suspended.
Exceeded max media mounts
An alert is generated when a media exceeds the threshold number of mounts.
Media required for restore
An alert is generated when a restore operation requires media. The restore operation may require a specific media which contains the specific image to be restored.
Low available media
An alert is generated when the number of available media becomes less than the predefined threshold value.
When you select All Master Server from the View drop-down list, low available media alert raises separate alerts for all the master servers listed under All Master Server. For example: If there are 5 master servers present under the All Master Servers view, opscenter will raise 5 alerts for each master server.
High suspended media
An alert is generated when the percentage of suspended media exceeds the predefined threshold value.
High frozen media
An alert is generated when the percentage of frozen media exceeds the predefined threshold value.
Zero Cleaning Left
An alert is generated when a cleaning tape has zero cleaning left.
Catalog Space low
An alert is generated when space available for catalogs becomes less than the threshold value or size. For Catalog Space low condition, you can specify the threshold value for a particular policy in percentage, bytes, kilobytes (KB), megabytes (MB), gigabytes (GB), terabytes (TB) or petabytes (PB) and generate alerts. The generated alert can also show available catalog space using these units.
Catalog not Backed up
An alert is generated when catalog backup does not take place for a predefined time period.
This does not necessarily mean that if you do not receive this alert, the catalog backup was successful.
Catalog Backup Disabled
An alert is generated when all the catalog backup policies are disabled. If the policy has been defined for a server group, an alert is generated for every master server within the group that satisfies this criteria. The alert is not generated if no catalog backup policy exists for a master server.
An alert is generated on a media mount request.
No Cleaning Tape
An alert is generated when no cleaning tapes are left.
Drive is Down
An alert is generated when a drive in a specified robot or media server in the selected server context goes down.
High Down Drives
An alert is generated when the percentage of down drives exceeds the predefined threshold value.
An alert is generated when specific events occur in the NetApp devices.
See Adding an alert policy .
Disk Pool Full
An alert is generated when a disk pool(s) reaches the high water mark. An alert policy based on Disk Pool Full condition generates an alert only when the used capacity of the disk pool reaches the high water mark.
Disk Volume Down
An alert is generated when the selected disk volume(s) is down.
Low Disk Volume Capacity
An alert is generated when a disk volume capacity is running below the threshold limit.
Agent Server Communication break
An alert is generated when the communication between Agent and OpsCenter Server breaks. By default, this alert is automatically cleared when the communication is re-established.
An alert policy based on the Agent Server Communication Break condition is always based on the ALL MASTER SERVERS view. If you created an alert policy based on the Agent Server Communication Break condition, and you do not have access to the ALL MASTER SERVERS view, alerts are not generated for the alert policy.
Master Server Unreachable
An alert is generated when OpsCenter loses contact with the master server. This alert condition means that the connection between OpsCenter and the managed NetBackup master server is lost. It does not necessarily mean that NetBackup backups are not working.
Lost Contact with Media Server
An alert is generated when OpsCenter loses contact with the media server.
Appliance Hardware Failure
An alert is generated in case of OpsCenter Appliance hardware failure.
An alert is generated when the selected appliance hardware fails.
You can set this alert condition to monitor your NetBackup or deduplication appliance hardware.
Job Policy Change
An alert is generated when a policy attribute for a job policy is changed. Multiple alerts are generated if multiple attributes are changed for a job policy
If you select a particular job policy, only the selected job policy is monitored for change. If you do not select any job policy, all the job policies are monitored for changes.