To get started using this Web Service you must enable the local datastore.  This can be accomplished by setting the persistent_store configuration option to 'enable' in the configuration manager or you can edit the aspera.conf file directly. An example of this configuration is seen below.


<central_server>
  <persistent_store>enable</persistent_store></central_server>

Aspera Central stores data about the session and file transfer in the local datastore and uses this as a time-sensitive cache. You can customize the behavior by configuring the following options in the aspera.conf file (in the central_server tag).

Option Accepted Values Description
persistent_store enable | disable Enables or disables the recording of session and file transfer information in the persistent store. In order to increase performance, it is better to configure the local store on a different disk than the one usually used with FASP.
persistent_store_path see default datastore location The path where the datastore is created. The path can be absolute or relative to Central's base directory.
If the path points to an existing directory, the datastore is created in that directory with the name "central-store.db". Otherwise, the datastore will be created with the provided name, creating directories as necessary.
persistent_store_max_age Unlimited | [sec]  86400(24 hours) The maximum age of sessions and file transfers in the datastore. Older items are purged from the store periodically. Age is expressed in seconds from the end time of a session or transfer.
persistent_store_on_error exit | ignore Defines the behavior of Central when it fails to persist data in the datastore:
  • exit: the Central service quits. If configured accordingly, all running and new fasp transfers will fail subsequently.
  • ignore: Central continues, ignoring the error. Note that this leads to unrecoverable data loss!
event_buffer_capacity 1000 The number of events that can be buffered temporarily in memory. Increase in high-concurrency situations with many small file transfers.
event_buffer_overrun block | drop Defines the behavior when the buffer reaches its capacity:
  • block: blocks new notifications, possibly slowing down transfers.
  • drop: drops the notification; this may lead to unrecoverable data loss!
compact_on_startup enable | disable If enabled, the datastore is compacted upon startup of Central. This might take several seconds depending on the actual size of the datastore.

The datastore is normally stored in the following locations, depending on your system:

Windows

  • C:\Program Files\Aspera\Enterprise Server\var\central-store.db

Macintosh

  • /Library/Application Support/Aspera/Enterprise Server/var/central-store.db

Linux, FreeBSD, Isilon and Solaris

  • /opt/aspera/var/central-store.db

When running a high performance system or expecting a high quantity of small file transfers it is recommended to put the database on a separate disk that is fast. When expecting 500 to 100,000 sessions you should expect to need at least 29 MB of disk space, and when expecting 5,000 to 1,000,000 sessions you should expect 289 MB of disk space.  These numbers are just estimates and real world conditions will define how much space you need to allocate; a typical session uses around 400 bytes of disk space and a typical file transfer uses around 300 bytes.

It is recommended that you occasionally run VACUUM to help keep the database compact and avoid fragmentation.  When you frequently insert, update and delete items the data in the database becomes fragmented and is scattered across the database file.  To run VACUUM look in the option/configuration folder in your Central installation.  The VACUUM is automatically started at Central startup when the compact_on_startup parameter is enabled, you can also start it by using the command line --compact-db option when starting Central.

 

Video player

Video

×