Important: You must first configure and manually start the Aspera
Watch Service (asperawatchd) before starting an Aspera Sync session. To start the
asperawatchd service, go to
Start > Administrative Tools > Services.
Right-click
Aspera WatchD and select
Start.
For more information about configuring the Aspera WatchD service, see
Starting the Aspera Watch Service.
Push Example
The asperawatchd service must first be properly configured
and running on the client host to push files with asperawatchd. To push files, start an Aspera
Sync session with the
--watchd datastore:host:port option.
For
example:
async --watchd redis:localhost:31415 -N watch_push -d C:\data\D1 -r adminuser@10.0.0.1:d:\data\R1
Pull Example
The asperawatchd service must first be properly configured
and running on the server host to pull files with asperawatchd. Aspera Sync uses the server's
aspera.conf file to determine whether or not to use asperawatchd for the session. To pull
files, start an Aspera Sync session with the
-K pull option. For
example:
async -N watch_pull -d C:\data\D1 -r adminuser@10.0.0.1:d:\data\R11 -K pull
Bi-Directional Example
The asperawatchd service must first be properly
configured and running on both the server and client hosts to start a bi-directional session
with asperawatchd. To start a bi-directional session, start an Aspera Sync session with the
--watchd datastore:host:port option and the
-K
BIDI option. For
example:
async --watchd redis:localhost:31415 -N watch_session -d C:\data\D1 -r adminuser@10.0.0.1:d:\data\R11 -K BIDI
Note: These examples are all one-time sessions, but you can run any of these sessions in
continuous mode by appending -C. In continuous mode, any changes you make to a
monitored directory are detected by asperawatchd. Changes are propagated through Aspera
Sync.