Status > Consecutive Failures
This report is the second of three using the advanced success or failure calculation logic around the notion of first, all and last job. The main use case is the calculation of two or more consecutive failures based around Last Job Success/Failure. It applies intricate logic to pick off the last failed job and in turn to determine that the last job failures are indeed consecutive. This report can be best verified through the Client Risk Analysis report. In this report, if three consecutive failures with 24 hour windows were chosen, the client or the policy combination should also appear on the risk report as not having a successful backup in 72 or more hours.
Jobs that fail consecutively appear in the Consecutive Failures report. The period for which they fail consecutively is configurable.
Figure: Consecutive Failures Report shows a sample view of Consecutive Failures Report.
The following columns are displayed in the report:
Node Name | Value in the Node Name column depends on the Report On parameter that you select. The default value of Report On parameter is Master Server. So the value in Node Name column by default shows the master server name. When you select a view from the Filters section while editing the report, the Report On parameter drop-down list also shows the view levels. Based on the levels that you select from the Report On drop-down list, value in the Node Name column changes. For example, if there is a view like Location (View name) - US -- Client1 -- Client2 -- Client3 - India -- Client4 -- Client5 -- Client6 The following selections are possible:
|
Client Name | Name of the client |
Policy Name | Policies associated with the client and node name |
Schedule Name | Schedules associated with the client |
Job ID | Job IDs associated with the policy and schedule that fail consecutively. |
Start Time | Date and Time when the job started |
End Time | Date and time when the job ended. |
Status Code | Status code for the job ID. You can also filter the report to see details of only a particular status code by using the Job > Status Code filter and selecting the specific status codes. Note that jobs with status code 0 (successful) may also appear in the report. This usually happens in case of multi-streaming jobs. Job IDs with status code 0 appear because if any of the sub-jobs of a multi-streaming job fail, it is considered a complete failure. Generally the Start Time for the multistreaming jobs would be very close. |
The following are the details that are associated with the Consecutive Failures report:
Report Name | Consecutive Failures |
Report Category | Status and Success Rate |
Where to Locate | Report > Report Templates > Backup > Status and Success Rate > Status > Consecutive Failures report. |
Report Purpose | Provides tabular view showing clients that had consecutive job failures. |
Supported products | NetBackup, NetBackup Master Appliance |
Applicable View | Master Server, Client |
Report Display | Tabular |
Drill down report | None |
Can be scheduled | Yes |
Supported formats | PDF, CSV, HTML, XML, TSV |
Mapping with VBR report | All Reports > Standard Report > Backup > Status > Consecutive Failures |
You can edit the Consecutive Failures report to show or hide the columns that you are interested in. All the columns are shown by default. You can also filter the report to view reports of specific master servers. The following table shows the filters for Consecutive Failures report and how you can use these filters to view specific data in the report.
Filter | Column | Description |
|---|---|---|
View | Select a view to show data for the selected view in the report. By default All My Views is selected. | |
Master Server | Master Server | Select one or more master servers to view data for the selected master servers in the report. All master servers that are added to the OpsCenter console are shown in the Value drop-down list . |
Policy | Policy Name | Select one or more policy names to view data for the selected policies. |
Job | Job Types | Select one or more job types as Archive, Backup, or Restore to view data for the selected job types. |
Status Code | Select one or more status codes to view data for the selected status codes. | |
Success Rate | Aggregation Level | Select different parameters for criteria definition about success rate of the jobs. Select All Jobs Success Rate, First job Success Rate, Last Job Success Rate. Select Aggregation Level to consider the kind of jobs for the specified time frame. For example, if you select First Job Success Rate then the report shows only the first job for the combination of master server, client, policy, and schedule. |
Metric Type | Select to calculate the success rate based as jobs. | |
Full Days | Select to specify the list of days to be considered for Full backups. | |
Full Window Parameter | Select to specify the start time for the full backup window. | |
Count Partial Successful job as Successful | Select to count partially successful jobs as successful. | |
Full for Duration of (In Hours) | Select (In Hours) to calculate the end time for the incremental backup window. Backup window end time is equal to the duration from the start time of the backup window. | |
Consecutive Failures | Select how many consecutive failures should be included in the report. | |
Increment Window Parameter | Select to specify the start time for the incremental backup window. | |
Schedule/Level Type | Select the schedule of jobs is Full or Increment or All. | |
Increment for Duration of (In Hours) | Select (In Hours) to calculate the end time for the incremental backup window. Backup window end time is equal to the duration from the start time of the backup window. | |
Increment Days | Select to specify the list of days to be considered for Incremental backups. |
Example of filter usage: You may run the report for specific policy names to view details only for that specific policy.