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 Commonly Used Platforms.

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, 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 normally done as part of the Simulation process. Transfer job execution time is not impacted when link detection is enabled because the document is scanned while the document is in memory as part of the normal migration process. Learn more about how link detection affects job performance here.

Link remediation operates separately from the migration and does not affect transfer times or speed. However, it adds time to the project as it requires an additional process for remediating links after 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 1000 files in a job takes about as much time as running a delta run with modifications to a 1000 files. This should be factored in when planning your project if you plan on using link detection and remediation. Learn more here.

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 that is migrated.

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 for roll-up reports. You can also pull a job audit log through the REST API.

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

DryvIQ stores file sizes in base-2 quantities. However, these values are displayed with base-10 prefixes, or SI (International System of Units), such as megabytes and gigabytes. Those prefixes are used 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" errors are 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 these are addressed.

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 failing URL. Then use the appropriate networking tools such as nslookup to troubleshoot and fix the DNS resolution. 

Please keep in mind that the same host name may resolve to different IP addresses based on the geographic location of the server. Any required network changes will need to be made in relation to the server(s) on which 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 to dl.boxcloud.com. Firewall rules must account for these subtle differences in order for DryvIQ to successfully run jobs.

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" tab, click on the Transfer Details breakdown status "retrying." This will direct you to the filtered "Items" list. Select the item then click the "View item history" link on the right toolbox.

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

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

2. Review all flagged items. This can be done through 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 what you can do to address each one on the Migration Remediation Best Practices page. Refer to it for assistance when reviewing your flagged items.