Using Veritas NetBackup KM

This section describes the most common operations that can be performed with Veritas NetBackup KM.

Acknowledging Alerts

By default, alerts are acknowledged automatically. If you modified the alert acknowledgement default settings, you will have to manually acknowledge alerts.

Manually Acknowledging Job Alerts

For a particular job instance, if the NBUJobStatus has a value of 1=Suspicious or 2=Failure, it will be set to alert with a status of Warning or Alarm respectively. These alerts can be acknowledged using the menu Acknowledgement > Alert… from the relevant job instance.

To acknowledge job alerts:

  1. In the Console, right-click the Jobs instance > KM Commands > Acknowledgement
  2. Select:
    • Warnings… to view and acknowledge alerts for all jobs with a status of Warning
    • Alarms… to view and acknowledge alerts for all jobs with a status of Alarm
    • All… to view and acknowledge all job alerts (Warnings and Alarms) at once.

Manually Acknowledging Log Alerts

When an error is detected in a monitored log file, it will either appear in NBULogAlarmText or NBULogWarningText and will respectively trigger an Alarm or a Warning on NBULogAlarmCount or NBULogWarningCount.

To acknowledge alerts:

  1. In the Console, right-click the Log instance > KM Commands > Acknowledgement
  2. Select:
    • Warning… to view, select, and individually acknowledge errors in the NBULogWarningText parameter
    • Alarms… to view, select, and individually acknowledge errors in the NBULogAlarmText parameter
    • All… to acknowledge all alerts (Warnings and Alarms) at once without viewing.

Generating Reports

The following reports are available in Veritas NetBackup KM:

  • Daemons > Reports > Daemon List…: lists all running Veritas NetBackup daemons
  • Databases > Reports > Database Backup Information…: reports information about the last catalog database backup
  • Logs > Reports > Messages List…: reports all messages logged in the past 24 hours
  • Mount Requests > Reports > Pending Requests…: reports a list of all mount requests
  • <Policy instance> > Reports > Policy Schedule…: displays the schedule for the selected policy instance
  • Robotic Libraries > Reports > Drive Cleaning Statistics or Standalone Drives > Reports > Drive Cleaning Statistics…: reports the drive cleaning statistics on the current master/media server
  • <Robotic Library instance> > Reports > Robotic Library Contents…: reports the contents of the selected robotic library instance
  • <Volume Pool instance> > Reports > Media List…: reports information on all media in the selected volume pool instance
  • Volume Pools > Reports > Available Media…: reports all available media across all volume pools.

Reports can be saved as a task window by clicking Save As Task. You could then save them as a text file or print them.

Refreshing Parameters

This section describes how to manually refresh parameters without waiting for an automatic polling cycle.

Forcing All Discoveries

To force all discoveries, right-click the server and select:

  • Refresh Process Cache to refresh the PATROL Agent process cache
  • Force Discovery.

The discovery will then be forced on all the KMs loaded on the PATROL Agent and on all the KM applications classes.

Forcing All Data Collectors

To force all data collectors, right-click the server instance and select:

  • Refresh Process Cache to refresh the PATROL Agent process cache
  • Refresh parameters to force all data collectors at the same time.

The NetBackup KM data collectors and all the data collectors defined under the application classes loaded on the PATROL Agent will then be refreshed.

Forcing Selected Data Collectors

This option is only available from a PATROL Developer Console.

  1. Right-click the server instance and select Refresh Process Cache to refresh the PATROL Agent process cache
  2. Force a data collector to execute immediately as follows:

    With the PATROL Console for MS Windows

    • Right-click on the server instance and choose Parameters without Icons…
    • Select the required data collector
    • Click Update.

    With the PATROL Console for Unix

    • Right-click on the server instance and choose Customize > Parameters…
    • Select the required data collector
    • Click Options > Update.

    With the PATROL Central Operator Console

    • Right-click on the server instance and choose Properties
    • Click on the Parameter List tab
    • Select the required data collector
    • Click Update.

Forcing Full Data Collection for Jobs

By default, the NBUJobCollector only searches for new jobs started since the last collection cycle. However, it can be forced to search for all jobs within the monitored time period during the next collection cycle.

To force full data collection for jobs, right-click the Jobs instance and select Force Full Collection.

Note: If the Jobs container instance is not instantiated, this menu command cannot be accessed. The PATROL Agent needs to be restarted to force a full data collection for jobs.

Reloading Commands

All new commands are reloaded automatically but some situations may require a manual command reload. To do so, in the Console, right-click the server instance > KM Commands > Reload Commands…

Keywords:
storage netbackup km patrol