Enterprise Server 2.2.1 Release Notes

Enterprise Server 2.2.1 Release Notes
Version 2.2.1
Platform: Windows, Mac, Linux, Isilon
June 1, 2009
  • What's New
    • New client and server configuration system, providing enforcement of server transfer policies via automatic negotiation with clients. Policies are configurable by individual users and groups, and are automatically applied to the client transfer, including:
      • Bandwidth Policies such as transfer target rate caps, minimum rate caps, transfer policy, and maximum priority;
      • Encryption Handling including transport and content encryption requirements;
      • Authorization Criteria including user docroots. Docroots can now be set on the group-basis and support Active Directory groups. Individuals users can log in with full domain name.
      • Vlinks for aggregate bandwidth control now configurable by group, with default and maximum bandwidth priority by user;
      • New advanced file handling capabilities including transfer manifest, exclude filters and full-job ETA reporting.
      • All policies configurable from the Console, and major policies are configurable from an enhanced Windows User Manager. Enhanced User Manager also now supports LDAP.
    • New disk rate control. A patent-pending innovation that extends Aspera's adaptive rate control to provide congestion avoidance for transfers over fast networks exceeding the storage bandwidth. Prevents overdrive of relatively slower storage or file systems, and maintains stable high throughput for both single and concurrent transfers.
    • New Central Management Capabilities via Aspera Console
      • Supports remote configuration of nodes (Enterprise Server and PtoP) from the Console
      • Supports server to server transfer capability with docroots
      • Supports whole Job-based Reporting and Email notification for Hot Folder transfers. File sets dropped into a hot folder are grouped as one job, with unified reporting and email notification
      • Supports automatic reconnection of nodes to the Console on connection failure
    • New Capabilities Supporting Web-based Applications
      • Token authorization for HTTP fallback and external authorization are now supported on the same server
      • New JavaScript APIs for Connect enable folder uploads on Vista and Linux and Content Encryption on all platforms
      • New file browser in Connect properly supports resume of directory downloads
      • Connect Server now supports transfers with multiple distributed servers from a single interface. Multiple transfer servers can be configured out-of-the-box.
  • Fixed Issues
    This list covers the critical and major problems fixed in Enterprise Server and Point-to-Point 2.2.
    1. ascp
      • Reduced the verbosity of standard logging to syslog by moving non-essential messages to the debug logging level. Logging is now more appropriately classified as error, info and debug levels.
      • Fixed failure when reading double byte characters from docroot file.
      • Fixed the fasp rate cap enforcement (aspera.conf).
      • ascp now handles disk drive letters in the source paths.
      • Implemented full support for the transfers sources containing symbolic links using the symbolic link option "-o SymbolicLinks=copy".
      • On Isilon, added needed symbolic links to fasplicense.txt.
      • On Isilon, added configurable buffer settings to accommodate highly concurrent transfers.
      • Corrected the 16-item limit on exclude patterns.
      • Fixed corner-case memory leak in windows ascp receiver.
      • Fixed issue manifesting in 2.2 Connect release on Mac OS X where ascp could not find its log directory.
      • Fixed the missing aspera-scp-transfer.log in the FAT32 file system.
      • Improved the detail of error messages thrown on interrupted data transfers, and corrected truncation of error message details.
    2. Aspera Scp GUI
      • Fixed the SCP: k2 & -p options to keep the original time stamps for new directory after transfer.
      • Fixed bug in which bandwidth detection to an endpoint fails when a non-default SSH port is configured.
      • On Windows, fixed a corner-case bug in which drops the SSH connection during transfer.
      • On Windows, fixed an issue causing the GUI to become unresponsive/frozen when log files are opened.
      • On Windows, added protection to prevent an overflow crash when a very large number of files is selected.
      • On Mac OS X, upgraded the progress meter widget used to avoid a bug in the JRE causing excessive CPU.
    3. Windows User Manager
      • Improved the domain controller look up function used to allow for automatic failover when the primary controller is down, and to exploit location of the nearest DC.
      • Extended support for Active Directory user accounts to log in through fully qualified domain names.
    4. Asperasync
      • Added comprehensive unicode encoding of textual values throughout the application. Prevents crashes when unusual characters or symbols are used in folders or files.
      • Fixed a bug in handling deep paths.
      • Fixed an issue in which newly edited hot folder properties don't take effect until asperasync is re-started.
      • On Windows, fixed an issue where hot folder configuration was not preserved on upgrade of Enterprise Server or Point-to-Point.
      • For push hot folders, added support for destinations having UNC paths containing IP addresses (rather than host names).
    5. Connect Server ("Aspera Web")
      • Added a new 'upload folder' control using a new AsperaWeb browser plug-in function designed to support folder uploads on all platforms (the previous implementation did not support folder uploads on Linux or Vista.)
      • Added support to authenticate users by their fully qualified Active Directory name, and a corresponding aspera.conf setting.
      • On Windows, fixed an issue causing a javascript error to be thrown if the aspera.conf file is not readable.
      • On Windows, fixed an issue causing directory listing to fail when the parent of the user's docroot is not readable.
      • Added support to enforce a configurable minimum Connect version.
      • Fixed a bug causing a failure when transferring packages with titles starting or ending with a comma.
      • Fixed a bug causing a failure when an uploaded folder contains parentheses in the the name.
    6. AsperaWeb JavaScript API and Connect
      • Fixed the file browser and directory download function so as to not create a new folder inside the target folder, properly allowing for downloads of the same directory to properly overwrite and resume.
      • Fixed the file browser and directory upload capability to allow for directory uploads on Vista and Linux desktops.
      • Added support for token-based authorization needed by HTTP fallback and external authorization on the same server.
      • Added JavaScript API support for requiring content protection (encryption-at-rest) in Connect transfers.
    7. Pre- and Post-Processing
      • On Isilon, fixed an issue in which aspera-prepost was being executed from the wrong location.
      • Corrected an issue in setting the environment variables passed to the aspera-prepost when using UNC paths.
      • Added an environment option for the path to the manifest file, MANIFESTFILE.
    8. Console/Faspex Support
      • Added a new asctl all:info output option.
      • Corrected an issue in error reporting in which transfers failing due to an invalid port indicate the wrong direction on the Activity Page.
    9. Others
      • Corrected the asprotect.exe manual page.
      • On Debian 4.0, fixed an Aspera Central restart failure.
      • On Fedora 8 and Red Hat Linux 5 (32bit), fixed an issue in which the dblogger fails to initialize mysql.
      • Several corrections in the administrator guide for Enterprise Server.
      • On Isilon, fixed an issue causing the syslog rotation of the aspera transfer log to fail.
      • SSH host keys are preserved on upgrades going forward from 2.2.1.
  • Known Issues
    This list covers the known problems with Enterprise Server 2.2.1.
    1. If <WEB> section has a rate specified in percentages (for example 75p).
      Workaround: modify the v1 conf to use an absolute rate, for example 45000 or 100000 and re-run the conversion tool.
    2. Hybrid v2 conf files are not converted (intentionally). These are the conf files used in 2.1 for HTTP fallback. We introduced a hybrid system before the v2 conf file was ready, because http uses it for its configuration.
      Workaround: remove the version="2" from the top of the file, then convert manually, then visually inspect the configuration file to make sure it captures both the old v1 directives as well as the v2 ones.
    3. faspex 1.5 prevents Windows user manager from adding/removing users.
      This happens because faspex holds the passwd file open. It is fixed in faspex 1.6 (to be released soon).
    4. Windows permission problems for passwd or group file. This causes the user manager to fail silently.
      Workaround: fix file permissions to allow the account operating the user manager or conversion tool to write the files.
    5. User accounts that no longer exist. The conversion will not be able to find the user name for all the UIDs in the old docroot file. It will add the users in aspera.conf by using their UIDs (for example 1111, 1112).
      Workaround: either create the users that are still needed, or delete them from the docroot file before the conversion.
    6. When upgrading your product from a prior release, the existing SSH Host Keys are not preserved (preservation of keys has been implemented in 2.2.1 for future upgrades).
      To workaround, in Aspera's installation folder, backup the SSH key files if you intend on using the same keys.
      Installation folder:
      • Windows 32bit \Program Files\Aspera\FASP\etc\
      • Win 64bit \Program Files (x86)\Aspera\FASP\etc\
      • OSX /Library/Aspera/etc/
      • UNIX (After v.2.0.2) /opt/aspera/etc/
      • UNIX (Before v.2.0.2) /var/opt/aspera/etc/
      • Isilon /ifs/.ifsvar/aspera/etc/
      Backup the following key files:
      • ssh_host_dsa_key
      • ssh_host_dsa_key.pub
      • ssh_host_key
      • ssh_host_key.pub
      • ssh_host_rsa_key
      • ssh_host_rsa_key.pub
    7. Transfers may fail if the following characters are used in the source or destination file names: / \ " : ? > < & * |
      • ascp strips beginning of path if path contains a colon (:). Workaround: Avoid using the colon in the folder and the file name.
      • In the Connect Server, the question mark in the source file name prevents the transfer. Workaround: download the containing folder or rename/move the file.
      • In the GUI, trying to delete a file with the " (double-quote) from the local computer results in silent failure; trying to delete a file with the " (double-quote) from the remote server results in the error message: "Invalid command or token separator mismatch" Workaround: delete or rename the file via OS provided mechanism, such as the file explorer and the Finder.
      • In the Aspera Scp, the transfer fails when the back-slash (\) is used in the file name. Workaround: Avoid using the back-slash in the file name.
    8. If you are upgrading from version 2.1.3, the configuration file aspera.conf will not be converted into the new format. Refer to the product's user guide for manual configuration instructions.
    9. In the log file, if the peer is running Aspera's product prior to version 2.1.2, it displays x.x.x.x
    10. Public key authentication is not supported on Windows Vista.
    11. If the "pre-calculate job size" takes more than 1 minute (e.g. transfers of 100,000 files or more), the transfer may timeout.
    12. If a file is dated earlier than January 1, 1970, ascp crashes on a _localtime64 assert.
    13. In the Connect Server, attempting to delete an empty directory without permissions fails silently.
    14. When an exclude filter is used or symbolic links are skipped, ascp incorrectly reports the excluded files in its pre-transfer count of files to be transferred.
    15. When transferring a single file to a non-existing target directory, using the -d option to create the directory, the directory creation fails to respect the permission settings specified in the aspera.conf
    16. The HTTP Fallback's transfer protocol is restricted to the aspera.conf's transfer setting <allowed_cipher />. When the option is set to none, HTTP will be used; if the option is missing, HTTPS will be used. Refer to the Appendix 5. Transfer Settings in aspera.conf in the documentation for configuration.
http://www.asperasoft.com/en/release_notes/default_1/release_notes_2
Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk