Reference

Upload to Bucket

Uploads a file or folder from the server to a bucket, skipping what is already there.

Category
Action
Topics
Scheduler ยท Destinations
01

Ports

Upload to Bucketaction
  • triggercontrol
  • Sourcestring
  • Key prefixstring
  • onCompletecontrol
  • onFailedcontrol
  • Objects uploadednumber
  • Objects skippednumber
  • Bytes sentnumber
Ports Control Data
Data types string number bool

Strings accept any data input.
Numbers accept boolean input.

02

Fields

Field What it does Default Limits
Destination The saved bucket to upload to, chosen from the destinations in Settings. None Must name a saved destination that still exists.
Source (file or folder) The file or folder to upload, relative to the server folder or absolute. None Inside the server folder, its backups folder or its DH staging folder.
Key prefix Text added to every object key after the destination's own prefix. None No . or .. segments.
03

What a run does

  1. Resolves Source against the server folder and refuses anything outside the folders it may read.
  2. Lists the files: a folder is walked in name order, and a link to a folder is not entered.
  3. Refuses the whole upload, before sending anything, if one file is over 5 GiB.
  4. Checks each object in the bucket: one of the same size is skipped, anything else is sent.
  5. Stops at the first failure and keeps what was sent, so the next run resumes.

Each key is the destination's prefix, then Key prefix, then the file's path below Source.
A single file is stored under its file name.
Only the size is compared, so a file edited to the same length is not sent again.
A wired Source or Key prefix replaces its field.

It leaves by onComplete when every file is sent or skipped, and by onFailed on any error.
Objects uploaded, Objects skipped and Bytes sent are set after a successful run.
Progress and the result appear in the server's console.
The block can run for up to 12 hours.

04

Errors

Message says Do
destination validation failed: Upload to Bucket (node): the destination "name" does not exist. It was deleted or renamed in Settings, or this graph came from another install. Pick a destination that exists, or add it in Settings.
destination "name": reason Correct the destination in Settings.
key prefix "prefix" must not contain "segment" Remove the . or .. segment from the prefix.
source path does not exist Check the path of the source.
source path is outside the folders a graph may upload from (the server's folder and its backups) Choose a source in the server folder, its backups folder or its DH staging folder.
file is a link that is outside the folders a graph may upload from (the server's folder and its backups) Remove the link, or point it inside those folders.
source path holds no files to upload Choose a source that holds at least one file.
key is size, over the 5 GiB single upload limit, so nothing was uploaded; split it or leave it out of the folder: file is over the 5 GiB single upload limit Split the file or move it out of the folder.
object n of total: reason Run it again; objects already sent are skipped.
timed out after 43200s: reason Run it again; objects already sent are skipped.