Release Notes: IBM Aspera High-Speed Transfer Server, High-Speed Transfer Endpoint, and Desktop Client, 4.4.2

NEW FEATURES

Added support in async for storing the preserved ACL contents in the async database. (Aspera #25)

Added support for authenticating to Redis by using ACL user identifiers and storing them securely in askms. (Aspera #388)

Added support for preserving Object Lock and Legal Hold metadata for AWS S3 objects when transferring from an AWS S3 source to an AWS S3 destination. (Aspera #413)

Added support for a new option in async to perform deletes before new or updated files are transferred to the destination. (Aspera #514)

Added support for timestamp, uid, and gid preservation for growing files through Watch Folders. (Aspera #546)

Added support for additional parameters for growing files through Watch Folders like ssh fingerprint, read block size, connect timeout, ... (Aspera #617)

Added support for automatically storing and updating the ID of the primary asperanoded node in a HA redis deployment. (Aspera #633)

BREAKING CHANGES

If you are upgrading from a previous release, the following changes in this release might require you to adjust your workflow, configuration, or usage.

Aspera #940 - The default for _transfer_in_bandwidth_flow_min_rate_cap and _transfer_out_bandwidth_flow_min_rate_cap has changed from Unlimited to 0 to prevent setting a minimum rate that conflicts with the vlink configured rate.

Aspera #1056 - The --log-io functionality in asperanoded has been removed.

ISSUES FIXED IN THIS RELEASE

Aspera #481 - Fixed a problem where async might not preserve directory permissions correctly for root-owned directories when running with elevated Linux capabilities.

Aspera #474 - Fixed a problem where Lua transfer events stop being processed after an error happened in a Lua script handling transfer events.

Aspera #574 - Fixed a problem where growing files might be copied multiple times and not marked as completed through Watch Folders.

Aspera #579 - Fixed a problem where the async server process might report a 'Disconnected from peer' error to management applications like Aspera Console even though the session was successful.

Aspera #595 - Fixed a problem where a stale lock file is not cleaned up if async fails to start.

Aspera #599 - Fixed a problem where the asnodeadmin option --access-key-restore returns an error in configurations by using HA redis.

Aspera #612 - Fixed a problem where Node API requests specifying a 'name=' filter might fail if the name is longer than 48 characters.

Aspera #621 - Fixed a problem where iteration tokens that are returned by the /ops/transfers Node API endpoint might be incorrect values.

Aspera #665 - Fixed a problem where ascp4 might hang when a file pair list input file is provided with a large number of file pairs.

Aspera #704 - Fixed a problem where async with the dedup option enabled might not create hardlinks for files that are the same as other preexisting files.

Aspera #716 - Fixed a problem with asperanoded being unable to start in AIX.

Aspera #753 - Fixed a problem where ascp fails to validate node user bearer tokens when establishing the transfer that uses a WebSocket channel.

Aspera #762 - Fixed a problem where async on Microsoft Windows might transfer files that are moved to the 'keep' directory.

Aspera #787 - Fixed a problem where ascp4 might not be able to transfer symlinks in a 'receive' transfer.

Aspera #797 - Fixed a problem with asperasync (HotFolders) might fail after a few minutes of activity.

Aspera #846 - Fixed a problem where using async on Microsoft Windows with compression enabled might result in the root drive losing its file system ACL entries.

Aspera #921 - Fixed a problem where starting an async job by using the Node API with client async activity logging enabled and that uses a CIFS path as the source might result in the async data being reported to an incorrect key in redis.

Aspera #929 - Fixed a problem where async might update the mtime of a symlink target in the destination system when just the symlink was transferred and not the target.

Aspera #1003 - Fixed a problem where the product installer might fail to start with an error when running in a Microsoft Windows system set to a language different than English.

Aspera #1044 - Fixed a problem where async might remain running indefinitely when using multiple transfer threads if one of the ascp subprocesses failed.

Aspera #454 - Using HTTP Fallback to upload a file or creating files by using the Node API might not result in setting the permissions for the file specified in the 'create_file_mode' configuration setting.

Aspera #535 - Fixed a problem where inconsistencies between the client and server databases for an async job might result in async not terminating with pending paths that are not cleared.

Aspera #740 - Fixed a problem where a vlink set via schedule might start the transfer with the default capacity rather than the capacity that must apply per the schedule.

Aspera #842 - Fixed a problem where async might not be able to restart a job again if there is an error applying the database journal.

Aspera #904 - Fixed a problem where Watch Folder might enter an invalid state that prevents it from transferring any more files if a file in the transfer set is deleted during the transfer.

Aspera #906 - Fixed a problem where Watch Folder might be unable to delete directories on S3 when 'delete after transfer' is used.

Aspera #994 - Fixed a problem in async where the parent directory's timestamp might not be preserved when a hard link is synchronized.

Aspera #1021 - Fixed an issue in ascp where symlinks might cause transfer failures in multi-session mode.

Aspera #1040 - Fixed a problem where a transfer might be unable to resume a previously partially uploaded file to Azure.

Aspera #1073 - Fixed a problem where hardlinks created by async might not get deduplicated with the --dedup=inode option.

Aspera #1085 - Fixed a problem where transfers to AWS S3 across accounts might not work when using an access point alias for the bucket.

Aspera #1181 - Fixed a problem where transfers started with the GUI might hang on 'Establishing connection' when trying the gssapi-with-mic authentication option.

Aspera #1196 - Fixed a problem in ascp where using --delete-before-transfer might result in unexpected paths that are removed from the destination when the source paths are specified through a --file-list.

Aspera #1218 - Fixed a problem where async might report a transfer error despite the transfer being successful if a generic cloud storage docroot is specified with the bucket being part of the source directory that is provided to async.