This section provides an overview of reporting available in the Rapid Recovery Core Console.
Topics include:
You can generate these reports from the Rapid Recovery Core Console. Other reports are also expected to be available from the QorePortal.
The reports available from the Core Console are described in the following table.
Report type | Description |
---|---|
Job report |
Provides a basic report on the status of successful jobs, failed jobs, and jobs with errors. Failed jobs can be further viewed in a Failure report.
For more information on this report type, see Understanding the Job report. |
Job summary report |
Provides a more detailed report on the status of successful jobs, failed jobs, and jobs with errors, showing a separate line in the report for each job type, allowing better diagnosis of potential issues.
For more information on this report type, see Understanding the Job Summary report. |
Failure report |
Provides information on failed Core jobs for the specified criteria. This report can include protected machine details or exclude them. Like the Job report, this report can also be run only from a protected machine selected in the Core. The resulting report displays detail about failed jobs only for the selected protected machine. For more information on this report type, see Understanding the Failure report. |
Summary report |
Provides summary information. By default, this set of information includes jobs for all machines—every protected machine, replicated machine and recovery point-only machine in the specified Cores. In the report parameters, you can customize the report. Use the filters to select or exclude some machines. You can also select or exclude jobs that are machine independent, in which case the report shows status for Core jobs only. This report is not available from the perspective of any single protected machine. The categories of information in this report include Core, license, and repository. The information is displayed in list, chart, and table form For more information on this report type, see Understanding the Summary report. |
Repository report |
This report type provides you with a report of all repositories on the selected Core or Cores. You can also select any single repository available to the Core. This report is only from the perspective of the Core. For more information on this report type, see Understanding the Repository report. |
Classic summary report |
This report provides a summary view of job statistics success, repository summaries by GB, snapshots success, repository usage trends, and a summary of protected machines on your Core. Report parameters include date range and the relevant Core. For more information on this report type, see Understanding the Classic Summary report. |
Scheduled report |
You can also schedule any of these reports from the Core Console. Scheduling a report causes the report you specify to generate repeatedly on the schedule you define. Optionally, you can establish email notifications each time a report is generated. For more information about scheduling, modifying, pausing, or deleting reports, see Managing scheduled reports from the Core Console. |
Based on the report type and the parameters that you select, you can generate a report on one or more Rapid Recovery Cores or for one or more protected machines.
You can generate reports on demand from the Core Console. The following rules apply:
The method for generating on-demand reports is similar, whether the report is generated from the focus of the Core, or whether it is generated from the perspective of a protected machine. However, navigation differs slightly.
As described in the topic About Rapid Recovery reports, you can generate the full range of available reports from the Core Console.
Complete the steps in the following procedure to generate a report from the perspective of the Rapid Recovery Core.
The Job Report page appears. To the right of the report name in the page title, a downward-facing arrow appears, from which you could select another report type.
If you want to generate a Job report, proceed to step 6 to begin specifying your report criteria.
If you do not choose a date range, the default option (Last 31 days) is used. You can choose from the options in the following table.
Option | Description |
---|---|
Last 24 hours | Reports activity for the last day, relative to the time you generate the report. |
Last 7 days | Reports activity for the last week, relative to the time you generate the report. |
Last 31 days | Reports activity for the last 31 days, relative to the time you generate the report. |
Last 90 days | Reports activity for the last 90 days, relative to the time you generate the report. |
Last 365 days | Reports activity for the last year, relative to the time you generate the report. |
All Time | This time period spans the lifetime of the Core. |
Custom | This time period requires you to further specify start and end dates. |
Month to date | Reports activity from the first day of the current calendar month to the date you generate the report. |
Year to date | Reports activity from the first day of the current calendar year to the date you generate the report. |
|
NOTE: In all cases, no report data is available before the Core software was deployed, or from before machines were protected on the Core. |
The default selection includes all available Cores.
By default, this set of information includes jobs for all machines—every protected machine, replicated machine and recovery point-only machine in the specified Cores. In the report parameters, you can customize the report. Use the filters to select or exclude some machines. You can also select or exclude jobs that are machine independent, in which case the report shows status for Core jobs only.
You can choose from:
Option | Description | ||
---|---|---|---|
Select all |
This option selects all protected machines protected on this Core.
| ||
Machine independent |
Select this option to generate a report which includes jobs from a Core perspective. Job types such as creating or deleting a repository, or creating a boot CD, are not associated with a specific machine. If deploying the Agent software to a machine that is not yet protected, this job type is also considered machine independent. These jobs do not list a protected machine in the Protected Machine column of the resulting report. In contrast, if you deploy the Agent software to a machine that is already protected in the Core, the protected machine name is included in the report. It is not considered machine independent. | ||
Protected machines |
This option lists the machines protected on this Core. You can select them all, or a subset of the protected machines. | ||
Recovery points only |
This option lists machines that were once protected, but still have recovery points saved in the repository. | ||
[Source cores] |
If your Core is a target Core, and replicates recovery points for any machines protected on a source Core, then the name of that source Core appears (in all uppercase letters). This option lists all machines protected on that source Core. You can select all machines replicated in this target Core, or you can select a subset of them. | ||
[Custom groups] |
If you have any custom groups created on this Core, the name of each custom group appears as an option. Each object in that custom group appears. You can select all objects in the group, or a subset of them. |
By default, this set of information includes all jobs for the selected protected machines. In the report parameters, you can customize the report. Use the filters to select or exclude every job in the Main Jobs category, and every job in the Other Jobs category. Or you can expand each of these categories when defining job parameters, and select only the job types from either category that you want to appear in the report. Click the checkbox for any job type to select or clear that type. You can select some or all jobs from either category.
You can choose from the following other job types:
The default selection includes all available repositories.
If the report criteria you selected is not found, the report still generates, but the report contains an empty row. For example, if there are no errors, the contents of the Error column are null in the report.
© ALL RIGHTS RESERVED. Conditions d’utilisation Confidentialité Cookie Preference Center