Aspera upgrades file sync and console platforms

Michelle Clancy | 20-02-2013

Aspera has upgraded its high performance content and big-file synchronisation and replication technologies, Aspera Sync 1.4 and Aspera Console 1.7, aimed at big data file stores — from millions of individual files to very large file sizes.
Aspera Sync for asynchronous file replication and synchronisation uses Aspera fasp high speed transport and a fast snapshot technology, for common enterprise-class use cases such as offsite replication for disaster recovery, content distribution and collection, file archiving and storage, and full system migration.
The latest release also includes full integration with Aspera Console 1.7 for global visibility into Sync sessions and activity across the entire network, providing real-time reports on synchronisation progress, per file status and throughput. Sync sessions can be paused and resumed, and bandwidth priority and speed can be modified on the fly from the centralised Console Web interface.
In terms of file handling, Sync offers support for soft and hard links, options for the preservation of access time, user and group IDs, and support for configurable user and group ID for the target system. It also supports Mac OSX and Solaris, in addition to Windows and Linux.
The latest version of Aspera Console, meanwhile, centrally manages all Aspera transfers across cloud, on-premise and hybrid deployments. It features integration with Active Directory to enable single sign-on for Active Directory groups and users, creating a more unified and consolidated security environment within enterprises.
Operators can also configure the Transporter host as an Aspera transfer node so that its transfers can be monitored and managed from Console, and it has a capability for auditing users' activity, including logins and logouts, failed login attempts, session timeouts and concurrent logins.
Also, Console's collection of pre-defined report templates has been expanded to include additional reports for bandwidth usage by user, node and peak usage.