Each platform requires unique information to create a connection to it. You can find instructions on how to create a connection for each platform DryvIQ supports under Supported Platform Connection. 

An account map is used to map users from one platform to another. The easiest way to do this is to create an account map CSV file and import the mapping file into the account map that will be used for the job. 

Yes, you can add filters to a job to include or exclude specific content based on various filters. Learn how to add filters to your job here . 

When link detection is enabled, the simulation job execution time increases due to the need to download the document into memory for link detection, which is an additional step that isn’t generally done as part of the Simulation process. Link detection does not impact transfer job execution time because DryvIQ scans the document while it is in memory as part of the normal migration process. 

Link remediation operates independently of migration and does not impact transfer times or speed. However, it adds time to the project since it requires an additional process for remediating links after the files are migrated. The link remediation process is roughly equivalent to the extra time it would take to do another delta run on a document count basis. For example, remediating links in 1,000 files in a job takes about the same amount of time as running a delta run with modifications to 1,000 files. You need to account for this extra time when planning your project if you plan on using link detection and remediation. Refer to “Link Detection and Remediation” for more information. 

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. 

1. Review the log message. DryvIQ logs a reason why it flagged the item. On the job Overview page, click on the Transfer Details breakdown status "flagged." This selection takes you to the filtered "Items" list. Select the item and click the "View item history" link in the toolbox on the right side of the page. Review the message and determine if you can resolve it on the source platform.
   
   

2. Review all flagged items. You can do this on the Flagged Items page or by filtering the Items Report to display just flagged items. You can export a list of the flagged items and retry items from both locations. 
   
   

   

DryvIQ provides a list of errors and suggestions on how to address each one on the Migration Remediation Best Practices page. Refer to it for assistance when reviewing your flagged items.  

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 in Service: 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.

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

DryvIQ stores file sizes in base-2 quantities but displays these values with base-10 prefixes, or SI (International System of Units), such as megabytes and gigabytes. DryvIQ uses these prefixes since most users are familiar with that notation. Because of the risk of confusing the user with the lesser-known base-2 notation (for example, mebibytes or gibibytes), we chose to display base-10 notation. When using a conversion tool such as searching "808884388 bytes to MB" in Google, be sure to either specify "MiB" (mebibytes) in the search string or change the resulting units to an appropriate base-2 unit of measure.

The "No such host is known" error is caused by DNS resolution failures. Most of the time, DryvIQ can recover from these errors and retry the transfer successfully. However, if there are permanent issues with DNS resolution, DryvIQ will not be able to resolve the host until you address the problems.

The first step in fixing these issues is to review the job log to determine which URLs are failing. Start by searching for "Failure": "No such host is known" in the job log file. The corresponding RequestUri value will provide the URL that is failing. Then, use the appropriate networking tools, such as nslookup, to troubleshoot and resolve the DNS issue. 

Please note that the same hostname may resolve to different IP addresses based on the geographic location of the server. You must make the required network changes to the server(s) where DryvIQ is installed. Also note that many platforms will redirect traffic to other domains or sub-domains based on the request. For example, Box file uploads will be redirected to upload.box.com, and file downloads will be redirected to dl.boxcloud.com. Firewall rules must account for these subtle differences for DryvIQ to run jobs successfully.

1. Rerun the job. 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.
   

   

No, simulation jobs do not count towards the Data Migrated “Volume used” until simulation is disabled and the job is run as a standard job (in normal mode).

The “Volume used” value is calculated based on the amount of data DryvIQ migrates. 

Delta migration job runs increase the Data Migrated “Volume used” by the size of the new items migrated as part of that job run. For edited items, the increment will be the full size of the changed item(s) and NOT the difference in size due to the changes.

Recreating or resetting migration jobs will increase the Data Migrated “Volume used” by the size of the items migrated as part of that job run. 

For migration jobs, review the Items report for individual jobs or roll-up reports. You can also pull a job audit log job audit log through the REST API.