Issue: In Skysync there is an option to select a specific delete propagation however, the use of this is unknown.

Delete Propagation determines how SkySync will deal with files that it detects have been deleted. By default Ignore Both is selected which means that no changes will be made on either the source or destination regardless as to what files are deleted.

There are three additional options beyond Ignore Both and they are explained in further detail down below, however they only affect Bi-Directional Sync jobs.

Mirror

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

Expand

title	Expand for more information

Extended Description: Based on your transfer type selected, you can expected the following behavior for Delete Policy Mirror:

Bi-Directional Sync - When a delete is detected on either the source or the destination, SkySync will take action and delete the file on the opposing side. This option will never ignore delete events.

Copy -

When

Delete Policy Mirror is not applicable When a delete is detected on either the source or the destination, SkySync will take action and delete the file on the opposing side. This option will never ignore delete events.

Migrate - Delete Policy Mirror is not applicable. With transfer type Migrate, SkySync 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, SkySync does not run change/delete detection on subsequent job runs, Delete Policy Mirror would not be applicable.

Ignore Source

When a delete is detected on the Source, the application will ignore and take no action. If a delete is detected on the Destination, the delete will propagate.

Expand

title	Expand for more information

Extended Description: Based on your transfer type selected, you can expected the following behavior for Delete Policy Ignore Source:

Bi-Directional Sync - When a delete is detected on the source, SkySync will ignore and take no action. If a delete is detected on the destination, the delete will still occur.

Copy -

When

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

Ignore Destination

When a delete is detected on the Destination, the application will ignore and take no action. If a delete is detected on the Source, the delete will propagate.

Expand

title	Expand for more information

Extended Description: Based on your transfer type selected, you can expected the following behavior for Delete Policy Ignore Destination:

Bi-Directional Sync - When a delete is detected on the destination, SkySync 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, SkySync 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, SkySync 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 not be applicable.

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

Ignore Both (Default selection)

When a delete is detected on either the Source or the Destination, the application will ignore and take no action. This is the system default option.

Expand

title	Expand for more information

Extended Description: Based on your transfer type selected, you can expected the following behavior for Delete Policy Ignore Both:

Bi-Directional Sync - When a delete is detected on either the source or the destination, SkySync will ignore and take no action.

Copy - Delete Policy Ignore Both is not applicable. With transfer type Copy, SkySync will always use the Ignore Source Delete Policy, so Delete Policy Ignore Both would not be applicable

Migrate - Delete Policy Ignore Both is not applicable. With transfer type Migrate, SkySync does not run change/delete detection on subsequent job runs, Delete Policy Ignore Both would not be applicable.

Publish - Delete Policy Ignore Both 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 Both would not be applicable.

Move - Delete Policy Ignore Both 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 Both would not be applicable.

Copy Folder Structure - Delete Policy Ignore Both is not applicable. With transfer type Copy Folder Structure, SkySync does not run change/delete detection on subsequent job runs, Delete Policy Ignore Both would not be applicable.

Page Comparison

Versions Compared

Old Version 6

New Version Current

Key

Issue: In Skysync there is an option to select a specific delete propagation however, the use of this is unknown.

Delete Propagation determines how SkySync will deal with files that it detects have been deleted. By default Ignore Both is selected which means that no changes will be made on either the source or destination regardless as to what files are deleted.

There are three additional options beyond Ignore Both and they are explained in further detail down below, however they only affect Bi-Directional Sync jobs.

Mirror

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

Extended Description: Based on your transfer type selected, you can expected the following behavior for Delete Policy Mirror:

Bi-Directional Sync - When a delete is detected on either the source or the destination, SkySync will take action and delete the file on the opposing side. This option will never ignore delete events.

Copy -

Delete Policy Mirror is not applicable When a delete is detected on either the source or the destination, SkySync will take action and delete the file on the opposing side. This option will never ignore delete events.

Migrate - Delete Policy Mirror is not applicable. With transfer type Migrate, SkySync 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, SkySync does not run change/delete detection on subsequent job runs, Delete Policy Mirror would not be applicable.

Ignore Source

When a delete is detected on the Source, the application will ignore and take no action. If a delete is detected on the Destination, the delete will propagate.

Extended Description: Based on your transfer type selected, you can expected the following behavior for Delete Policy Ignore Source:

Bi-Directional Sync - When a delete is detected on the source, SkySync will ignore and take no action. If a delete is detected on the destination, the delete will still occur.

Copy -

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

Ignore Destination

When a delete is detected on the Destination, the application will ignore and take no action. If a delete is detected on the Source, the delete will propagate.

Extended Description: Based on your transfer type selected, you can expected the following behavior for Delete Policy Ignore Destination:

Bi-Directional Sync - When a delete is detected on the destination, SkySync 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, SkySync 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, SkySync 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 not be applicable.

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

Ignore Both (Default selection)

When a delete is detected on either the Source or the Destination, the application will ignore and take no action. This is the system default option.

Extended Description: Based on your transfer type selected, you can expected the following behavior for Delete Policy Ignore Both:

Bi-Directional Sync - When a delete is detected on either the source or the destination, SkySync will ignore and take no action.

Copy - Delete Policy Ignore Both is not applicable. With transfer type Copy, SkySync will always use the Ignore Source Delete Policy, so Delete Policy Ignore Both would not be applicable

Migrate - Delete Policy Ignore Both is not applicable. With transfer type Migrate, SkySync does not run change/delete detection on subsequent job runs, Delete Policy Ignore Both would not be applicable.

Publish - Delete Policy Ignore Both 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 Both would not be applicable.

Move - Delete Policy Ignore Both 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 Both would not be applicable.

Copy Folder Structure - Delete Policy Ignore Both is not applicable. With transfer type Copy Folder Structure, SkySync does not run change/delete detection on subsequent job runs, Delete Policy Ignore Both would not be applicable.