-
Home
- PATROL
Operate EMC NetWorker KM
This section describes the most common operations that can be performed with EMC NetWorker 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 Log Alerts
When an error is detected in a monitored log file, it will either appear in NSRLogAlarmText or NSRLogWarningText and will respectively trigger an Alarm or a Warning on NSRLogAlarmCount or NSRLogWarningCount.
To acknowledge log alerts:
-
In the Console, right-click the Log instance > KM Commands > Acknowledgement
-
Select:
- Warnings… to view, select, and individually acknowledge errors in the NSRLogWarningText parameter
- Alarms… to view, select, and individually acknowledge errors in the NSRLogAlarmText parameter
- All… to acknowledge all alerts (Warnings and Alarms) at once without viewing.
Manually Acknowledging Save Group Alerts
For a particular save group instance, if the NSRSaveGrpStatus 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 KM command Acknowledgement > Alert from the relevant save group instance.
To acknowledge save groups alerts:
-
In the Console, right-click the Save Groups instance > KM Commands > Acknowledgement
-
Select:
- Warnings… to view and acknowledge alerts for all save groups with a status of Warning
- Alarms… to view and acknowledge alerts for all save groups with a status of Alarm
- All… to view and acknowledge all save group alerts at once (Warnings and Alarms).
Generating Reports
The following reports are available in EMC NetWorker KM for PATROL:
- Daemons > Reports > Daemon List…: lists all running EMC NetWorker daemons
- Databases > Reports > Database Backup Information…: reports information about the previous index database backups
- Logs > Reports > Messages List…: reports all messages logged in the past 24 hours
- Pending Requests > Reports > Pending Requests…: reports a list of all pending requests
- Jukebox instance > Reports > Jukebox Contents…: reports the contents of the selected jukebox instance
- Volume Pool instance > Reports > Volumes List…: reports information on all volumes in the selected volume pool instance.
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 instance 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 EMC NetWorker 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.
-
Right-click the Server instance and select Refresh Process Cache to refresh the PATROL Agent process cache
-
Force a data collector to execute immediately as follows:
With the PATROL Console for Windows
- Right-click the Server instance and choose Parameters without Icons…
- Select the required data collector
- Click Update.
With the PATROL Console for UNIX
- Right-click the Server instance and choose Customize > Parameters…
- Select the required data collector
- Click Options > Update.
With the PATROL Central Operator Console
- Right-click the Server instance and choose Properties
- Click the Parameter List tab
- Select the required data collector
- Click Update.
Forcing Full Data Collection for Save Groups
By default, the NSRSaveGroupCollector only searches for new save groups started since the last collection cycle. However, it can be forced to search for all save groups within the monitored time period during the next collection cycle.
To force full data collection for save groups, right-click the Save Groups instance and select Force Full Collection….
Forcing the Classic Mode
EMC NetWorker KM for PATROL can either be configured from a BMC PATROL Console (Classic Mode) or BMC Helix/TrueSight Operations Management. When the KM is installed on a PATROL Agent, which is managed by Central Monitoring Administration (CMA), all the KM configuration menus are disabled in the PATROL Console. To configure EMC NetWorker KM from a PATROL Console, you need to force the KM to run in Classic Mode.
This will disconnect EMC NetWorker KM from receiving configuration from Central Monitoring Administration. Any monitoring settings that was configured in CMA and used by the PATROL Agent will be removed and replaced by the configuration made from the PATROL Console. However, this will not delete the policies created in CMA from the configuration.
Warning: Any configuration for EMC NetWorker KM received from Central Monitoring Administration will be ignored.
To force the KM to operate in Classic mode:
-
In the PATROL Console, right-click the EMC NetWorker icon > KM commands > Configuration > Force Classic Configuration Mode…
-
Check the Force the KM to run in Classic mode box and click OK.
EMC NetWorker KM for PATROL starts running in Classic Mode, enabling you to use the KM Configuration menus.
To configure the KM in Helix/TrueSight OM, repeat the above procedure and uncheck Force the KM to run in Classic mode. All configurations made through the PATROL Console will then be ignored.
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…