This can occur if reverse name lookup is not configured for the file server's hostname in the DNS environment
This can be confirmed by carrying out a nslookup command against the targeted FSA Servers IP Address:

1. Open command prompt on file server.
2. Type nslookup   (e.g. nslookup 10.0.0.1)

​nslookup should return the Fully Qualified Domain Name of the server similar to the below:

C:\Users\Administrator>nslookup 10.0.0.1
Server: dnsserver.domain.local
Address:  10.0.0.2

Name:    fileserver.domain.local
Address:  10.0.0.1

If there is no PTR Record (Reverse Lookup Record) for the FSA server in the DNS domain then you may see an error similar to the below:

C:\Users\Administrator>nslookup 10.0.0.1
DNS request timed out.
    timeout was 2 seconds.
Server:  UnKnown
Address:  ::1

*** UnKnown can't find 10.0.0.1: Non-existent domain

To fix this issue configure a PTR record in the DNS environment, the exact steps on how to do this depends on the Operating Systems involved and your network setup, therefore we recommend you consult your vendor for instructions.

Once the PTR record is added carry out an NSLookup operation against the IP Address again, this time it should succeed, once confirmed an NSlookup works as expected the FSA Reporting Scan should also run as expected.

More details on how to use NSLookup can be found at ,
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/nslookup

A Reporting Scan carried out against a File System Archiving (FSA) file server appears unresponsive when run and the task does not record a start time in the Vault Admin Console. A Dtrace of the FSAReportingService process on the affected file server shows the following:

(FSAReportingService) <16028> EV:H CheckIfClusteredServer Got Virtual Server Count :0 Name:Fileserver, IP:10.0.0.1
(FSAReportingService) <16028> EV:M IPV6 - Entered Function FSAReportingUtil::GetFullyQualifiedDomainName, server name passed to this function = Fileserver|
(FSAReportingService) <16028> EV:M FSAReportingUtil::GetFullyQualifiedDomainName - IPV6: FQDN found [FILESERVER]|
(FSAReportingService) <16028> EV:M IPV6 - Leaving Function FSAReportingUtil::GetFullyQualifiedDomainName ,FQDN got is = Fileserver, status = 0|
(FSAReportingService) <16028> EV:H GetDomainNameForServer - IPV6 Unable to find the full DNS name for Fileserver

Cause

This can occur if reverse name lookup is not configured for the file server's hostname in the DNS environment
This can be confirmed by carrying out a nslookup command against the targeted FSA Servers IP Address:

1. Open command prompt on file server.
2. Type nslookup <IP Address of file server> (e.g. nslookup 10.0.0.1)

​nslookup should return the Fully Qualified Domain Name of the server similar to the below:

C:\Users\Administrator>nslookup 10.0.0.1
Server: dnsserver.domain.local
Address: 10.0.0.2

Name: fileserver.domain.local
Address: 10.0.0.1

If there is no PTR Record (Reverse Lookup Record) for the FSA server in the DNS domain then you may see an error similar to the below:

C:\Users\Administrator>nslookup 10.0.0.1
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: ::1

*** UnKnown can't find 10.0.0.1: Non-existent domain