Deleted Items Job Policy

Learn how to configure how DryvIQ handles deleted content.

Updated at May 22nd, 2025

+ More

Table of Contents

Overview Mirror the Deletion When Items are Deleted from Source Ignore Items Deleted from Source Ignore Items Deleted from Destination Ignore Items Deleted from Both Source and Destination

Overview

When a delete is detected on either the source or the destination, the Deleted Items Policy determines how DryvIQ will behave. Regardless of the policy selected, the transfer direction selected for the job affects how deleted items can be handled. Refer to the information below to understand how the different transfer types handle each Deleted Items policy option.

Mirror the Deletion When Items are Deleted from Source

When a delete is detected on either the source or destination, DryvIQ will delete the file on the opposing side. This option will never ignore delete events. Based on the transfer direction selected for the job, you can expect the following behavior for the Mirror delete policy.

Transfer Direction	Behavior
Synchronize	When a delete is detected on either the source or the destination, DryvIQ will delete the file on the opposing side. This option will never ignore delete events.
Copy	When a delete is detected on the source, DryvIQ will delete the file on the destination on subsequent job runs. This option will never ignore delete events.
Migrate	Delete Policy Mirror is not applicable. With transfer type Migrate, DryvIQ does not run change/delete detection on subsequent job runs, so the Mirror delete policy would not be applicable.
Publish	Delete Policy Mirror is not applicable. Based on the definition of transfer type Publish, DryvIQ must make deletes on the destination to ensure it matches the Source, so the Mirror delete policy would not be applicable.
Move	Delete Policy Mirror is not applicable. Based on the definition of transfer type Move, DryvIQ must evaluate the source, transfer all content to the destination, and then delete everything from the source, so the Mirror delete policy would not be applicable.
Replicate Folder Structure	Delete Policy Mirror is not applicable. With transfer type “replicate folder structure,” DryvIQ does not run change/delete detection on subsequent job runs, the delete policy Mirror would not be applicable.

Ignore Items Deleted from Source

When a delete is detected on the source, DryvIQ will ignore and take no action. If a delete is detected on the destination, the delete will propagate. This is the default Delete Policy for Copy jobs. Based on the transfer direction selected for the job, you can expect the following behavior for the Ignore Source delete policy. Note that this is the only delete policy available for Intelligent Migration jobs.

Transfer Direction	Behavior
Synchronize	When a delete is detected on the source, DryvIQ ignores it and takes no action. If a delete is detected on the destination, the delete will still occur.
Copy	This is the default delete policy for Copy jobs. When a delete is detected on the source, DryvIQ ignores it and takes no action. If a delete is detected on the destination, the delete will still occur.
Migrate	Delete Policy Ignore Source is not applicable. With transfer type Migrate, DryvIQ does not run change/delete detection on subsequent job runs, so the Ignore Source delete policy would not be applicable.
Publish	Delete Policy Ignore Source is not applicable. Based on the definition of transfer type Publish, DryvIQ must make deletes on the destination to ensure it matches the source, so the Ignore Source delete policy would not be applicable.
Move	Delete Policy Ignore Source is not applicable. Based on the definition of transfer type Move, DryvIQ must evaluate the source, transfer all content to the destination, and then delete everything from the source, so the Ignore Source delete policy would not be applicable.
Replicate Folder Structure	Delete Policy Ignore Source is not applicable. With transfer type Replicate Folder Structure, DryvIQ does not run change/delete detection on subsequent job runs, so the Ignore Source delete policy would not be applicable.

Ignore Items Deleted from Destination

When a delete is detected on the destination, DryvIQ will ignore it and take no action. If a delete is detected on the source, the delete will propagate. Based on the transfer direction selected for the job, you can expect the following behavior for the Ignore Destination delete policy.

Transfer Direction	Behavior
Synchronize	When a delete is detected on the destination, DryvIQ ignores it and takes no action. If a delete is detected on the source, the delete will still occur.
Copy	Delete Policy Ignore Destination is not applicable. With transfer type Copy, DryvIQ will always use the Ignore Source delete policy, so the Ignore Destination delete policy would not be applicable.
Migrate	Delete Policy Ignore Destination is not applicable. With transfer type Migrate, DryvIQ does not run change/delete detection on subsequent job runs, so the Ignore Destination delete policy would not be applicable.
Publish	Delete Policy Ignore Destination is not applicable. Based on the definition of transfer type Publish, DryvIQ must make deletes on the destination to ensure it matches the source, so the Ignore Destination delete policy would not be applicable.
Move	Delete Policy Ignore Destination is not applicable. Based on the definition of transfer type Move, DryvIQ must evaluate the source, transfer all content to the destination, and then delete everything from the source, so the Ignore Destination delete policy would not be applicable.
Replicate Folder Structure	Delete Policy Ignore Destination is not applicable. With transfer type Replicate Folder Structure, DryvIQ does not run change/delete detection on subsequent job runs, so the Ignore Destination delete policy would not be applicable.

Ignore Items Deleted from Both Source and Destination

When a delete is detected on either the source or destination, DryvIQ will ignore it and take no action. Ignore Both is the system default delete policy. Based on the transfer direction selected for the job, you can expect the following behavior for Ignore Both delete policy.

Transfer Direction	Behavior
Synchronize	When a delete is detected on either the source or the destination, DryvIQ ignores it and takes no action.
Copy	Delete Policy Ignore Both is not applicable. With transfer type Copy, data transfer occurs in one direction from source to destination, so the Ignore Both delete policy is not be applicable. The default delete policy for copy jobs is to ignore items deleted from the source.
Migrate	Delete Policy Ignore Both is not applicable. With transfer type Migrate, DryvIQ does not run change/delete detection on subsequent job runs, so the Ignore Both delete policy is not applicable.
Publish	Delete Policy Ignore Both is not applicable. Based on the definition of transfer type Publish, DryvIQ must make deletes on the destination to ensure it matches the source, so the Ignore Both delete policy would not be applicable.
Move	Delete Policy Ignore Both is not applicable. Based on the definition of transfer type Move, DryvIQ must evaluate the source, transfer all content to the destination, and then delete everything from the source, so the Ignore Both delete policy would not be applicable.
Replicate Folder Structure	Delete Policy Ignore Both is not applicable. With transfer type Replicate Folder Structure, DryvIQ does not run change/delete detection on subsequent job runs, so the Ignore Both delete policy would not be applicable.

migrate migrations job policy deleted items mirror delete ignore source ignore destination