On This Page

Overview

Control the level of tracking and reporting for content that exists on both the source and destination platform, including 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.

The available inspection policy options are:

• none (Default)

• all

• filtered

• flagged

• shared

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. 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.

• Source: All content (files & folders) at all levels in the hierarchy will be tracked; items configured to be ignored/skipped through job policies will not be tracked. If the connection does not have access to a given folder in the hierarchy, DryvIQ cannot track and report these items.

• Destination: All content in the root (files and folders) that existed prior to the initial transfer will be tracked as destination only items and reported as ignored/skipped. All content (files and folders) in lower depths of the directory (subfolders) that existed prior to the initial transfer will not be tracked.

• Job type Sync: The destination will behave like the source.

• If the connection does not have access to a given folder in the hierarchy, DryvIQ cannot track and report these items.

"transfer": {
"item_inspection_policy": "none",
"item_inspection_policy_next": "none"
 }

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 job policies 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 option when creating a job.

• Source: All content in the root, folder, and subfolder directories including those configured to be skipped/ignored through job policies 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 job policies 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.

"transfer": {
"item_inspection_policy": "all",
"item_inspection_policy_next": "all"
 }

Filtered

The validation option to inspect filtered content will track items that have been ignored/skipped based on the job filters. 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 option when creating a job.

• Source: Filtered content configured to be skipped/ignored through job policies will be tracked.

• Destination: Content on the destination is not tracked for jobs that migrate in one direction from source to destination.

• Job type Sync: The destination will behave like the source.

• If the connection does not have access to a given folder in the hierarchy, DryvIQ cannot track and report these items.

"transfer": {
"item_inspection_policy": "filtered",
"item_inspection_policy_next": "filtered"
 }

Flagged

The validation option to inspect flagged content will track items that have been flagged during 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 option when creating a job.

• Source: Flagged content will be tracked.

• Destination: Content on the destination is not tracked for jobs that migrate in one direction from source to destination.

• Job type Sync: The destination will behave like the source.

• If the connection does not have access to a given folder in the hierarchy, DryvIQ cannot track and report these items.

"transfer": {
"item_inspection_policy": "flagged",
"item_inspection_policy_next": "flagged"
 }

Shared

The validation option to inspect shared content will track items that have are shared. 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 option when creating a job.

• Source: Filtered content configured to be skipped/ignored through job policies will be tracked.

• Destination: Content on the destination is not tracked for jobs that migrate in one direction from source to destination.

• Job type Sync: The destination will behave like the source.

• If the connection does not have access to a given folder in the hierarchy, DryvIQ cannot track and report these items.

"transfer": {
"item_inspection_policy": "shared",
"item_inspection_policy_next": "shared"
 }

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:

• Identified: This is the totals count of items or data identified on the source and destination (including flagged/retried items).

• 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.

• 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

GET {{url}}v1/transfers/{{job_id}}/stats/by_inspection