On This Page

Overview

DryvIQ uses jobs to perform specific actions between the source and destination platforms. Transfer type determines how content is transferred from the source to the destination. Some transfer types are set based on the transfer direction selected on the Job Type page, while others are set using a combination of the selected transfer direction and policy settings. The most common type of jobs are copy and sync. 

Copy

This transfer type is set when you select Transfer in one direction from a Source to a Destination as the transfer direction. This will copy all content (files, folders) from the source to the destination. Each Job run will detect any new content on the source and copy it to the destination. DryvIQ never modifies source content for a copy job. It only creates matching content on the destination. Subsequent job runs will evaluate the source for new content, and only this new content will be copied to the destination.

When a failure occurs during a copy transfer, the Job will continue and flag the failures at the end for review. When a failure occurs at the folder level, DryvIQ will not traverse this folder's content. It will be skipped, and the next folder will be evaluated for copy transfer.

API Setting

Synchronize

This transfer type is set when you select Transfer in both directions, syncing between two locations as the transfer direction. This ensures all content (files, folders) on the source and the destination are the same. Each job run will verify the source and destination match, modifying content on either the source or destination as needed. When subsequent sync jobs run, DryvIQ evaluates both the source and destination for any new content. Only the new content is transferred, to either side, to ensure the source and the destination match.

When a failure occurs during a synchronize transfer, the job will continue and flag the failures at the end for review. When a failure occurs at the folder level, DryvIQ will not traverse this folder's content. It will be skipped, and the next folder will be evaluated for synchronization.

API Setting

Move

This transfer type is set when you select Transfer in one direction from a Source to a Destination as the transfer direction and Delete the items from source once they have been successfully transferred as the delete policy. This will copy all content (files, folders) from the source to the destination. After verifying that everything was moved to the destination successfully, DryvIQ will delete all content from the source. DryvIQ will not delete any files that were not successfully copied to the destination during the initial transfer. These files will remain on the source. When subsequent move jobs run, DryvIQ will evaluate the source for new content, and the new content will be copied to the destination. After this transfer is successful, the files on the source will be deleted.

When a failure occurs during a move transfer, the job will continue and flag the failures at the end for review. When a failure occurs at the folder level, we will not traverse this folder's content. It will be skipped and the next folder will be evaluated for Move transfer.

API Setting

Migrate

This transfer type is set when you select Transfer in one direction from a Source to a Destination as the transfer direction and Do not transfer items that were not present on the initial run as the new items policy. This will copy all content (files, folders) from the source to the destination. Subsequent job runs will not pick up any new content; they will only retry content that encountered errors on the initial run. DryvIQ never modifies source content for a copy job. It only creates matching content on the destination. This transfer type is recommended for large transfer jobs where the content on the source is not expected to change. Migrate is more efficient because subsequent jobs don’t evaluate the entire structure again and only executes retry errors from the previous run.

When a failure occurs during a Migrate transfer, the job will continue and flag the failures at the end for review. When a failure occurs at the folder level, DryvIQ will not traverse this folder's content. It will be skipped, and the next folder will be evaluated for Migrate transfer.

API Setting

Publish

This transfer type can only be set using the REST API; it cannot be set through the user interface. It transfers in one direction from the source to the destination and will transfer new content identified on the source during subsequent job runs. It will also delete any content on the destination that does not match the source. This ensures the destination mirrors the source. It only creates matching content on the destination. Subsequent job runs will evaluate the source for new content, and only this new content will be copied to the destination. The job will also evaluate the destination for new content. If new content exists on the destination but is not present on the Source, DryvIQ will delete this content from the destination. Similarly, if content on the destination is newer than the source, this content will be reverted.

When a failure occurs during a Publish transfer, the job will continue and flag the failures at the end for review. When a failure occurs at the folder level, DryvIQ will not traverse this folder's content. It will be skipped, and the next folder will be evaluated for Publish transfer.

API Setting

Taxonomy

This transfer type is set when you select Replicate the folder structure of a Source onto a Destination as the transfer direction. This will copy the folder structure only from the source to the destination. No files will be transferred. DryvIQ will never modify any content on the source or the destination. It simply evaluates the folder hierarchy on the source and creates a matching structure on the destination. Subsequent jobs will evaluate the source for any new folders and/or subfolders. Only new empty directories will be created on the Destination.

When a failure occurs during a copy folder structure transfer, the job will continue and flag the failures at the end for review. When a failure occurs at the parent folder level, DryvIQ will not traverse this folder's subfolders. It will be skipped, and the next folder will be evaluated for Copy Folder Structure transfer.

API Setting