...

...

...

...

...

...

Disclaimer

Your use of this download is governed by Stonebranch’s Terms of Use, which are available at https://www.stonebranch.com/integration-hub/Terms-and-Privacy/Terms-of-Use/

Overview

The Inter-Cloud Data Transfer integration allows you to transfer data to, from, and between any of the major private and public cloud providers like AWS, Google Cloud, and Microsoft Azure.

...

• AWS S3
• Google Cloud
• Sharepoint
• Dropbox
• OneDrive
• Hadoop Distributed File Storage (HDFS)

Software Requirements

Software Requirements for Universal Agent

• Universal Agent for Linux or Windows Version 7.2.0.0 or later is required.

• Universal Agent needs to be installed with python option (--python yes).

Software Requirements for Universal Controller

• Universal Controller 7.2.0.0 or later.

Software Requirements for the Application to be Scheduled

• Rclone: v1.58.1 or higher needs to be installed on server where the Universal Agent is installed.

• Rclone can be installed on Windows and Linux

• To install Rclone on Linux systems, run:

  Code Block
  language py linenumbers true
  curl https://rclone.org/install.sh | sudo bash

  
  

  Note
  title Note
  If the URL is not reachable from your server, the Linux installation also can be done from pre-compiled binary.

  
  

• To install Rclone on Linux system from a pre-compiled binary:

  Fetch and unpack

  Code Block
  language py linenumbers true
  curl -O <https://downloads.rclone.org/rclone-current-linux-amd64.zip> unzip rclone-current-linux-amd64.zip cd rclone-*-linux-amd64

  Copy binary file

  Code Block
  language py linenumbers true
  sudo cp rclone /usr/bin/ sudo chown root:root /usr/bin/rclone sudo chmod 755 /usr/bin/rclone

  Install manpage

  Code Block
  language py linenumbers true
  sudo mkdir -p /usr/local/share/man/man1 sudo cp rclone.1 /usr/local/share/man/man1/ sudo mandb

  
  

• To install Rclone on Windows systems:

  • Rclone is a Go program and comes as a single binary file.

  • Download the relevant binary here.

  • Extract the rclone or rclone.exe binary from the archive into a folder, which is in the windows path

Key Features

Some details about the Inter-Cloud Data Transfer Task:

• Transfer data to, from, and between any cloud provider

• Transfer between any major storage applications like SharePoint or Dropbox

• Transfer data to and from a Hadoop File System (HDFS)

• Download a URL's content and copy it to the destination without saving it in temporary storage

• Data is streamed from one object store to another (no intermediate storage)
• Horizontal scalable by allowing multiple parallel file transfers up to the number of cores in the machine
• Supports Chunking - Larger files can be divided into multiple chunks

• Preserves always timestamps and verifies checksums

• Supports encryption, caching, and compression

• Perform Dry-runs

• Dynamic Token updates for SharePoint connections

• Regular Expression based include/exclude filter rules

• Supported actions are:

  • List objects

  • List directory

  • Copy / Move

  • Copy To / Move To

  • Sync Folders

  • Remove object / object store

  • Perform Dry-runs

  • Monitor object, including triggering of Tasks and Workflows

  • Copy URL

Import Inter-Cloud Data Transfer Universal Template

To use this downloadable Universal Template, you first must perform the following steps:

1. This Universal Task requires the Resolvable Credentials feature. Check that the Resolvable Credentials Permitted system property has been set to true.
2. Download the provided ZIP file (for example, from the Stonebranch Integration hub).
3. In the Universal Controller UI, select Configuration > Universal Templates to display the current list of Universal Templates.
4. Click Import Template.

5. Select the template ZIP file and Import..

...

1. To import the Universal Template into your Controller, follow the instructions here.
2. When the files have been imported successfully, refresh the Universal Templates list; the Universal Template will appear on the list.

...

Configure Inter-Cloud Data Transfer Universal Tasks

To configure a new Inter-Cloud Data Transfer there are two steps required:

1. Configure the connection file.

2. Create a new Inter-Cloud Data Transfer Task.

Anchor
Configure the Connection File Configure the Connection File

Configure the Connection File

The connection file contains all required Parameters and Credentials to connect to the Source and Target Cloud Storage System.

...

The following connection file must be saved in the Universal Controller script library. This file is later referenced in the different Inter-Cloud Data Transfer tasks.

connections.conf (v4)

# Script Name: connectionv4.conf
# 
# Description: 
# Connection Script file for Inter-Cloud Data Transfer Task
# 
#
# 09.03.2022   Version 1   Initial Version requires UA 7.2
# 09.03.2022   Version 2   SFTP support
# 27.04.2022   Version 3   Azure target mistake corrected
# 13.05.2022   Version 4   Copy_Url added

#

[amazon_s3_target]
type = s3
provider = AWS
env_auth = false
access_key_id = ${_credentialUser('${ops_var_target_credential}')}
secret_access_key = ${_credentialPwd('${ops_var_target_credential}')}
region = us-east-2
acl = bucket-owner-full-control


[amazon_s3_source]
type = s3
provider = AWS
env_auth = false
access_key_id = ${_credentialUser('${ops_var_source_credential}')}
secret_access_key = ${_credentialPwd('${ops_var_source_credential}')}
region = us-east-2
acl = bucket-owner-full-control
role_arn = arn:aws:iam::552436975963:role/SB-AWS-FULLX


[microsoft_azure_blob_storage_sas_source]
type = azureblob
sas_url = ${_credentialPwd('${ops_var_source_credential}')}


[microsoft_azure_blob_storage_sas_target]
type = azureblob
sas_url = ${_credentialPwd('${ops_var_target_credential}')}


[microsoft_azure_blob_storage_source]
type = azureblob
account = ${_credentialUser('${ops_var_source_credential}')}
key = ${_credentialPwd('${ops_var_source_credential}')}


[microsoft_azure_blob_storage_target]
type = azureblob
account = ${_credentialUser('${ops_var_target_credential}')}
key = ${_credentialPwd('${ops_var_target_credential}')}


[datalakegen2_storage_source]
type = azureblob
account = ${_credentialUser('${ops_var_source_credential}')}
key = ${_credentialPwd('${ops_var_source_credential}')}


[datalakegen2_storage_target]
type = azureblob
account = ${_credentialUser('${ops_var_target_credential}')}
key = ${_credentialPwd('${ops_var_target_credential}')}


[datalakegen2_storage_sp_source]
type = azureblob
account = ${_credentialUser('${ops_var_source_credential}')}
service_principal_file = ${_scriptPath('azure-principal.json')} 
# service_principal_file = C:\virtual_machines\Setup\SoftwareKeys\Azure\azure-principal.json


[datalakegen2_storage_sp_target]
type = azureblob
account = ${_credentialUser('${ops_var_target_credential}')}
service_principal_file = ${_scriptPath('azure-principal.json')} 
# service_principal_file = C:\virtual_machines\Setup\SoftwareKeys\Azure\azure-principal.json


[google_cloud_storage_source]
type = google cloud storage
service_account_file = ${_credentialPwd('${ops_var_source_credential}')}
object_acl = bucketOwnerFullControl
project_number = clagcs
location = europe-west3


[google_cloud_storage_target]
type = google cloud storage
service_account_file = ${_credentialPwd('${ops_var_target_credential}')}
object_acl = bucketOwnerFullControl
project_number = clagcs
location = europe-west3


[onedrive_source]
type = onedrive
token = ${_credentialToken('${ops_var_source_credential}')}
drive_id = ${_credentialUser('${ops_var_source_credential}')}
drive_type = business
update_credential = token


[onedrive_target]
type = onedrive
token = ${_credentialToken('${ops_var_target_credential}')}
drive_id = ${_credentialUser('${ops_var_target_credential}')}
drive_type = business
update_credential = token


[hdfs_source]
type = hdfs
namenode = 172.18.0.2:8020
username = maria_dev


[hdfs_target]
type = hdfs
namenode = 172.18.0.2:8020
username = maria_dev


[linux_source]
type = local


[linux_target]
type = local


[windows_source]
type = local


[windows_target]
type = local


[sftp_source]
type = sftp
host = 3.19.76.58
user = ubuntu
pass = ${_credentialToken('${ops_var_source_credential}')}


[sftp_target]
type = sftp
host = 3.19.76.58
user = ubuntu
pass = ${_credentialToken('${ops_var_target_credential}')}


[copy_url]

connection.conf in the Universal Controller script library

Image RemovedImage Added

Considerations

Rclone supports connections to almost any storage system on the market:

...

Create an Inter-Cloud Data Transfer Task

For Universal Task Inter-Cloud Data Transfer, create a new task and enter the task-specific Details that were created in the Universal Template.

The following Actions are supported:

...

In the following for each task action, the fields will be described and an example is provided.

Important Considerations

1. Before running a move, moveto, copy, copyto or sync command, you can always try the command by setting the Dry-run option in the Task.

2. The field max-depth (recursion depth) limits the recursion depth. max-depth 1means that only the current directory is in scope. This is the default value.
   
   

   Note
   title Attention
   If you change max-depth to a value greater than 1, a recursive action is performed. This should be considered in any Copy, Move, sync, remove-object and remove-object-store operations.

   
   

Inter-Cloud Data Transfer Actions

Action: list directory

Example

The following example list all aws s3 buckets in the AWS account configured in the connection.conf file.

No sub-directories are displayed, because max-depth is set to 1.

Image RemovedImage Added

Action: copy

Before running a move, moveto, copy, copyto or sync command, you can always try the command by setting the Dry-run option in the Task.

Example

The following example copies all file starting with report4 from the amazon s3 bucket stonebranchpm folder in to the Azure container: stonebranchpm.

No recursive copy will be done, because the flag --max-depth 1 is set.

Image RemovedImage Added

Action: copyto

The Action copyto copies a single object from source to target and allows you to rename the object on the target.

Before running a move, moveto, copy, copyto, or sync command, you can always try the command by setting the Dry-run option in the Task.

Example

The following example copies the file report4.txt from the amazon s3 bucket stonebranchpm folder in to the azure container stonebranchpm.

The file will be renamed at the target to: stonebranchpm/report4_${_date('yyyy-MM-dd_HH-mm-ss')}.txt; for example report4_2022-05-16_08-00-29.txt

Image RemovedImage Added

Action: list objects

Example

The following example lists all objects starting with report in the S3 bucket stonebranchpm.

Image RemovedImage Added

Action: move

Example

The following example moves the objects matching report[3-6].txt from the Windows source directory C:\demo\out to the target Azure container stonebranchpm.

...

No recursive copy will be done, because max-depth is set to 1.

Image RemovedImage Added

Action: moveto

The Action moveto, moves a single object from source to target and allows to rename the object on the target.

Before running a move, moveto, copy, copyto, or sync command, you can always try the command by setting the Dry-run option in the Task.

Example

The following example moves the file report4.txt from the amazon s3 bucket stonebranchpm folder in to the azure container stonebranchpm.

The file will be renamed at the target to: stonebranchpm/report4_${_date('yyyy-MM-dd_HH-mm-ss')}.txt; for example, report4_2022-05-16_08-00-29.txt

Image RemovedImage Added

Action: sync

Before running a move, moveto, copy, copyto, or sync command, you can always try the command by setting the Dry-run option in the Task.

Example

The following example synchroizes all files and folders from the Linux source: /home/stonebranch/demo/sync to the target SharePoint folder DemoSharePoint.

One Level of subfolders and files in the directory /home/stonebranch/demo/sync will be considered for the sync ation, because max-depth is set to 2. max-depth 2 means that the current folder plus one subfolder level is synced from the source to the target.

Image RemovedImage Added

Action: remove-object

Example

The following example removes all s3 objects starting with report* from the Azure container sbdatalake folder reports.

If the folder reports would contain a subfolder with an object starting with report, then that object would also be deleted, because max-depth is set to 2. max-depth 2 means that the current folder plus one subfolder level is in scope for the remove-object action.

Image RemovedImage Added

Action: remove-object-store

Example

The following example removes the Azure container demostonebranch.

The container must be empty in order to remove it.

Image RemovedImage Added

Action: create-object-store

Example

The following example creates the Azure container demostonebranch.

Image RemovedImage Added

Action: copy-url

  -a, --auto-filename    Get the file name from the URL and use it for destination file path
  -h, --help             help for copyurl
      --no-clobber       Prevent overwriting file with same name
  -p, --print-filename   Print the resulting name from --auto-filename
      --stdout           Write the output to stdout rather than a file

Example

The following example downloads a PDF file:

...

The Linux folder is located on the server where the Agent ${AGT_LINUX} runs.

Image RemovedImage Added

Action: monitor-object

Example

The following example monitors the Azure Datalake Gen2 storage container sbdatalake folder /reports/ for all object matching report[1-4].txt ( report1.txt, report2.txt, report3.txt, report4.txt).

...

If the monitor has launched the Task Load Seller Data to SAP , it will only launch a new Task “Load Seller Data to SAP” if the launched Tasks is not active anymore.

Image Removed

Inter-Cloud Data Transfer Example Cases

The following section provides examples for the Inter-Cloud Data Transfer Task actions:

• Copy

• Move

• Remove-object

• Monitor-object

...

N#

...

Name

...

Copy

...

C1

...

Copy a file to target. The file does not exist at the target.

...

C2

...

Copy two files. One of files already exists at the target.

...

C3

...

Copy a file to a target with Parameter ignore-existing set. A file with the same filename exists on the target.

...

C4

...

Copy a file to a target, which already exists with Parameter error-on-no-transfer set.

...

C5

...

Copy all files except one, from one folder into another folder.

...

C6

...

Copy non-recursively a file from a folder into another folder using the parameter max-depth 1.

...

C7

...

Copy files using multiple Parameters.

...

Move

...

M1

...

Move without deleting if no transfer took place.

...

M2

...

Move a file with same source and target - config error case.

...

Remove-object

...

R1

...

Delete a file in a specific folder by using the parameter: max-depth 1.

...

R2

...

Delete all files matching a given name recursively in all folders starting from a given entry folder.

...

Monitor-object

...

FM01

...

Monitor a file in AWS - file does not exist on start of monitor.

...

FM02

...

Monitor a file in AWS - file exists on start of monitor.

Copy

The following file transfer examples will be described for the Copy action:

...

N#

...

Name

...

C1

...

Copy a file to target. The file does not exist at the target.

...

C2

...

Copy two files. One of files already exists at the target.

...

C3

...

Copy a file to a target with Parameter ignore-existing set. A file with the same filename exists on the target.

...

C4

...

Copy a file to a target, which already exists with Parameter error-on-no-transfer set.

...

C5

...

Copy all files except one, from one folder into another folder.

...

C6

...

Copy non-recursively a file from a folder into another folder using the parameter max-depth 1.

...

C7

...

Copy files using multiple Parameters.

Copy a File to Target: File does not Exist at the Target

Copy the file report1.txt to target stonebranchpm/in/. The file does not exist at the target.

Configuration

• Source Storage Type: linux_source

• Source: /home/stonebranch/demo/out/

• Target Storage Type: amazon_s3_target

• Target: stonebranchpm/in/

• Filter Type: include

• Filter: report3.txt

• Other Parameters: none

Image Removed

Result

• Task Status: success

• Output: report1.txt: Copied (new)
  

Copy Two Files:. One File Already Exists at the Target

Copy two files report2.txt and report3.txt to the target stonebranchpm/in/. The file report2.txt (same size and content) already exists at the target.

Configuration

• Source Storage Type: linux_source

• Source: /home/stonebranch/demo/out/

• Target Storage Type: amazon_s3_target

• Target: stonebranchpm/in/

• Filter Type: include

• Filter: report[2-3].txt

• Other Parameters: none

Image Removed

Result

• Task Status: success

• Output:

  • report3.txt: Copied (new)

  • report2.txt: Unchanged skipping

Copy a File to a Target with Parameter ignore-existing Set. A File with the Same filename Exists on the Target.

Copy a file report2.txt to the target stonebranchpm/in/ with Parameter ignore-existing set . A file with the same filename exists at the target (size or content can be the same or different).

When ignore-existing is set, all files that exist on destination with the same filename are skipped. (No overwrite is done.)

Configuration

• Source Storage Type: linux_source

• Source: /home/stonebranch/demo/out/

• Target Storage Type: amazon_s3_target

• Target: stonebranchpm/in/

• Filter Type: include

• Filter: report2.txt

• Other Parameters: --ignore-existing

Image Removed

Result

• Task Status: failure

• Output:

  • There was nothing to transfer.

  • Exiting due to ERROR(s).

Copy a File to a Target, which Already Exists with Parameter Flag error-on-no-transfer Set.

Copy a file report2.txt to a target, which already exists with Parameter error-on-no-transfer set .

When error-on-no-transfer is set, the task will fail in case no file is transferred.

Configuration

• Source Storage Type: linux_source

• Source: /home/stonebranch/demo/out/

• Target Storage Type: amazon_s3_target

• Target: stonebranchpm/in/

• Filter Type: include

• Filter: report2.txt

• Other Parameters: --error-on-no-transfer

Image Removed

Result

...

Task Status: failure

Output:

report2.txt: Unchanged skipping

...

There was nothing to transfer

...

Exiting due to ERROR(s).

Copy all Files except One, from One Folder into Another Folder

Copy contents of folder in into folder out excluding the file index.html.

Configuration

• Source Storage Type: linux_source

• Source: stonebranchpmtest/in

• Target Storage Type: amazon_s3_target

• Target: stonebranchpmtest/out

• Filter Type: exclude

• Filter: index.html

• Other Parameters: none

stonebranchpmtest

├── in

│   ├── report1.txt

│   └── report2.txt

│   ├── sub01

│        ├── report1.txt <- this file will be copied incl. directory sub01

│   └── index.html <- will not be copied, because of the exclude filter

 

├── out

│   └── report10.txt

 

After execution of the delete action:

├── out

│   ├── report1.txt

│   └── report2.txt

│   ├── sub01

│        ├── report1.txt <- this file will be copied incl. directory sub01

│   └── report10.txt

Image Removed

Result

• Task Status: success

• Output:

  • report1.txt: Copied (new)


  • report2.txt: Copied (new)
  • sub1/report1.txt: Copied (new)

Copy Non-Recursively a File from a Folder into Another Folder by Using the Parameter max-depth 1. 

Copy the file report1.txt from the folder stonebranchpmtest/in into folder stonebranchpmtest2/. The Parameter max-depth 1 is used to copy non-recursively.

• max-depth limits the recursion depth (default -1).

• max-depth 1 means only the current directory is in scope.

Configuration

• Source Storage Type: amazon_s3_source

• Source: stonebranchpmtest/in

• Target Storage Type: amazon_s3_target

• Target: stonebranchpmest2/out

• Filter Type: include

• Filter: report1.txt

• Other Parameters: --max-depth 1

stonebranchpmtest

├── in

│   ├── report1.txt <- this file will be copied

│   ├── report2.txt

│   ├── sub01

│        ├── report1.txt <- this file will not be copied, because of --max-depth 1

├── report1.txt <- this file will not be copied

 

stonebranchpmtest2

├── report10.txt

After execution of the delete action:

stonebranchpmtest2

├── report1.txt

├── report10.txt

Image Removed

Result

• Task Status: success

• Output: report1.txt: Copied (new)

Copy Files Using Multiple Parameters

It is possible to provide multiple Parameters in the Other Parameters field of the Task.

Example:

Parameters: --max-depth 1 --error-on-no-transfer

In this case, both Parameters are applied.

Configuration

• Source Storage Type: amazon_s3_source

• Source: stonebranchpmtest/in

• Target Storage Type: amazon_s3_target

• Target: stonebranchpmest2/out

• Filter Type: include

• Filter: report1.txt

• Other Parameters: --max-depth 1, --error-on-no-transfer

Image Removed

Result

The Parameters: --max-depth 1 and --error-on-no-transfer are both applied.

Move

The following file transfer examples will be described for the Move action:

...

N#

...

Name

...

M1

...

Move without deleting if no transfer took place.

...

M2

...

Move a file with same source and target - config error case.

Move Without Deleting if no Transfer Took Place

If you want only the source file to be deleted when a file transfer took place, then add the flag ignore-existing in the field Other Parameters

Example: You move a file to a destination that already exists. In this case, rclone will not perform the copy but deletes the source file.

If you set the flag --ignore-existing, the delete operation will not be performed.

Configuration

• Source Storage Type: linux_source

• Source: /home/stonebranch/demo/out/

• Target Storage Type: amazon_s3_target

• Target: stonebranchpm/in/

• Filter Type: include

• Filter: report4.txt

• Other Parameters: --ignore-existing, --max-depth 1, --error-on-no-transfer

Image Removed

Result

• Task Status: failed

  • The file report4.txt is not deleted at the source “/home/stonebranch/demo/out/”

• Output:

  • There was nothin to transfer


  • Return Code: 9
  • Exiting due to ERROR(s).

Move a File with Same Source and Target - config error Case

Accidently, the source has been configured the same as the target.

The --ignore-existing parameter avoids that a file is deleted, if the source is equal to the destination in a copy operation.

• The --ignore-existing parameter avoids that a file is deleted, if the source is equal to the destination in a copy operation.

• The max-depth 1 parameter avoids a recursive move of files.

Configuration

• Source Storage Type: linux_source

• Source: /home/stonebranch/demo/out/

• Target Storage Type: linux_source

• Target: /home/stonebranch/demo/out/

• Filter Type: include

• Filter: report4.txt

• Other Parameters: --ignore-existing, --max-depth 1

Image Removed

Result

• Task Status: success (because --error-on-no-transfer was not set)

  • The file report4.txt is not deleted.

• Output:

  • There was nothin to transfer


  • Return Code: 0

Remove-object

The following file examples will be described for the Remove-object action:

...

N#

...

Name

...

R1

...

Delete a file in a specific folder by using the parameter max-depth 1.

...

R2

...

Delete all files matching a given name recursively in all folders starting from a given entry folder.

Delete a File in a Specific Folder by Using the Parameter max-depth 1

Delete only the report1.txt in the folder stonebranchpmtest/in/

To delete a specific file in a folder, provide the File Path to the file to delete and provide the Parameter: --max-depth 1 in the Other Parameters field.

• max-depth limits the recursion depth (default -1).

• max-depth 1 means only the current directory is in scope.

Configuration

• File Path: stonebranchpmtest/in/

• Storage Type: amazon_s3_source

• Filter Type: include

• Filter: report1.txt

• Other Parameters: --max-depth 1

stonebranchpmtest

├── in

│   ├── report1.txt <- this file will be deleted

│   ├── report2.txt

│   ├── sub01

│        ├── report1.txt <- this file will not be deleted because of --max-depth 1

├── report1.txt

 

After execution of the delete action:

stonebranchpmtest

├── in

│   ├── report2.txt

│   ├── sub01

│        ├── report1.txt

├── report1.txt

Image Removed

Result

• Task Status: success

• Output: report1.txt Deleted


Delete all Files Matching a Given Name Recursively in all Folders Starting from a Given Entry Folder

Delete report1.txt recursively in all folders starting from the given entry folder stonebranchpmtest/ will be deleted.

Configuration

• File Path: stonebranchpmtest/

• Storage Type: amazon_s3_source

• Filter Type: include

• Filter: report1.txt

• Other Parameters: none

stonebranchpmtest

├── in

│   ├── report1.txt <- this file will be deleted

│   ├── report2.txt

│   ├── sub01

│        ├── report1.txt <- this file be deleted

├── report1.txt <- this file be deleted

 

After execution of the delete action:

stonebranchpmtest

├── in

│   ├── report2.txt

│   ├── sub01

│        ├──

├──

Image Removed

Result

• Task Status: success

• Output:

  • in/report1.txt Deleted

  • in/sub1/report1.txt Deleted
  • report1.txt Deleted

Monitor-object

The following examples describe how file monitoring can be performed.

...

N#

...

Name

...

FM01

...

Monitor a file in AWS - file does not exist on start of monitor.

...

FM02

...

Monitor a file in AWS - file exists on start of monitor.

Monitor a File in AWS - File does not Exist on Start of Monitor

With the Parameter Flag --use-server-modtime, you can tell the Monitor to use the upload time to the AWS bucket instead of the last modification time of the file on the source (for exxample, Linux).

max-depth 1 means only the current directory is in scope.

Configuration

• Directory: stonebranchpmtest/in/

• Storage Type: amazon_s3_source

• Filter Type: include

• Filter: test3.txt

• Interval: 10s

• Trigger on Existence: no

• Other Parameters: --max-depth 1, --use-server-modtime

Image Removed

Result

• Task Status: running

• The monitor will stay in running until the file test3.txt is copied to stonebranchpmtest/in

• Output:

  • INFO - REST SB library version 1.0

  • INFO - ############  Monitor Objects Action ###############

  • INFO - ############  List Objects Action ###############

  • INFO - sleeping for 10 seconds now

Monitor a File in AWS - File Exists on Start of Monitor

With the Parameter Flag --use-server-modtime,  you can tell the Monitor to use the upload time to the AWS bucket instead of the last modification time of the file on the source (for example, Linux).

max-depth 1 means only the current directory is in scope.

Configuration

• Source Storage Type: linux_source

• Source: /home/stonebranch/demo/out/

• Target Storage Type: amazon_s3_target

• Target: stonebranchpm/in/

• Filter Type: include

• Filter: report10.txt

• Trigger on Existence: yes

• Other Parameters: --ignore-existing, --max-depth 1, --error-on-no-transfer

Image Removed

Result

...

Task Status: success

...

The task goes to success because the file report10.txt already exists in stonebranchpmtest/in ( trigger on existence is set to true ).

Output:

...

######  object in stonebranchpmtest/in/ ######

...

[{"Path":"report10.txt","Name":"report10.txt","Size":15,"MimeType":"text/plain","ModTime":"2021-12-08T16:26:18.000000000Z","IsDir":false,"Tier":"STANDARD"}]

...

Image Added