Mount point contents are missing after scanning a share that contains reparse points
Article ID: 100015941
Updated On:
Description
Example
Application:
-
The user’s home directories are shared out from the D:\Production\IT\Corporate\Home\Users folder.
-
Each of the user’s folders are mount points in this directory. Everyone in the company knows this folder as Company\Users\Username.
Real Server:
Veritas.Server.com
| Column 1 | Column 2 | Column 3 | Column 4 | Column 5 |
| VIRTUAL SERVER NAME | VIRTUAL\PATH\SHARENAME | REAL.SERVER.FQDN | REAL SHARE NAME | REAL PHYSICAL PATH |
| Company | Users\Bob | Veritas.Server.Com | Bob | Production\IT\Corporate\Home\Users\Bob |
| Company | Users\Jane | Veritas.Server.Com | Jane | Production\IT\Corporate\Home\Users\Jane |
Cause
Data Insight does not scan reparse points.
This is by design, to prevent the process from becoming trapped within an infinite loop.
While this behavior cannot be changed, a workaround is to consolidate multiple shares under one name space, in a logical manner, without a Distributed File System (DFS) server.
Once this is complete, the end-user will still be able to access a share that contains reparse points, and Data Insight will contain all of the access data.
Resolution
Use the DFS mapping import feature to consolidate multiple, individual shares under one namespace.
This is done without using a DFS server.
1. For each reparse point in the share, create a new individual share.
Note: Data Insight cannot scan reparse points unless the root of the share is a mount point. In this case, the scan starts from inside the mounted volume.
2. Add the shares that you just created in Step 1 to the filer in Data Insight.
3. Scan all of the shares so that the shares now appear in Data Insight.
4. Create a DFS that maps the CSV file to import into Data Insight. This option is available in the Data Insight Console under Settings - Inventory - Filers - Import DFS Mapping
Review Table 1 for instructions below for further information about contents of the CSV file. Do not use the instructions in the Administrator Guide unless you are using a DFS server.
Table 1 - CSV File Explanation
The CSV spreadsheet will contain five columns. Add an additional row for each individual share that was created in Step 1. Note: Some of the data in this spread sheet will be redundant. |
||||
| Column 1 | Column 2 | Column 3 | Column 4 | Column 5 |
| VIRTUAL SERVER NAME | VIRTUAL\PATH\SHARENAME | REAL.SERVER.FQDN | REAL SHARE NAME | REAL PHYSICAL PATH |
| A virtual Server name. This server name does not exist anywhere because you are not using a DFS server. This name will show up in Data Insight as the main namespace that is being scanned. This namespace should be something that is meaningful to the people that must read reports on this namespace. Note: Do not use a real server name of any kind unless you have a DFS server that is presenting the shares. |
This is a virtual path to the reparse point folder in your original share. Do not start with a "\". Include every folder, from the root up to the reparse folder, or mount point. Include the name of the reparse folder, or mount point folder. Note: This is not the same share that you created in Step 1. This is the original share that is used by the actual end users. This is the share you are trying to track with Data Insight. This column represents what the DI administrator sees in the DI GUI when he navigates to the namespace that is listed in Column 1. |
The fully-qualified domain name (FQDN) of the filer that has the share. | The share name only. Note: Do not include "\\" or the hostname. Only include the share name. |
The physical path to the individual share that is defined in Column 4. Do not include "C:\" etc... |
Issue/Introduction
