...
DryvIQ allows you to control the level of tracking and reporting for content that exists on both the source and destination platform through the Item Inspection Policy. This includes content that has been configured to be excluded from transfer and content that existed on the destination prior to the initial transfer. By default, this policy is set to “none.” This configuration will not track all items but will offer additional tracking with performance in mind“filtered,” which inspects filtered content that have been ignored/skipped based on the job filters.
For the source, DryvIQ will track all filtered content (files and folders) at all levels in the hierarchy; items configured to be ignored based on various policies set for the job will not be tracked. For sync jobs, the destination will we treated like the source.
For the destination, all content in the root (files and folders) that existed prior to the initial transfer will be tracked as destination only items and will be reported as ignored/skipped. All content in lower depths of the directory (subfolders) that existed prior to the initial transfer will not be trackedis not tracked for jobs that migrate in one direction from source to destination..
At any time, you can run a job to perform validation on filtered and/or shared items. This will trigger a full inspection of the selected content for the next run only. If filtered and shared items are already being inspected for the job, these options will be disabled.
...