Error Message

# DFS shares dropped. make sure dropped filers are either configured as devices or added as alias for configured devices/filers and other share details are correct in input.

The most common cause for failing to import filers under a DFS root are:

1. The list of filers in the CSV file contains more filers than are configured as filers in Data insight.

2. The DFS server hosting the root is itself a filer configured in Data Insight.

3. The filer name in the imported CSV file does not match the filer name configured in Data Insight

Referring to the list:

1. Ensure that each filer in the CSV file is configured in Data Insight as a filer.

2. The server hosting the DFS root cannot be also a filer in Data Insight. If configured already, then the CSV import file could be modified manually to change the DFS root server name to a label not used by Data Insight. For example, "FinanceDFS". All the imported filers would then be visible under Data Insight DFS workspace under this label. Refer to the graphic below, the DFS server hosting the root "ISCSI01" is not configured as a filer under Data Insight. In this example, it has been configured as a DFS server only.

3. This can happen if FQDN is in one location and a short name in another. Refer to the graphic below, "foc2016fs.iasyd.veritas.com" has been configured with a FQDN and so the CSV file must match this.

 

Data Insight supports Microsoft Distributed File System (DFS) namespace. DFS collates the shared folders from multiple file servers and places them under one root so that they can be accessible by that root folder as if they were all physically located under that folder. The DFS folder structure can be imported into Data Insight to create a view where all the scanned files are visible under the DFS root in the Data Insight workspace. If certain conditions are not met, then Data Insight will fail to import the mapping file, or may import the data partially.