Loading...

Auxiliary Copy Alerts

The following alerts are available for auxiliary copy operations.

Alerts

Description

Alert every n attempt (Phase failures) Notifies that the specified number of attempts were made to resume the auxiliary copy operation after a phase failure.
Alert every n attempt (Network failures) Notifies that the specified number of attempts were made to resume the auxiliary copy operation after a network failure.
Delayed by n Hrs This alert notifies that an auxiliary copy operation was in a waiting state for the hours specified during the configuration.
Auxiliary Copy fallen behind alert

 

Notifies when the system predicts that the auxiliary copy operation will exceed the number of hours specified for the operation to complete. This prediction is calculated when one of the following criteria has been met for the selected storage policy copy.
  • Data that is ready to be copied is over the quantity specified in TB.
  • Jobs that are over the number of specified days old and have not yet been fully copied.
  • More than 48 hours is required to copy all data, based on the average throughput of previously run auxiliary copy jobs. Adjust this value with an estimated completion time so that the alert is triggered.

If an alert is received, immediate attention should be given to any abnormal condition. Immediate action will prevent the auxiliary copy from falling behind the source copy, in terms of the amount of data to be copied.

For more information, see Resolving the Auxiliary Copy Fallen Behind Alert Issues.

The alert indicates the criteria that was met to trigger the alert, with one alert reason for each criteria, respectively:

  • to be copied data exceeded
  • old jobs not copied
  • need more time to copy data

Assuming that the Auxiliary copy had no issues and is expected to run for that duration, use the throughput and application values from the Auxiliary Copy Job Summary Report to set the value for the need more time to copy data criteria. For example, application data size is 1000 GB and throughput is 500 GB/hr, set the time to 2 hours.

Example:

The example explains how the throughput is calculated internally and can be followed to set the hours value for the need more time to copy data criteria:

Auxiliary Copy Job1 copied 4 TB in 2 hours.

Auxiliary Copy Job2 copied 2 TB in 1 hour.

Average Throughput = (Total data copied by all jobs) / (Total time taken by all previous Auxiliary Copy jobs)

In the example,

  • Total data copied = 6 TB
  • Total time taken = 3 hrs

Average throughput is 6/3 = 2 TB/hr

To copy 4 TB, the calculation is 4/2. Round up to the next hour and set the alert to 2 hours.

If the amount of data to copy increases to 27 TB and throughput is 2TB/hr, set the alert to 14 hours.

If throughput increases, for example 10 TB can be copied in 1 hr, then set the alert to 3 hrs, if data to be copied is 27TB.

New subclient associations to the storage policy will be prevented if the data to be copied is more than three times the specified value in the Auxiliary Copy Fallen Behind criteria, or if any of the other specified criteria is exceeded by more than three times.

Note: Fallen behind alert for Silo copy and IntelliSnap backup copy is not supported.

You can configure the interval between alerts for this criteria. For more information, see Interval (Hours) between Auxiliary Copy Fallen Behind Alerts.

Job Activity This alert notifies that an auxiliary copy operation was killed, resumed, or suspended by a user.
Job Failed This alert notifies that an auxiliary copy operation failed to complete, failed to start, or was stopped by the system.
Job Skipped This alert notifies that a scheduled auxiliary copy operation ran late, was skipped by a user, or skipped due to a holiday.
Job Succeeded This alert notifies that an auxiliary copy operation completed successfully.
Job Succeeded with Errors This alert notifies that an auxiliary copy operation completed with errors.

Related Topics

Resolving the Auxiliary Copy Fallen Behind Alert Issues