On This Page

Overview

Items that were unable to be transferred by the DryvIQ Platform will be flagged for manual remediation. Items can be flagged for many reasons, and in some cases, still transferred to the destination platform. Each item is a package, consisting of the media itself, version history, author, sharing, and any other metadata. DryvIQ ensures all pieces of the item package are transferred to the destination to preserve data integrity. When an item is flagged, DryvIQ is indicating that all or some portion of this failed to migrate.

All migrations require some amount of manual intervention by the client to move content that fails to transfer automatically. Note that simulation mode is recommended prior to a production migration to assess potential content that could fail to transfer and the reason. Simulation mode can also be used to adjust the job parameters to achieve a higher number of automatic remediation successes.

What are the most common reasons content doesn’t transfer?

1. Errors from Source and Destination Platforms: This is a broad error category that indicates DryvIQ was prevented from reading, downloading, uploading or writing content during content transfer by either the source or destination platform provider. Each situation is dependent on the storage provider's rejection reason and will require manual investigation to resolve.

2. Insufficient Permissions: Many platforms require additional permissions to perform certain functions, even for site administrator accounts. These permissions typically require a special request from the storage provider. For example, content that has been locked, hidden, or flagged to disable download may require this special permission request from your storage provider.

3. Scenario-Specific Configuration: The content on your source storage platform is diverse, and users across your business will structure their data in a wide variety of ways. A single one-size-fits-all project configuration may not be suitable and can result in some content not transferring to the destination platform. DryvIQ will assist in assessing these situations to help provide a custom, scenario-specific configuration that may work around the issue preventing the transfer.

4. Disparate Platform Features: Each platform provider has a distinct set of features that generally share common concepts within the storage industry. However, within each storage platform, there can be behavioral or rule differences within these features, and aligning these discrepancies can be challenging. Features such as permission levels (e.g., edit, view, view + upload) may not align exactly with the destination platform, or file size restrictions or file names may need to be altered to conform to the destination platform's policies. DryvIQ will attempt to accommodate these restrictions through system configurations; however, not all scenarios can be covered within a diverse data set.

5. Interruption: DryvIQ must maintain a continuous connection to the database throughout the transfer process. If there is an interruption in service, DryvIQ will fail the transfer as it is unable to track/write to the database.

How do I validate my content transferred successfully?

Verify the destination platform. DryvIQ will report all content that has transferred to the destination. Log in to your destination platform and verify that the content is located as expected

DryvIQ is reporting items in "pending" or "retrying" status. What are my next steps?

1. Run the job again: DryvIQ defaults to retrying the job 3 times to reconcile items that are in pending/retry status. Depending on your job configuration, this may occur with the defined schedule, or you can start the job manually.

2. Review the log message: DryvIQ logs a reason why the item is in pending/retry status. On the job Overview page, click on the Transfer Details breakdown status "retrying." This selection takes you to the filtered "Items" list. Select the item and then click the "View item history" link in the toolbox on the right side of the page.

DryvIQ is reporting items in "Flagged" status. What are my next steps?

When an item is in "flagged" status, it means DryvIQ has made all attempts to transfer the file without success, and manual remediation is required. 

Review the log message: DryvIQ logs a reason why the item has been flagged. On the job "Overview" tab, click on the Transfer Details breakdown status "flagged." This will direct you to the filtered "Items" list. Select the item and click the "View item history" link on the right toolbox. Review the message and determine if you can resolve on the source platform.

Review all flagged items: These are the recommended ways to view all flagged items: export the flagged item report or review the "Flagged Items" page. 

1. Export the report:

2. Review "Flagged Items" page. From here, you can:

• Retry or Ignore individual items.

• View Item History for individual items.

• Link back to the job to which the flagged items is associated.

• Export all Flagged Items report.