Topics | Troubleshoot | How Do I | Related Topics
Data Protection Operations are Missing from Reports or Summaries
Some Data Protection Types are Missing from Reports or Summaries
Some Data Protection Activities are not Shown on my Activities Report
Some Data Protection Activities are not Shown on my Window Utilization Report
SRM Subclient Information is Missing from Reports or Summaries
File system Information is Missing from Reports or Summaries
Information is Missing from Oracle Reports or Summaries
Some Reports are Dimmed in the CommNet Browser
Reports or Summaries do not Display Subclient Content Beyond Five Lines
Some iDataAgents are Missing from the CommCell Growth Report
Reports saved on UNC paths fail with error
The data protection history or CommCell Events may have been pruned from the CommNet Server
The retention of data protection history and CommCell Events is based on the settings for pruning in the CommNet Properties dialog box. Once data has been pruned from the CommNet Server, it is no longer available for reports.
Additionally, since the software receives historical data from the CommCell when first installed, only the history that is stored on the CommCell at that time will be available for reports. For example, if your pruning schedule is set for 12 months, but the CommCell only has 2 months of historical data available when you first install the software, you will only be able to run reports for the previous 2 months. As time goes on, while the CommCell will continue to prune according to its schedule, historical job and event data will continue to accumulate until the time limit for CommNet Server pruning is reached.
Synthetic full backups are not considered when checking coverage and are not considered in SLA calculations
Because synthetic full backups are produced by combining previous data protection operations, only the original data protection operations are counted as coverage for the days when they actually ran. For example, if an incremental backup was executed on Monday, May 1st, and a synthetic full backup was executed on Tuesday, May 2nd; a Data Protection Coverage Report run on Wednesday, May 3rd, which is checking coverage for the past three days, would only show coverage for Monday, May 1st because that was the only day that a data protection operation was executed. The synthetic full backup that was executed on Tuesday would not be counted as coverage.
| When users run a Data Protection Coverage Report, the report will include all data protection operations, including synthetic full backups. |
The data protection activity may be more recent than the last update
These issues are addressed in Some of the Cells do not Get Updated at the Specified Hour.
The data protection history may have been pruned from the CommNet Server
Data Protection Operations are Missing from Reports or Summaries
The CommNet Browser may have lost its connection with the CommNet Server
What do I do When the CommNet Browser Loses Connection with the Server
Only data protection jobs that begin inside the Data Protection Window are reported
Since the purpose of this report is to check how well your Data Protection Window is being utilized, data protection jobs that begin outside (either before or after) the Data Protection Window will not be reported. You will notice that jobs that begin inside, but complete outside, the Data Protection Window are reported, and shown in a different color on the charts.
To see more jobs on this report, you can lengthen the Data Protection Window. See Configure the Data Protection Window.
The data protection history may have been pruned from the CommNet Server
Data Protection Operations are Missing from Reports or Summaries
The CommNet Browser may have lost its connection with the CommNet Server
What do I do When the CommNet Browser Loses Connection with the Server
The SRM Agent for File System may not be installed
The SRM Agent for Unix File System or the SRM Agent for Windows File System must be installed before reports and summaries will display complete file system information, including file system logical volumes. Note that in the case of Oracle, even though the SRM Agent for Oracle is not installed on the Oracle server, the SRM File System Agent must be installed on the Oracle server.
The SRM Agent for File System may not be installed
The SRM Agent for Unix File System or the SRM Agent for Windows File System must be installed before reports and summaries will display complete file system information, including file system logical volumes. Note that in the case of Oracle, even though the SRM Agent for Oracle is not installed on the Oracle server, the SRM File System Agent must be installed on the Oracle server.
The databases or log file may reside on a raw partition
File system and space information is not reported for raw partitions or volumes.
You do not have an Advanced Reporting license, or it has expired
Check to see if the Advanced Reporting license has expired. If it has, or you wish to obtain an Advanced Reporting license, contact your software provider.
CommNet reports and summaries are limited to five lines of subclient content. Contents greater than five lines will not display.
iDataAgents must be associated with a subclient to be included in a CommCell Growth Report
When running a CommCell Growth Report for data protection jobs, only completed jobs, whether they failed or were successful, are counted in the report. Pending, running or suspended data protection jobs are not counted. Additionally, when running a report for iDataAgents, if there are no subclients associated with an iDataAgent, the report will not recognize it, and therefore, not count it. If there are subclients associated with the iDataAgent, the report will count it.
WebClient service must be up and running on CommNet Server
For saving a report on UNC paths, it is required that WebClient service be up and running on the CommNet Server.
However for Windows 2008 computer you must have Desktop Experience installed and then run the WebClient service on the CommNet Server.