Page Comparison

...

align	center

...

On This Page

Table of Contents

Overview

When a delete is detected on either the source or the destination, the Delete Policy determines how SkySync will behave.

Mirror the Deletion When Items are Deleted from Source

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.

...

Based on the transfer type selected for the job, you can expected the following behavior for Delete Policy Mirror.

Transfer Direction	Behavior
Synchronize	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.
Copy	When a delete is detected on the source, the application 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 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 not run change/delete detection on subsequent job runs, Delete Policy Mirror would not be applicable.

Ignore Items Deleted from 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. This is the default Delete Policy for Copy jobs.

...

Based on the transfer type selected for the job, you can expected the following behavior for Delete Policy Ignore Source.

Transfer Direction	Behavior
Synchronize	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 still occur.
Copy	This is the default Delete Policy for Copy jobs. When a delete is detected on the source, the application 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 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 not run change/delete detection on subsequent job runs, Delete Policy Ignore Source would not be applicable.

Ignore Items Deleted from 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.

...

Based on the transfer type selected for the job, you can expected the following behavior for Delete Policy Ignore Destination.

Transfer Direction	Behavior
Synchronize	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 still occur.
Copy	Delete Policy Ignore Destination is not applicable. With transfer type Copy, the application 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 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 not run change/delete detection on subsequent job runs, Delete Policy Ignore Destination would not be applicable.

Ignore Items Deleted from Both Source and Destination

When a delete is detected on either the Source or the Destination, the application will ignore and take no action. Ignore Both is the system default Delete Policy.

...

Based on the transfer type selected for the job, you can expected the following behavior for Delete Policy Ignore Both.

Transfer Direction	Behavior
Synchronize	When a delete is detected on either the source or the destination, the application will ignore and take 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 Delete Policy Ignore Both is not be applicable. The default Delete Policy for copy jobs is Ignore items deleted from the source.
Migrate	Delete Policy Ignore Both is not applicable. With transfer type Migrate, the application does not run change/delete detection on subsequent job runs, so Delete Policy Ignore Both is not 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, the application does not run change/delete detection on subsequent job runs, Delete Policy Ignore Both would not be applicable.

...

Delete Policy Using REST API

Configuration options available in using the REST API correspond directly with the user interface options.

REST API Setting	UI Setting
ignore_both (This is the default option.)	Ignore items deleted from both Source and Destination
ignore_source	Ignore items deleted from Source
ignore_destination	Ignore items deleted from Destination
mirror	Mirror the deletion when items are deleted from Source

POST {{url}}v1/jobs

Code Block

{
  "name":"Test Delete Policy",
  "kind": "transfer",
  "transfer": {
      "audit_level": "error",
      "transfer_type": "copy",
      "delete_propagation": "ignore_source",
      "source": {
        "connection": { "id": "{{cloud_connection_source}}" },
        "target":
        {"path":"/SourcePath"}
      },
      "destination": {
        "connection": { "id": "{{cloud_connection_destination}}" },
        "target": {
          "path": "/DestinationPath"
        }
      }
  },
  "schedule": {
    "mode": "manual"
  }
}

Versions Compared

Old Version 6

New Version 7

Key