Sync 1.5.3 Release Notes

Sync 1.5.3 Release Notes

Aspera Sync 1.5.3 Release Notes


Product Release: Apr 18, 2014

Release Notes Updated: Apr 18, 2014


Performance Enhancements

This release of Aspera Sync provides significant performance enhancements:

•         The 1.5 architecture minimizes the operations of the snapshot database, thereby allowing faster synchronization speed, especially on systems with slow storage.

•         The startup time for a synchronization update (a session working from an existing snapshot) is considerably faster than in previous releases.


If you run Sync 1.5.3 with a snapshot database generated by 1.4, it will automatically migrate the database to 1.5.3. No special action is required by users.

Note: Aspera Sync 1.5.3 cannot synchronize with endpoints running older versions of Sync. Any endpoints to be synced with 1.5.3 must also be upgraded to 1.5.3.

Aspera Sync 1.5.3 is available prepackaged with release 3.4.3 of Enterprise Server, Connect Server, and Point-to-Point, and it can also be downloaded separately from Aspera’s website.

Aspera Sync 1.5.3 is fully compatible with release 3.3 of Enterprise Server, Connect Server, and Point-to-Point.

New Features

This release of Aspera Sync 1.5.3 provides the following new features:

•         Support for Solaris.

•         Support for preserving Windows and OSX ACLs, even when syncing between Windows or OSX and an OS that does not support ACLs. In the latter case, ACL data can be preserved in a metafile and metafile data can be restored to native ACL format. The following async options are available for ACL preservation, where mode is the type of storage:


mode=nativemetafile, or none 


mode=nativemetafile, or none 


This feature is only meaningful if both hosts are in the same domain. If the user ID at the source does not exist at a destination, the sync proceeds but no ACL data is saved and the log records that the ACL could not be applied.

The default storage type is none. The default can be overridden with the aspera.conf setting<preserve_acls>. The default type and aspera.conf settings can be overridden with the command-line options.

•         Support for preserving OSX extended attributes (xattr), even when syncing between OSX and a file system that does not support OSX extended attributes. In the latter case, the xattr data can be preserved in a metafile and metafile data can be restored to native xattr format on OSX. The following async options are available for preserving extended attributes:


mode=nativemetafile, or none 


mode=nativemetafile, or none 


The default storage type is none. The default can be overridden with the aspera.conf setting<preserve_xattrs>. The default type and aspera.conf settings can be overridden with the command-line options.

If the sync is run by a regular user, only user-level attributes are preserved. If run by superuser, preserve everything.

•         Docroot support for server-side async. For information about docroots, see the user guide for Enterprise/Connect Server.

•         Support for aspshell. For information about aspshell, see the user guide for Enterprise/Connect Server.

•         New options for recognizing files and directories that have been renamed or removed. The options --scan-dir-rename and --scan-file-rename are useful but rely on your file system having stable inodes.

•         The configuration option <async_db_spec> can now be used to specify whether to run with the database in memory or on disk.  

•         Timeouts are now configurable for (a) connection establishment and (b) non-responsive sessions. In aspera.conf, use <async_connection_timeout> to specify the number of seconds async should wait for a session to be established before terminating. Use <async_session_timeout> to specify the number of secondsasync should wait for a non-responsive session to resume before terminating.

•         Removed the restriction on peer IP addresses changing for a given snapshot. This addresses issues with hosts that are in clusters or behind virtual IPs.

•         Sync can now synchronize files that are currently open for writing in other Windows applications, solving two problems:

-          If a file is open in an application (such as Excel, for example), it can still be synced (rather than causing a failure).

-          If a file is in the process of being synced, Sync does not prevent it from be opened in an application.

•         Deduplication can now be bidirectional as well as unidirectional. The primary benefit of deduplication is that it reduces network traffic by transferring only a single copy of files that are duplicates. The --dedup option can now be used in either of two modes, copy or hardlink. With --dedup=copy, duplicate files are recreated at the destination by copying. With dedup=hardlink, the duplicates are recreated using hard links. The hardlink mode works for all supported OSs except Windows. For Windows destinations, only copy mode can be specified.

•         Support for SSH agent (which stores passwords in memory). If you specify a private key on the async command line, it will be used. If no private key is specified,async will use the SSH agent. If there is no agent, it will prompt for a password.

•         New SSH fingerprint option --check-sshfp=value allows you to specify the expected fingerprint of the server.

•         A delay-deletion option --delete-delay postpones actual deletion until the end of the sync session.

•         The name of the option --retry-max, for setting the number of retries after a sharing violation, has been changed to --sharing-retry-max.

•         Conflicts and errors recorded in the snapshot are now cleaned at session startup.

•         Support for network file system mounts that have different encoding.

•         More comprehensive support for UNC paths.

•         Various fixes and improvements to preserve access, creation, and modification times of synced files.

•         Can now sync to a drive letter (Windows) or the root of a volume (Linux/UNIX).

•         A new benchmark tool asyncbench provides expected benchmarks by exercising the storage on which snapshot operations will be performed.

Other Changes

•         The async option --inode-format=format (where format is either native or hash) is no longer available, because native format is no longer an option. Hash mode is the default and only format.

•         The -M option, or --no-scan-dir-rename, is no longer needed and no longer available.


Windows: XP, 2003, Vista, 2008, 7, 8, 2012

Linux: Kernel 2.4 or higher and libc version GLIB 2.3.4+


Aspera Sync 1.4.3 Release Notes 

Aspera Sync 1.4.2 Release Notes 

Aspera Sync 1.4.1 Release Notes 

Aspera Sync 1.3.1 Release Notes 

Aspera Sync 1.3.0 Release Notes 

Aspera Sync 1.2.2 Release Notes 

Aspera Sync 1.2.1 Release Notes 

Aspera Sync 1.2.0 Release Notes 

Aspera Sync 1.1.0 Release Notes 



9265f7f1485a72f5eb49d413339c1e7d  aspera-sync-

ff1e7a366f6a474a32d8b6d512f8d27b  aspera-sync-



868139bfdcaec4ef7ba12a6d5bfd29ed11740c01  aspera-sync-

da28229089c3da95ca411c822de3da9b36aa4d01  aspera-sync-



Aspera Sync 1.5.3 User Guide (Windows) 

Aspera Sync 1.5.3 User Guide (Linux) 


For on-line support resources for Aspera products, including raising new support tickets, please visit the Aspera Support Portal. Note that you may have an existing account if you contacted the Aspera support team in the past. Before creating a new account, first try setting a password for the email that you use to interact with us. You may also call one of our regional support centers.


Article is closed for comments.
Powered by Zendesk