On This Page
Overview
The Validation report allows you to run a content inspection and to view the content reconciliation that has occurred between the source and destination.
If the connection does not have access to a given folder in the hierarchy, DryvIQ cannot track and report these items.
Content Inspection
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.
For the source, DryvIQ will track all 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 tracked.
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.
The Item Inspection Policy cannot be set in the user interface. You will need to use the Scripting option when creating a job to change the Item Inspection policy.
Content Reconciliation
The content reconciliation provides a comparison of the reconciled items between the source and destination. It can help track the success of the migration. By default, it shows the counts for files and folders, but you can choose to view just folders, just folders, or data. The items reported in this section vary based on what policies and filters have been set for the job and based on what happened during the job run.
Ignored Categories
Reason | Description |
|---|---|
Content extension | Ignored due to third-party extension |
Date | Ignored due to date range filter |
Destination only items | Ignored on the destination |
Empty container policy | Ignored due to empty container policy |
File extension | Ignored due to file extension filter |
Hidden | Ignored due to hidden file/folder filter |
Item type | Ignored due to file type filter |
Large item policy | Ignored due to large item policy i.e. file too large to be transferred to destination platform |
Match fail | Ignored due to error in calculating a destination path |
Metadata | Ignored due to metadata filter |
One way transfer | For one way transfer - destination only items which were not transferred to source |
Overwrite policy | Ignored due to overwrite policy |
Path | Ignored due to path filter |
Pattern | Ignored due to item name pattern filter |
Predefined | Ignored due to predefined content categories filter |
Restricted content policy | Ignored due to restricted content policy |
Shared | Ignored due to shared item filter |
Size | Ignored due to file size filter |
Unknown filter reason | Unknown reason, includes items ignored by previous DryvIQ versions on upgraded installations |
These categories are also available as filters in the Jobs grid. Select to filter by status “Ignored,” and select the subcategory to use.