06-14-2017 03:36 PM
There should be a way to merge or connect access information when multiple shares contain the same file. For Example these duplicate shares would have different access information about the same file:
Windows Admin: \\SERVER\C$\share\users\user1\file1.txt
Data Admin: \\SERVER\users\user1\file1.txt
Individual user: \\SERVER\user1\file1.txt
A file could be modified via any number of shares and the access data may not appear when looking at it through a specific share name.
06-14-2017 03:46 PM
Bdabel, which version are you currently running.
It would appear you are asking about a nested share on a windows host sharing to clients.
We have Product Action Request (PAR) for entering an Enhancement to the application for things you would like to see in the future.
Based on the device you are capturing I/O from and the version of Data Insight we can advise you as to what is currently possible so if you would like to expound on the details we may be able to provide you more information.
Rod
06-20-2017 03:34 PM
Data Insight 5.2.1. NetApp.
06-21-2017 10:53 AM
Thank you Bdabel,
you currently have a version that is a current version for the 5.2 application tree. While we have altered calculations for license (by TB) there is not a GUI view for merging the same share accessed by multiple methods. The procedure for consideration for possible inclusion in a future version would be to reach out to your Veritas account team representative for addition of an enhancement request.
As a potential workaround in the meantime consider that you suggested a share or nested share could be accessed by different path locations or even shared out via different systems in some cases. We do have reporting that could produce for you a detailed access (auditing ) report. We do not display this in the console's workspace view as the drilldowns are based on the access path due to the display being a particular path.
Consider how the data is gathered when understanding why this is so.
The actual device would provide data in the form of:
device_id|opcode|username|domainname|sid|pathname|renamepath|type|imagename|ipaddr|timestamp|gennumber
We would then have to parse the data for transfer to the Data Insight indexer in the form:
id|opcode|username|domainname|sid|pathname|renamepath|type|imagename|ipaddr|timestamp
We would expect the pathname to match an existing record in the index for the particular Share ID or we would create a new record for that instance. If I wanted to view that event in the workspace I would navigate to the share and drill down to the object to see the registered accesses or I could could create a report to capture the same thing.
In a report I would be able to specify multiple access points and view similar objects (or even create a report on one object from multiple shares).
Something like:
HeaderTable | ||
Created By | Report Type | Report Name |
Veritas Data Insight 5.2.0.8800 | Activity Details for Paths | Nested_Path_Access |
ParamTable | ||
Name | Value | |
Paths: | \\win2008r2nas\dept\IT, \\192.168.10.125\Dept\IT, \\NETAPPCM\dept\IT | |
Operations: | mkdir, checkin, view, rmdir, rename, link, dirread, update, renamedir, create, copy, symlink, write, dirwrite, move, security, read, delete, checkout, undelete, permchange |
A small sampling of the data returned would be:
File Server \ Web Application | Access Path | Path Name | Path Type | User Name | User Account | Meta Access Type | IP Address | BU Name | BU Owner | Start Time | End Time | Event Count | Total | DFS Path | Access Type | Permission Change Details |
win2008r2nas | \\win2008r2nas\dept\IT\IT_File_13.txt | IT_File_13.txt | File | Laine | LSingleton@SAMGWIN.local | Write | 0.0.0.0 | Mar 11, 2017, 2:28 AM | Mar 11, 2017, 2:28 AM | 1 | 100000 | Write | ||||
win2008r2nas | \\win2008r2nas\dept\IT\IT_File_13.txt | IT_File_13.txt | File | Larita | LBuckner@SAMGWIN.local | Read | 0.0.0.0 | Mar 16, 2017, 12:22 AM | Mar 16, 2017, 12:22 AM | 1 | 100000 | Read | ||||
win2008r2nas | \\win2008r2nas\dept\IT\IT_File_13.txt | IT_File_13.txt | File | Larita | LBuckner@SAMGWIN.local | Write | 0.0.0.0 | Mar 16, 2017, 12:22 AM | Mar 16, 2017, 12:22 AM | 1 | 100000 | Write | ||||
win2008r2nas | \\win2008r2nas\dept\IT\IT_File_13.txt | IT_File_13.txt | File | Larita | LBuckner@SAMGWIN.local | Read | 0.0.0.0 | Mar 14, 2017, 12:21 AM | Mar 14, 2017, 12:21 AM | 1 | 100000 | Read | ||||
win2008r2nas | \\win2008r2nas\dept\IT\IT_File_13.txt | IT_File_13.txt | File | Larita | LBuckner@SAMGWIN.local | Write | 0.0.0.0 | Mar 14, 2017, 12:21 AM | Mar 14, 2017, 12:21 AM | 1 | 100000 | Write | ||||
NETAPPCM | \\NETAPPCM\dept\IT\IT_File_13.txt | IT_File_13.txt | File | Akilah | ATrujillo@SAMGWIN.local | Read | 192.168.10.22 | Mar 10, 2017, 7:22 AM | Mar 10, 2017, 7:22 AM | 1 | 100000 | Read | ||||
NETAPPCM | \\NETAPPCM\dept\IT\IT_File_13.txt | IT_File_13.txt | File | Akilah | ATrujillo@SAMGWIN.local | Write | 192.168.10.22 | Mar 10, 2017, 7:22 AM | Mar 10, 2017, 7:22 AM | 1 | 100000 | Write | ||||
NETAPPCM | \\NETAPPCM\dept\IT\IT_File_13.txt | IT_File_13.txt | File | Akilah | ATrujillo@SAMGWIN.local | Read | 192.168.10.22 | Mar 9, 2017, 11:45 AM | Mar 9, 2017, 11:45 AM | 1 | 100000 | Read | ||||
NETAPPCM | \\NETAPPCM\dept\IT\IT_File_13.txt | IT_File_13.txt | File | Akilah | ATrujillo@SAMGWIN.local | Write | 192.168.10.22 | Mar 9, 2017, 11:45 AM | Mar 9, 2017, 11:45 AM | 1 | 100000 | Write | ||||
NETAPPCM | \\NETAPPCM\dept\IT\IT_File_13.txt | IT_File_13.txt | File | Akilah | ATrujillo@SAMGWIN.local | Read | 192.168.10.22 | Mar 8, 2017, 6:00 PM | Mar 8, 2017, 6:00 PM | 1 | 100000 | Read | ||||
NETAPPCM | \\NETAPPCM\dept\IT\IT_File_13.txt | IT_File_13.txt | File | Akilah | ATrujillo@SAMGWIN.local | Write | 192.168.10.22 | Mar 8, 2017, 6:01 PM | Mar 8, 2017, 6:01 PM | 1 | 100000 | Write | ||||
NETAPPCM | \\NETAPPCM\dept\IT\IT_File_13.txt | IT_File_13.txt | File | Akilah | ATrujillo@SAMGWIN.local | Read | 192.168.10.22 | Mar 8, 2017, 1:58 AM | Mar 8, 2017, 1:58 AM | 1 | 100000 | Read |
I hope you find that useful.
Rod
06-21-2017 02:55 PM - edited 06-21-2017 02:56 PM
related link to Enhancement procedure of reaching out to the account team in case you needed it.
https://www.veritas.com/support/en_US/article.000116044