FileFly 2.1 Release Notes

This release of FileFly features stub deletion monitoring and single stub snapshot restores, numerous improvements to logging, and support for Windows Server 2016.

Agent Logging

• New: agent.log and messages.log
• Retired: summary.log and console.log
• Improved log rotation
• Rotated log compression

Admin Console

• Improved Active Directory authentication support
• Improved login/logout
• Fixed: incorrect timezone format in activity emails
• Fixed: issue where scheduled task would run on the wrong day

Agent

• Updated openssl libraries
• Improved syslog to minimize loss of UDP log messages
• Migration driver updated: some new features and fixes will not be applied until next reboot

Windows

• Added support for Windows Server 2016
• Windows Server 2012 R2 now requires at least April 2014 rollup update
• Scrub policies improved by new stub deletion monitoring feature
• Status ‘out of disk quota’ or ‘disk full’ no longer suspends demigrator
• Fixed: DFSN folder creation issue
• Fixed: data loss during CIFS copy of stubs between certain Windows versions
• Fixed: DFSR interoperability issues
• Fixed: FSRM installation issue
• Improved sociability with Cygwin applications

• Fixed: migration driver disconnection issue necessitating a service restart

• Fixed: stub deletion errors and/or performance issue with WORM destinations

Caringo Swarm + CloudScaler

• Fixed: Content-Disposition encoding issue

NetApp Cluster-mode

• Enabled single stub snapshot restore via FPolicy Servers
• Added support for ONTAP 9.0/9.1
• Fixed: spurious ERR_ADD_SHORT_MIGKEY errors

Known Issues

• NetApp ndmpcopy cannot copy stubs.
• NetApp: changing attribute flags of NetApp stubs without first demigrating them may cause a demigration followed by the migration flag being re-applied.
  Workaround: demigrate/open stubs before changing attributes

• FileFly stores a Content-Disposition header containing the original filename, so that it can be downloaded. However, it is not properly escaped, so a filename with a comma causes Chrome to fail with a header error:(net::ERR_RESPONSE_HEADERS_MULTIPLE_CONTENT_DISPOSITION): Multiple Content-Disposition headers received. No workaround is available, so contact Support if you encounter this problem. (FFLY-48)