Resetting security notifications for clients

When you reset security notifications for a client, you delete the historical data that was used for baseline comparisons with current backup sessions. Reset notifications for a client if backup characteristics for the client no longer resemble the recent historical data, or to delete notifications that you no longer have to track.

About this task

The Operations Center determines whether to log a security notification for a client backup session by comparing the workload size and data deduplication rate in the session to recent historical data for the client. The baselines that are used for comparison are rolling averages that are calculated from up to five of the most recent backup sessions. A significant change in the backup characteristics triggers a security notification. However, atypical workload sizes and data deduplication rates that trigger a security notification might have benign causes. Significant changes to the amount of data that is being backed up for a client, or in the amount of client data that is unsuited for data deduplication, might result in false positives.

If you do not reset security notifications for the client, the Operations Center might issue notifications for the same false positives after subsequent backup sessions. It might take up to five backup sessions before the rolling average represents normal backup characteristics again.

Procedure

To reset security notifications for one or more clients, complete the following steps:

  1. To open the Security Notifications page, click Overviews > Security.
  2. On the Security Notifications page, select one or more client security notifications.
  3. Click Reset.

Results

The rolling averages that were used for baseline comparisons and the client security notifications are deleted. The Operations Center does not analyze the next client backup session, but records new workload and deduplication rate baselines. After the second client backup session, the observed workload size and deduplication rate are compared to the baselines for possible security incidents and are included in the new baseline averages. After enough backup sessions, the rolling averages are again calculated from the five most recent backup sessions.