Enterprise Vault™ Troubleshooting FSA Reporting

To troubleshoot FSA Reporting with DTrace

1. On the FSA Agent computer, enable DTrace for the FSAReportingService process and start logging the results. Specify a monitoring level of at least medium. For example, enter the following two commands at the DTrace command prompt:

   set FSAReportingService verbose 
   log c:\temp\dtracelog.log

2. Check whether there are problems with obtaining the FSA configuration parameters. Do as follows:

   • For Windows file servers, restart the Enterprise Vault File Collector Service on the file server. For non-Windows file servers with an FSA Reporting proxy server that is not an Enterprise Vault server, restart the Enterprise Vault File Collector Service on the proxy server. For non-Windows file servers with an Enterprise Vault server as the FSA Reporting proxy server, restart the Admin Service on the Enterprise Vault server.

   • Check the results of the fetch operation. To do this, look in the DTrace log for entries containing the following string:

     {Client.GetConfigurationInformation}

     The detail level of these entries is Medium.

   • Check that the FSA Agent computer can access the computer that runs the FSA Reporting web service.

   • Check that both a forward DNS lookup and a reverse DNS lookup succeed for the file server. The following DTrace entry indicates that a reverse DNS lookup is failing:

     FSAReportingUtil::GetFullyQualifiedDomainName, server name passed to this function = (NetBIOS name instead of FQDN) |

   • Open the Event Viewer and look in the Enterprise Vault event log for information event 24576 with the following description:

     Parsing of configuration XML is successful; Schedules 
     service started.

     If you cannot see this event, open SQL Server Enterprise Manager and go to the EnterpriseVaultFSAReporting database. Examine the FileServerConfiguration table as follows:

     • Check whether the table contains a row for each file server that is configured for FSA Reporting.

     • Check whether the DomainName column in each row contains the fully qualified domain name of the domain where the file server is located. If it does not, edit the entry to specify the fully qualified domain name.

     • If any rows are missing, the most likely reason is that you are using versions of FSA Agent and Enterprise Vault Reporting that are incompatible with FSA Reporting.

       See the following technical note on the Veritas Support website: https://www.veritas.com/docs/100030221.

     If you are using compatible versions of FSA Agent and Enterprise Vault Reporting then another issue must have caused the database problem.

3. Verify that FSA Reporting scans are running successfully. Look for the relevant entries in the DTrace log, depending on how the scan was initiated:

   • If a user initiated the scan using the Run FSA Reporting Scan option in the Administration Console, look for entries containing the following:

     CServer::ScanNow

   • For a scheduled scan, look for entries containing the following:

     Call back timerproc

   Then look for an entry containing the following, which indicates that the scan is being prepared:

   CAgentParams::GetObject

   The detail level of these entries is Low.

4. Verify that a scan has started, by looking for the entry:

   CScan::ScanMain

   The detail level of this entry is Low.

5. Check whether the list of archive points is being obtained correctly. The FSA Agent requires the list of archive points present under the volume that is currently being scanned. To verify that this archive point information is obtained properly, look for entries containing the following:

   • ArchivePointThread

   • {Client.GetArchivePointDetails}

   The detail level of this entry is Medium.

   Note that there will be several entries that contain these strings. The entries may not necessarily be found together, as there are other operations occurring simultaneously. If these entries indicate any failure, do as follows:

   • Check that the FSA Agent computer can access the computer that runs the FSA Reporting web service.

   • Then run GetArchivePointDetails from the ReportingServer web page. Specify the following parameters:

     fileServerName	The fully qualified domain name of the file server, for example blackbird.demo.local. For non-Windows file servers, specify the file server name, not the FSA Agent computer name.
     volumeName	The name of the volume for which to obtain information.

   A web browser window should open and list all the archive points. If no archive points are listed, run the same function but use the IP address of the file server.

6. Check whether the archive information is being obtained correctly. Look for entries containing the following:

   • ArchiveThread

   • {Client.GetArchiveInformationByArchivePoint}

   The detail level of these entries is Medium.

   If these entries indicate any failure, do as follows:

   • Check that the FSA Agent computer can access the computer that runs the FSA Reporting web service.

   • Then run GetArchiveInformationByArchivePoint from the ReportingServer web page. Enterprise Vault invokes this function for every archive point in a target volume. You must specify the following:

     fileServerName	The fully qualified domain name of the file server, for example fileserver.demo.local. For non-Windows file servers, specify the file server name, not the FSA Agent computer name.
     volumeName	The name of the volume for which to obtain information.
     archivePointVEID	The id of the archive point for which to obtain information. This is specified by the GetArchivePointDetails method you used earlier.
     knownFileTypes	Do not enter a value for this parameter.

     Verify that archive data is shown for the specified archive point and file types. If no archive data is listed, run the same function but use the IP address of the file server.

7. Check the progress of the scanning of live files. To do this, check all the entries reported at the Medium detail level containing the string:

   CRDScan

8. Check that the FSAReportingService is sending scanned data to the FSA Reporting database. Enterprise Vault sends the scanned data and metadata per archive point, using the functions SendAndUpdateDataForArchivePoint and SendAndUpdateMetaData. For example, if a volume has two archive points, Enterprise Vault calls both functions three times: once for each archive point, to send the data and metadata for the archive point, and a third time to send the data and metadata for the volume.

   • To verify the scanned data transfers, look for entries containing the string

     {Client.SendAndUpdateDataforArchivePoint}

   • To verify the metadata transfers, look for entries containing the string:

     {Client.SendAndUpdateMetaData}

     The detail of these entries is Medium.