Migrating Watch Services on Upgrade

As of Enterprise Server version 3.7.1, Aspera Watches and Watchfolders are managed by the Aspera Watch Service Manager (asperarund), which allows easy management of the asperawatchfolderd and asperawatchd services. Most importantly, asperarund allows admins to start services under different users without having to switch between the different contexts.

If you upgraded from Enterprise Server version 3.6.1, and you had the asperawatchd and asperawatchfolderd services enabled and configured, you must manually migrate any services that are run by a user other than svcAspera.

Scenario 1: User is "svcAspera"

If the user is svcAspera, the installer first stops the asperawatchd and asperawatchfolderd services and removes them from running services. The installer restarts the services using the following command:

> asperawatchd --user svcAspera
> asperawachfolderd --user svcAspera

Windows requires a password when running services as other users. Enter the password when prompted.

Due to the new deployment model, users running asperawatchd and asperawatchfolderd services must have a docroot set in aspera.conf. If you didn't have a docroot set for your user, see Updating the Docroot of a Running asperawatchfolderd Service.

Scenario 2: User is Not "svcAspera"

If the user is not svcAspera, the installer does not automatically migrate the services. You must manually start the service under the user that was running the asperawatchd and asperawatchfolderd services. Before you perform the migration steps, confirm or set the following for the user running the services:

You can set the docroot with the following asconfigurator command:

> asconfigurator -x "set_user_data;user_name,username;absolute,docroot"
Note: URI docroots (for example, paths to cloud storage or file://path) are not currently supported by asperawatchd and asperawatchfolderd. Only local file systems can be monitored.

The asconfigurator command adds the following configuration to the <aaa> section of aspera.conf (in this example, the docroot is set to C:\):

You can find the aspera.conf configuration file at:

C:\Program Files (x86)\Aspera\Enterprise Server\etc\aspera.conf

Validate the aspera.conf file using the asuserdata utility:
> asuserdata -v

After setting the docroot and ensuring the user has write permissions to the log directory, start the services with the following commands:

> asperawatchd --user username
> asperawatchfolderd --user username

Windows requires a password when running services as other users. Enter the password when prompted. This command starts the services running under the designated user.

Creating and Managing Watch Folders

You can use the following tools to create and manage watch folders: