Differences between Storage Transfer Service options

This document summarizes the differences between Transfer service for on-premises data and Storage Transfer Service.

Feature Storage Transfer Service Transfer for on-premises Notes
Scheduling frequency Daily Every N hours, days, or weeks For more frequent Transfer for on-premises transfers, you can schedule several daily jobs at your desired frequency interval. For example, for 24 daily transfers, you'd schedule 24 different daily transfers that each start on the hour. That is, midnight, 1AM, 2AM and so forth.
Sync Full or incremental copy Incremental copies only The detection algorithm for changes in objects and files is identical for Storage Transfer Service and Transfer for on-premises. However, Transfer for on-premises always checks the delta between files in Google Cloud and on the on-premises machine. If files don't already exist, Transfer for on-premises performs a full copy. If you want to use Transfer for on-premises to perform a full copy for files already in Cloud Storage, then either delete the corresponding objects in the destination Cloud Storage bucket, or choose a new prefix for your destination objects.
Bandwidth control Not supported Supported—can set limits across all transfers in the project in MB/s increments
Google Cloud's operations suite monitoring Not supported Supported for agents only For Cloud-to-Google Cloud, you can poll the API to get the status, speed, and so forth of your transfer jobs. For more information, see TransferJobs API description.
Run now Not supported Supported In Cloud-to-Google Cloud transfers, to run an existing transfer now, you start by creating a new transfer job that uses identical settings as the existing transfer job, and starting it now.
Destination object prefix Not supported Supported—a fixed prefix can be prepended to all transferred destination objects in Cloud Storage.
Transfer logs Not supported Supported—you can view a record of all files copied and any errors. For errors in Cloud-to-Google Cloud transfers you can view the error samples in Google Cloud Console.
Name-based source data filtering Supported—include and exclude prefixes for source objects Not supported To specify a subset of files for an on-premises transfer, you create a separate staging directory with only the files you intend to transfer, and then start a transfer job with that directory as the source.
Modified-time source-data filtering Supported—include source files based on last modified time Not supported To specify a subset of files for an on-premises transfer, you create a separate staging directory with only the files you intend to transfer, and then start a transfer job with that directory as the source.
IAM
  • Storage Transfer Admin, Storage Transfer User, and Storage Transfer Viewer roles
  • Custom IAM permissions
Storage Transfer Admin and Storage Transfer User roles The Cloud Console for Storage Transfer Service will not work properly if the custom role is missing required permissions. For example, some parts of the Cloud Console assume the role has read access to display an item before editing it, so a role with only write permissions will experience Cloud Console screens that don't work.
Delete on transfer
  • Can delete source files transferred to destination.
  • Can delete destination files no longer in source.
Can delete destination files no longer in source.
API support Supported Not supported — can access through GUI only.
Customer-defined job IDs Supported — API users can specify their own job ID Not supported