Running async
Sync uses the async command line tool to
synchronize content from the source to the destination. async has many
options for customizing the behavior of the synchronization, and this section describes how
to compose an async session, the command line arguments, and examples for
specific use cases.
Composing an Async Session
Sync has more than 80 options that can be used when composing an async session, but only a few are required, and Aspera recommends using several others.
async Command Reference
An async session accepts the following options, some of which are required.
Examples of Async Commands and Output
Examples of common Sync use cases and a description of async output.
Using Filters to Include and Exclude Files
Filters refine the list of source files (or directories) to transfer by indicating which to skip or include based on name matching. When no filtering rules are specified by the client, Ascp transfers all source files in the transfer list; servers cannot filter client uploads or downloads.
Filtering Examples
Filtering examples that demonstrate the effects of adding more filter rules to the command and show how to format a filter rule file.
Bidirectional Example
Bidirectional synchronization syntax is similar to push or pull async sessions, as show in the following example.
Synchronizing with AWS S3 Storage
Sync can be used to synchronize files when the source or destination is AWS S3 Cloud Object Storage. Each endpoint (HSTS) of the async session must be configured to support Sync and the async must include certain file system-related options.
Sync with Basic Token Authorization
Aspera nodes that require access key authentication, such as IBM Aspera Transfer Cluster Manager or IBM Aspera on Cloud transfer service (AoCts ), can be used as synchronization endpoints by configuring the async database on the node and authenticating the async session with a basic token. A basic token requires a docroot on the server and allows access to all files in the docroot.