Monitor transfers

Edit online

You can review your attempted and completed transfers and monitor your active, in-progress transfers using the transfer monitor. This in-app monitor reflects the transfer activity that you perform using the Aspera on Cloud app, including transfers that use the IBM Aspera Connect transfer client; the IBM Aspera HTTP Gateway; and direct node-to-node FASP transfers. To view transfer activity and usage for the entire organization, use the Aspera on Cloud Activity app.

Transfer monitor

To open the transfer monitor, click the Transfers icon . You can filter the list of transfers by activity type (all, upload, download) or by transfer status (all, failed, stopped, running).

Note these aspects of the transfer monitor:

  • For each transfer:
    • Label indicates whether the transfer occurred in the Packages app or in the Files app
    • Main label indicates package name (for transfers in the Packages app) or file/folder path/name (for transfers in the Files app)
    • Check mark indicates successful completion
    • Progress bar indicates active, in-progress transfer
    • "x" icon indicates failed transfer
    • Statistics labels indicate transfer size and date, transfer status (Downloaded, Uploaded , Error, Stopped, InProgress)
    • Access the activity modal by clicking the information icon. You can adjust the target rate of desktop transfers that were started using the Aspera clients. This modal displays real-time insights including transfer rate, percent completion, and more.
    • Click View local folder to jump to the finder/explorer location of the content on the local machine or remote storage
    • Location path displays near transfer statistics
  • For active transfers:
    • Click the Pause or Play icon to the right to pause or resume the transfer
    • Text labels indicate transfer progress, rate, and items remaining
    • Animated progress bar indicates transfer progress

Entries in the transfer monitor

Note that a single user transfer operation may generate multiple transfer entries in the transfer monitor.

For example, suppose a single package contains content from multiple sources. Content from a local or remote source is a separate transfer from content that already resides on an Aspera transfer server. In this case, it is possible for one transfer to succeed and another to fail, even though both transfers are initiated from sending a single package.

What starts a transfer?

Aspera on Cloud initiates a transfer when you perform any of the following actions:

  • Upload content into your Files app
  • Download content from your Files app
  • Move content from one location in your Files app to another
  • Save content from a package to a location in your Files app
  • Send a digital package in the Packages app
  • Send a package to a shared inbox
  • Download content from a package (including a shared inbox submission)

In addition, Aspera on Cloud also initiates a transfer during these operations:

  • When an outside user sends you content
  • When an outside user submits content to a shared inbox
  • When an outside user you've shared content with downloads it
  • When an outside user you've sent content to downloads it