Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

Cannot run report scan on Non-windows file server (NetApp)

Created: 26 Oct 2012 | 5 comments
Pedro Rocha's picture

Hello,

I've been trying to configure FSA Reports on a NetApp filer, but not being successfull. I am running EV 10 for FS and a FAS3270 filer on Data Ontap 8.0.

The proxy server for the FSA reporting on the NetApp is the EV server itself. I am able to run a report scan on a local volume, but the same is not true for the NetApp filer.

It is enabled and seems to be well configured, but whenever a hit the "Run FSA Reporting Scan" under the filer menu on EV Admin Console, neither the scan start time nor end time gets updated.

The reporting scan status collumn for the NetApp filer is "Reporting enabled".

I tried to see whats happening using DTRACE in verbose mode for the FSAReportingService. And all it shows me is the following lines:

319 16:54:24.969 [3880] (FSAReportingService) <12464> EV:L CFSAReporting::get_Servers method called |
320 16:54:24.969 [3880] (FSAReportingService) <12464> EV:L Leaving CFSAReporting::get_Servers
321 16:54:24.969 [3880] (FSAReportingService) <12464> EV:L CServers::get__NewEnum method called
322 16:54:26.513 [3880] (FSAReportingService) <12464> EV:L CServer::get_Name method called
327 16:54:26.700 [3880] (FSAReportingService) <12464> EV:L CFSAReporting::get_Servers method called |
328 16:54:26.700 [3880] (FSAReportingService) <12464> EV:L Leaving CFSAReporting::get_Servers
329 16:54:26.700 [3880] (FSAReportingService) <12464> EV:L CServers::get__NewEnum method called
330 16:54:28.245 [3880] (FSAReportingService) <12464> EV:L CServer::get_Name method called
337 16:54:29.945 [3880] (FSAReportingService) <12464> EV:L CFSAReporting::get_Version method called
338 16:54:29.945 [3880] (FSAReportingService) <12464> EV:L CFSAReporting::get_Version method leaving
343 16:54:32.348 [3880] (FSAReportingService) <12464> EV:L CFSAReporting::get_Servers method called |
344 16:54:32.348 [3880] (FSAReportingService) <12464> EV:L Leaving CFSAReporting::get_Servers
345 16:54:32.348 [3880] (FSAReportingService) <12464> EV:L CServers::get__NewEnum method called
348 16:54:33.892 [3880] (FSAReportingService) <12464> EV:L CServer::get_Name method called

Do anyone knows what could be possibly happening? What is wrong with my config?

Kind regards,

Pedro Rocha.

Comments 5 CommentsJump to latest comment

Jeff Shotton's picture

Hi Pedro,

 

Maybe the following will help you figure out the issue:

http://www.symantec.com/docs/TECH51475

From the troubleshooting document the following appears to fit your issue (p12)

 

FSA Reporting scans fail to start, no change in scan
status

Problem: FSA Reporting scans fail to start for a file server. The Administration
Console shows no change in scan status, and displays no error message.
A DTrace of the FSAReportingService includes the following entry:
FSAReportingUtil::GetFullyQualifiedDomainName, server name passed to
this function = (NetBIOS name instead of FQDN) |
Cause: Enterprise Vault requires that both a forward DNS lookup and a reverse
DNS lookup of the file server is successful.
Resolution: Make sure that both a forward DNS lookup and a reverse DNS lookup
succeed for the file server.

Regards,

Jeff

Jeff Shotton

Principal Consultant

Adept-tec Ltd

Website: here

Pedro Rocha's picture

Hello Jeff, thank you for the information. I'll try that and let you know.

But, even if my DTrace does not show the message on the troubleshooting guide, do you think this applies?

Regards,

Pedro Rocha

Jeff Shotton's picture

You *may* have missed it?! Start another dtrace of that process with all the services stopped, start all the services, do a RUN NOW and have another look.

You *should* at least see

"FSAReportingUtil::GetFullyQualifiedDomainName, server name passed to this function ="

Regards,

Jeff

Jeff Shotton

Principal Consultant

Adept-tec Ltd

Website: here

Pedro Rocha's picture

Hello Jeff,

No luck in here... the DTRACE only shows the logs I've mentioned before. Nothing about DNS.

Any other ideas?

Regards,

Pedro

 

Jeff Shotton's picture

Ideas....well maybe try another server to run the scan from?

 

Any chance of posting a dtrace with a deployment scanner?

Stop all the Enterprise Vault services

Run dtrace from the command line.

set dtrace on the fsareportingservice and log to a file

start all the enterprise vault services

do a 'run now' on the reporting scan and post the log.

Regards,

Jeff

Jeff Shotton

Principal Consultant

Adept-tec Ltd

Website: here