After configuring a Scheduled Report, the user clicks the "Save and Test" button. The server indicates that the report was sent to the server for processing. However, the report is not published.
The following message is logged in the DPA server.log file on the DPA Application server:
This is a known bug/defect in Data Protection Advisor 6.0. This is caused when a scheduled reprot is configured with a scope of children objects (i.e. a specific selection of clients from a backup server).
Resolution
To work around this issue, change the scope to a higher level object. For example, if the currently selected scope is a list of clients change the selection to the backup server that these clients are configured on. This is resolved in DPA 6.0.1 and later.
A Hot Fix may be available for this issue on some platforms and some DPA versions. Please contact EMC Technical Support for more details.
Note: Not all issues are available for a Hot Fix for all versions and platforms. These will be evaluated by L2 SME Engineers and DPA Engineering. If a Hot Fix is not available, upgrade will be required."
That's a fairly basic functionality snafu. I don't want to report on the whole Avamar grid - I want to report on a sub-set of the clients for a specific use case. I have over 1000 clients on this grid.
I had a quick look into this and from what I can tell it seems that there is a patch for DPA 6.0 that will resolve this issue. To get the patch please log a support ticket and reference the ESG article.
Dusted
9 Posts
0
June 10th, 2013 03:00
Found the answer myself in article : esg136230
"Symptoms
After configuring a Scheduled Report, the user clicks the "Save and Test" button. The server indicates that the report was sent to the server for processing. However, the report is not published.
The following message is logged in the DPA server.log file on the DPA Application server:
[Date] [TIME] ERROR [com.emc.dpa.services.reporter.schedule.RunScheduledReportServiceBean] ( :2470998a-ac96-4536-a094-a32fb18b92a1:Sched) Unexpected error occurred when running scheduled report: java.lang.NullPointerException: javax.ejb.EJBTransactionRolledbackException: java.lang.NullPointerException
Cause
This is a known bug/defect in Data Protection Advisor 6.0. This is caused when a scheduled reprot is configured with a scope of children objects (i.e. a specific selection of clients from a backup server).
Resolution
To work around this issue, change the scope to a higher level object. For example, if the currently selected scope is a list of clients change the selection to the backup server that these clients are configured on. This is resolved in DPA 6.0.1 and later.
A Hot Fix may be available for this issue on some platforms and some DPA versions. Please contact EMC Technical Support for more details.
Note: Not all issues are available for a Hot Fix for all versions and platforms. These will be evaluated by L2 SME Engineers and DPA Engineering. If a Hot Fix is not available, upgrade will be required."
That's a fairly basic functionality snafu. I don't want to report on the whole Avamar grid - I want to report on a sub-set of the clients for a specific use case. I have over 1000 clients on this grid.
Pah. When is the next version released?
eagarg1
66 Posts
0
June 10th, 2013 13:00
I had a quick look into this and from what I can tell it seems that there is a patch for DPA 6.0 that will resolve this issue. To get the patch please log a support ticket and reference the ESG article.
Regards,
Gareth