Aspera Watch Service Session Examples

Push Example

The asperawatchd service must first be properly configured and running on the local host to push files with asperawatchd. For more information about configuring and starting the Aspera WatchD service, see Starting the Aspera Watch Service.

To push files, start an Aspera Sync session with the --watchd datastore:host:port[:domain] option. For example:

async --watchd redis:localhost:31415:root -N watch_push -d /data/D1 -r adminuser@10.0.0.1:/data/R1   

Pull Example

The asperawatchd service must first be properly configured and running on the remote host to pull files with asperawatchd. For more information about configuring and starting the Aspera WatchD service, see Starting the Aspera Watch Service.

Aspera Sync uses the remote host'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 /data/D1 -r adminuser@10.0.0.1:/data/R11 -K pull

Bi-Directional Example

The asperawatchd service must first be properly configured and running on both the remote and local hosts to start a bi-directional session with asperawatchd. For more information about configuring and starting the Aspera WatchD service, see Starting the Aspera Watch Service.

To start a bi-directional session, start an Aspera Sync session with the --watchd datastore:host:port:domain option and the -K BIDI option. For example:

async --watchd redis:localhost:31415:root -N watch_session -d /data/D1 -r adminuser@10.0.0.1:/data/R11 -K BIDI

Remote from ascp Example

If you are using CIFS or NFS mounted storage, you must configure and run the asperawatchd service on the host running the NFS server, but neither the local host nor the remote host need to be configured.

On the NFS server, you must also set the Redis database to a non-loopback address by configuring Redis with a modified configuration file including the correct port and host address bindings. For example, if your host address is "10.54.44.194":

# Accept connections on the specified port, default is 6379.
# If port 0 is specified Redis will not listen on a TCP socket.
port 31415

# If you want you can bind a single interface, if the bind option is not
# specified all the interfaces will listen for incoming connections.
#
bind 10.54.44.194

Save your configuration file and then run the the asperaredisd service with the location of your configuration file.

# /opt/aspera/sbin/asperaredisd /filepath/redis_configuration.conf.

Point asperawatchd to the new Redis location by running the following command on your server:

# asconfigurator -x "set_node_data;watchfolderd_db_spec,redis:redis_host:redis_port:domain"

For example,

# asconfigurator -x "set_node_data;watchfolderd_db_spec,redis:10.54.44.194:31415:root"

Restart the asperawatchd service.

# /opt/aspera/bin/asperawatchd --user username

You can now start an Aspera Sync session from any client mounting NFS storage from that NFS server.

Important: The path of your mounted directory must match the path of the directory on the NFS server. For example, if the directory is found at /data/D1 on the NFS server, you must mount it at /data/D1.

Start an Aspera Sync session with the local directory (-d) pointing to the mounted storage and the --watchd option pointing to the remote Redis monitored by asperawatchd. For example:

async --watchd redis:10.54.44.194:31415 -N watch_remote -d /data/D1 -r adminuser@10.0.0.1:/data/R11 -K BIDI

In this example, the client on Host A starts the Aspera Sync session. The asperawatchd service on Host B (10.54.44.194) scans the /data/D1 directory mounted by Host A and passes the snapshot to Sync. Sync transfers the relevant files from the mounted storage to the target directory remote Host C (10.0.0.1). In this example, only Host B needs to be configured for asperawatchd.

Note: These examples are all one-time sessions, but you can run any of these sessions in continuous mode (if the source machine is Windows or Linux) by using the -C option. In continuous mode, any changes you make to a monitored directory are detected by asperawatchd. Changes are propagated through Aspera Sync.