Monitoring and Tracking

Administrators can view the progress and performance of all active Aspera transfer sessions on each managed node, including file details, number of bytes transferred, transfer speed, and any errors. A graphical bandwidth monitor in the browser shows the bandwidth used by each transfer session, and the aggregate bandwidth of
all Aspera transfers on a node or across a group (”cluster”) of nodes.

Transfer activity reports summarize the total data transferred, with detailed per-job drill-down views, over the past day, week, month, or custom date range. Search and filter functions allow the operator to build custom reports for transfer activity by date, user or client IP.

Bandwidth Regulation and Prioritization

Administrators can pause, resume, or change the speed or bandwidth sharing policy of individual transfers. In addition, with Aspera's new aggregate bandwidth management capability, Administrators can set aggregate bandwidth caps that gracefully regulate the total bandwidth used by all Aspera transfers on a server or cluster of servers.

For example, a content provider hosting an Aspera server on a 1Gbps connection can assign a bandwidth cap of 500 Mbps, and be assured that as Aspera transfer bandwidth demand approaches 500 Mbps, the transfers will gracefully slow down, each taking only a fair share and remaining stable, even for a very large number of concurrent transfers. As transfer demand subsides, ongoing transfers will naturally speed up for full bandwidth utilization, but within the configured cap.

Automation

Administrators can browse managed Aspera nodes to select files and directories to transfer, and set up one-time or periodic, scheduled transfer jobs. In addition to simple one-to-one transfers, Aspera will be adding support for several more complex job types:
• Multi-endpoint push transfers in which the same file set is sent to a number or receivers.
• One-way replication and bi-directional synchronization of directories between nodes.
• Pipelined transfers in which an Aspera transfer from node A to B feeds a downstream transfer from B to C. With fasp, the downstream transfer can begin as early as possible and count on a steady, uninterrupted data flow.

Custom actions to be done post-transfer such as email notification and operations on the transferred file set – delete, move, rename – can be attached to the automated job.