...
On This Page
| Table of Contents |
|---|
Overview
Control The Validation report allows you to run a content inspection and to view the content reconciliation that has occurred between the source and destination.
| Info |
|---|
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 , including 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. This feature categorizes items for reports on the job Validation tab or within the job transfer block with "item_inspection_policy." Items that have been ignored / skipped by policy or not shown because they already existed on the destination can now be seen on reports with the defined categories.
All job types and transfer directions support validation:
Basic transfer, Folder mapping, User job mapping, Network home drive mapping
Simulation Mode (Analyzer)
Transfer in one direction with copy and both directions with sync
Jobs using Impersonation (Run as user)
| Info |
|---|
Only the Content Reconciliation is available on the Validation report for roll-up reports. |
Default Configuration: "item_inspection_policy": "none"
The default validation option is inspect none. This option does not need to be configured in the application user-interface or through the ReST API; it is the system default. By default, this policy is set to “none.” This configuration will not track all items but will offer additional tracking with performance in mind. Inspect none will track all items on the source at all levels of the hierarchy but not including those configured to be ignored / skipped through policy. For the destination, all content in the root (files & folders) that existed prior to the initial transfer will be tracked as destination only items and reported as ignored/skipped.
This option has the following features:
...
This option does not need to be configured in the application user interface or through the REST API; it is the system default. Jobs created in previous releases will now assume this settings after upgrade. A soft reset will be required to align the validation chart calculations using the inspect none configuration.
...
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 (sub-folders) that existed prior to the initial transfer will not be tracked
...
If the connection does not have access to a given folder in the hierarchy, we cannot track and report these items.
...
.
...
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.
...
Validation Default | JSON Configuration
...
| Code Block |
|---|
"transfer": {
"item_inspection_policy": "none",
"item_inspection_policy_next": "none"
} |
Track Everything | "item_inspection_policy": "all"
The validation option to inspect all will track all content at all levels in the hierarchy on both the source and destination; including items configured to be ignored/skipped through policy and items that existed on the destination prior to the initial transfer.
This option has the following features:
This option can be configured via the REST API or in the application user interface through the Advanced Scripting JSON block.
Source: All content in the root, folder, and subfolder directories including those configured to be skipped/ignored through policy and items that existed on the destination prior to the initial transfer will be tracked.
Destination: All content in the root, folder, and subfolder directories including those configured to be skipped/ignored through policy and items that existed on the destination prior to the initial transfer will be tracked.
If the connection does not have access to a given folder in the hierarchy, we cannot track and report these items.
...
Validation Track Everything | JSON Configuration
...
| Code Block |
|---|
"transfer": {
"item_inspection_policy": "all",
"item_inspection_policy_next": "all"
} |
If filtered and shared items are already being inspected for the job, these options will be disabled.
...
| Info |
|---|
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. It reports on the following information: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.
Identified: This is the totals count of items or data identified on the source and destination (including flagged/retried items).
Ignored [policy]: This is the content that was ignored based on the specified policy set for the job.
Ignored destination only items: This is the count of the items ignored on the destination and the percentage of the overall content theses items make up.
Retrying (not transferred): This is the number of items set to be retried on the next job tun.
Ignored [Filter]: If filters were added to the job to exclude content, any entry for each filter is included in this section. It will identify the count of the filtered items and the percentage of the overall content theses items make up.
Successfully matched or transferred (Including flagged and revised): This is the count of items or data that have been successfully matched or transferred between the course and destination.
REST API | Transfer Stats, By Inspection
| Code Block |
|---|
GET {{url}}v1/transfers/{{job_id}}/stats/by_inspection |
...