Synchronize

When a delete is detected on either the source or the destination, the application will  DryvIQ will take action and delete the file on the opposing side. This option will never ignore delete events.

Copy

When a delete is detected on the source, the application DryvIQ will take action and 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, the application does  DryvIQ does not run change/delete detection on subsequent job runs, Delete Policy Mirror would not be applicable.

Publish

Delete Policy Mirror is not applicable.
Based on the definition of transfer type Publish, it must make deletes on the destination to ensure it matches the Source, so Delete Policy Mirror would not be applicable.

Move

Delete Policy Mirror is not applicable.
Based on the definition of transfer type Move, it must evaluate the source, transfer all content to the destination, then delete everything from the source, so Delete Policy Mirror would not be applicable.

Copy folder structure

Delete Policy Mirror is not applicable.
With transfer type Copy Folder Structure, the application does  DryvIQ does not run change/delete detection on subsequent job runs, Delete Policy Mirror would not be applicable.

Synchronize

When a delete is detected on the source, the application will  DryvIQ will ignore and take 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, the application will  DryvIQ will ignore it and take 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, the application does  DryvIQ does not run change/delete detection on subsequent job runs, Delete Policy Ignore Source would not be applicable.

Publish

Delete Policy Ignore Source is not applicable.
Based on the definition of transfer type Publish, it must make deletes on the destination to ensure it matches the source, so Delete Policy Ignore Source would not be applicable.

Move

Delete Policy Ignore Source is not applicable.
Based on the definition of transfer type Move, it must evaluate the source, transfer all content to the destination, then delete everything from the Source, so Delete Policy Ignore Source would not be applicable.

Copy folder structure

Delete Policy Ignore Source is not applicable.
With transfer type Copy Folder Structure, the application does  DryvIQ does not run change/delete detection on subsequent job runs, Delete Policy Ignore Source would not be applicable.

Synchronize

When a delete is detected on the destination, the application will  DryvIQ will ignore and take 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, the application will  DryvIQ will always use the Ignore Source Delete Policy, so Delete Policy Ignore Destination would not be applicable.

Migrate

Delete Policy Ignore Destination is not applicable. With transfer type Migrate, the application does  DryvIQ does not run change/delete detection on subsequent job runs, Delete Policy Ignore Destination would not be applicable.

Publish

Delete Policy Ignore Destination is not applicable. Based on the definition of transfer type Publish, it must make deletes on the destination to ensure it matches the Source, so Delete Policy Ignore Destination would not be applicable.

Move

Delete Policy Ignore Destination is not applicable. Based on the definition of transfer type Move, it must evaluate the source, transfer all content to the destination, then delete everything from the Source, so Delete Policy Ignore Destination would

Copy folder structure

Delete Policy Ignore Destination is not applicable. With transfer type Copy Folder Structure, the application does  DryvIQ does not run change/delete detection on subsequent job runs, Delete Policy Ignore Destination would not be applicable.