Welcome to
Help Desk

Product Updates
Ideas Contact Support

Scanning of Content Sources in Content Lifecycle



The Egnyte Secure & Govern (S&G) system relies on information from various sources to provide users insight into the data they have stored in Egnyte as well as other content sources they have connected. This information is aggregated in a database that can then be queried to present the information in the user interface. In order to provide visibility into Content Sources that are available in the Content Lifecycle view, the Egnyte backend systems need to scan all of that content initially and also perform periodic update scans to identify changes. The time it takes for these scans will vary depending on the amount of data that is in that content source (and the number of changes for the update scans). 

Initial Scan

Scan all files/folders in the content source. This includes gathering information on file metadata (size, creation date), content classification, and searching for duplicate files.

Update Scans

Scans changes in the files and folder structure, including updates regarding top policies and file types for the quick filters.


Q: How long do scans take?

A: Unfortunately, this is not an easy question to answer. The scan time varies based on several factors, including the number of files being scanned and other activities that share the same resources. For the initial scan, the estimate is 1M files per day.

Q: How often are update scans performed?

A: Updates are performed once per day for each source. However, if an update takes longer than a day to complete (due to significant changes to the source file system), new information will be available in the Content Lifecycle view as soon as the updates scan is completed.

Q: What is the last scan value?

A: The last scan value displayed for each source is the start time of the last scan that was completed. For example, if the last scan started on July 1, 2021 2:00PM and finished on July 2, 2021 09:00AM, the value would be July 1, 2021 2:00PM. This value is the start time of the last scan because that is when the data snapshot was taken. Changes made during the scan won't be reflected until the next scan is completed.

Q: How do updates scans affect issue detection?

A: Issue detection is run hourly and is independent of the update scans. 



Was this article helpful?
0 out of 0 found this helpful

For technical assistance, please contact us.