Accepted Solutions
kdrone, you seem very familiar with the application being that you are running a healthy sized implementation.
The process of getting device info from the filer to the indices is different under the two scenarios but let's group them for our discussion.
Scanning is the Hierarchical crawl of the data structure and is run on a schedule or demand. Auditing is the capture of I/O access to the data structure and runs 24X7. Both come from the device to the collector and are transferred to the indexer for further processing.
I'll assume all is well and you wish to put the files from the inbox on the indexer to the indices for reporting or display purposes. I am providing the option to initiate the job manually on demand; there is also the scheduled option where you could lessen the time between runs. Until the accumulated files transferred form the collector are indexed successfully there is no access to the information.
That occurs at the conclusion of the IndexWriterJob run against the files on a share by share basis. I will not go into it further but anyone in our support organization, technical product management or Sales Engineers could provide you a detailed view of the process. If you would like access to a document detailing each job please private message me and I'll direct you to the content.
To force the job to run on demand and not wait for the schedule so that you may see the data accumulated on the indexer sooner you may start it manually in the Symantec DataInsight version you have installed and all later versions.
Simply navigate to the settings tab and locate the DataInsight servers page then select the desired indexer holding the data you wish to see sooner from that page, navigate to the jobs tab and using the button for action start the job. Depicted in the pictures below is the location of these items.
I hope that answers your question. I'll check back after the weekend break (note - this weekend is bank holiday in the USA) and see if you have further follow up asks.
kdrone, you seem very familiar with the application being that you are running a healthy sized implementation.
The process of getting device info from the filer to the indices is different under the two scenarios but let's group them for our discussion.
Scanning is the Hierarchical crawl of the data structure and is run on a schedule or demand. Auditing is the capture of I/O access to the data structure and runs 24X7. Both come from the device to the collector and are transferred to the indexer for further processing.
I'll assume all is well and you wish to put the files from the inbox on the indexer to the indices for reporting or display purposes. I am providing the option to initiate the job manually on demand; there is also the scheduled option where you could lessen the time between runs. Until the accumulated files transferred form the collector are indexed successfully there is no access to the information.
That occurs at the conclusion of the IndexWriterJob run against the files on a share by share basis. I will not go into it further but anyone in our support organization, technical product management or Sales Engineers could provide you a detailed view of the process. If you would like access to a document detailing each job please private message me and I'll direct you to the content.
To force the job to run on demand and not wait for the schedule so that you may see the data accumulated on the indexer sooner you may start it manually in the Symantec DataInsight version you have installed and all later versions.
Simply navigate to the settings tab and locate the DataInsight servers page then select the desired indexer holding the data you wish to see sooner from that page, navigate to the jobs tab and using the button for action start the job. Depicted in the pictures below is the location of these items.
I hope that answers your question. I'll check back after the weekend break (note - this weekend is bank holiday in the USA) and see if you have further follow up asks.
