IBM Aspera Sync 3.5.4 Release Notes
IBM Aspera Sync 3.5.4 Release Notes

IBM Aspera Sync 3.5.4 Release Notes

  • Product Release: Feb 27, 2015
  • Release Notes Updated: Feb 27, 2015

WHAT'S NEW

IBM Aspera Sync 3.5.4 provides the new features, fixes, and other changes listed below.

  • Sync now triggers a transfer when only the permissions have changed (and no content has changed).
  • Software and documentation are now in compliance with IBM naming conventions, copyright notices, and trademark notices.

ISSUES FIXED IN THIS RELEASE

#14504 - When scanning or monitoring a file system for changes, async skips files with names that end in one of the special suffixes specified in the configuration file with <resume_suffix> and <partial_file_suffix>. To disable this behavior, set these values to the empty string. By default, the <resume_suffix> value is ".aspx". By default, the <partial_file_suffix> value is the empty string, but is often set to ".partial".

#29314 - The hot folder feature "Send Changes Daily at" does not work.

KNOWN ISSUES

#5527 - Sync may not respond cleanly if the file system it uses becomes full. After making more room, it may be necessary to shut it down forcibly and rebuild the snapshot database before normal operation is restored.

#8412 - A backslash (\) in a file name produces an error.

#9126 - The application logs events at a fast rate. The log destination must have room for large log files.

#12298 - Due to a bug in Windows 7, the result code from asyncadmin -T is not meaningful.

#13645 - Sync never completes when a directory is renamed during a transfer.

#13761 - If file names contain "\" or new line, async tries to transfer but fails, causing the internal transfer queue to become full and the synchronization to stall (or hang after all other files have completed).

#13826, #13827, #13833 - Limited Unicode filename support on Windows.

#23888 - Sync does not trigger a transfer when only the permissions have changed (and no content has changed).

#25631 - When transferring from Windows to Mac using preserve-acls=native and remote-preserve-acls=native, ACL data is saved as xattr. Workaround: Do not use the "native" setting when transferring/sync'ing across platforms.

#25915 - When async is set to continuous, overwriting an existing file on the initiating node may result in the deletion of the previous version of the file on the responding node. Workaround: Perform the sync manually to recreate the deleted file.

#27621 - Sync conflicts due to handling of hidden, temporary, or transient files (such as those created by Microsoft Office products).

#28817 - The Sync log entry for SYNCERROR_DELAY does not include information describing the file name and path.

#29038 - The default checksum behavior with S3 (as with any cloud storage) is "none". An existing file on S3 is considered identical to the local file when their sizes are equal. Therefore the file on S3 is not overwritten, even when the content of S3 differs from the content of the local file. Using overwrite=always does not overwrite the file.

#29474 - Pushing to S3 with the --scan-dir-rename option causes Sync to hang.

SYSTEM REQUIREMENTS

Windows: 7, 8, 2008r2, 2012

Linux 64-bit: RedHat 6-7, CentOS 6-7, Fedora 16-20, Ubuntu 12-14, Debian 6-7, SLES 11-12 Kernel 2.4 or higher and libc version GLIB 2.3.4+.

Mac OS X: 10.7, 10.8, 10.9, 10.10

PACKAGE INFORMATION

Windows: aspera-sync-3.5.4.100593-win-v100-32-release.zip

MD5:  be91ac86765eab28d8cd8a9c1d38581d
SHA1:  810c25d1c3c293c5511cade508f048fb4c902900

Mac OS X: aspera-sync-3.5.4.100407-1-mac-intel-10.9.tar

MD5:  6ea5fe62c6361f503941c9edf1d1632e
SHA1:  8925c2bf378ac7948f0820b7ff54a74bb3c7d392

Linux 64-bit: aspera-sync-3.5.4.100407-1-linux-64.tar

MD5:  93bca83a9d8b27f47628c0217cf03106
SHA1:  1a00dac1e8d1a36e48e1edad0c233f63a99443b9

Linux 32-bit: aspera-sync-3.5.4.100407-1-linux-32.tar

MD5:  f1d1608534670782a161ada4a0838d3e
SHA1: 184fe30cc3609bde8f03531e4c364728ae38b05c

PRODUCT SUPPORT

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.