Contents I. Upgrading and Backwards Compatibility... 2 II. File Servers Supported... 2 III. What s New in QFS v IV. Bug Fixes in QFS v8.5...

Transcription

1 NTP Software QFS Release Notes Version 8.5 These Release Notes contain supplemental information about QFS Version 8.5. Topics include: Contents I. Upgrading and Backwards Compatibility... 2 II. File Servers Supported... 2 III. What s New in QFS v IV. Bug Fixes in QFS v P a g e 1

2 I. Upgrading and Backwards Compatibility Upgrading should be compatible from any previous version of QFS. All components should be upgraded to the same version family. II. File Servers Supported QFS 8.5 supports the following server types: 1. Microsoft Windows Includes support for Windows Cluster 2. NetApp 7-Mode C-Mode 3. EMC VNX Isilon 4. Hitachi HNAS 5. Other NAS Servers What s New in QFS v8.5 Performance enhancement for NetApp c-mode filers. Replaced xml parser with less overhead string processing code which increased performance and reduced the memory footprint. New feature to block MS Outlook PST and OLM files specifically when a file control policy has the patterns *.pst and *.olm. A new registry DWORD value has been added to control the behavior: KEY: HKLM\Software[\Wow6432Node]\NTPSoftware\[NCS ECS BCS] DWORD: BlockMSOutlookFiles Values: 0 disabled (default), 1 enabled What this feature will do is identify the pst/olm file to actually be an outlook file (it deeps scans the file in question) and will determine if it is an MS Outlook file and block the file, while a non-ms outlook PST/OLM file will be allowed. When a file is copied that is an Outlook PST/OLM file, the file will make it to disk but will be quarantined/deleted (depending on config on connector tab) when closed when QFS is able to scan the content of the file. **Note** this only works with the NAS version of the product. Changed the behavior of logging in the connector. All log messages that are considered an error or a warning are now logged by default. Previously you had to enable different flags for TraceLogFlags2 to be able to enable logging of the different components within the P a g e 2

3 service. Logging all error and warning message for all components by default should help with initial troubleshooting with the connector. Changed the underlying socket options in the connection to c-mode filers to disable the Nagle Algorithm. The Nagle Algorithm can have negative performance impact when sending small packets of information which QFS does when sending responses back to the filer. Performance enhancement with the UI when displaying directory sizes. The UI was slow when displaying non-* directories in the UI because for every path displayed, the connector had to go back to the filer to get volume information. The connector now gets the volume size and free space from cached information instead of asking the filer every time it gets the size of a managed directory. The cache is updated during normal volume cache refresh every hour by default. Revamped the directory rename code that determines whether a directory needs to be sized (moving a directory into or out of a managed directory) and also the code that updates the managed directories in the path of the directory rename if it was necessary. Changed the behavior of QFS in that the connector will no longer store managed folders where the volume doesn t exist on the managed device. Minor performance enhancement with user/group resolution when a user can t be found to not attempt to resolve the groups. Added support in the CLI to be able to add c-mode directory paths by adding a new parameter to the AddTargetPath command. Added caching of directory paths for share names on the filer. This is updated every hour and can be changed via registry setting under the NCS key. The DWORD value name is ShareRefreshRateMinutes and the default value is 60 minutes. Changed how the QFS service creates and caches the directory search handles with ADSI. The change forces ADSI to cache the socket that is created between ADSI and the domain controller. This will alleviate the constant opening/closing of socket ports during user and group resolution that happens under the covers of ADSI. Changed the re-connect logic within the NetApp connector to better handle the scenario where too many requests are outstanding on the filer and it goes into a throttled state, disconnecting us and reconnecting. Added 2 new registry settings for the NetApp connector to allow specifying the values to use for the engine settings of max-server-requests and max-connection-retries. The defaults within QFS have also changed. Max-server-requests is now set at 500 to reduce the number of times the outstanding request message is displayed, reducing the need to throttle the connection. Max-connection-retries is now 0 so that if the filer does not get a response from the connector in 60 seconds during a throttle state that it will completely disconnect QFS and will allow all backed up requests to go through. QFS will go through the normal process of reconnecting after x minutes. The new registry values are DWORDS called MaxServerRequests and MaxConnectionRetries. They can be specified in 2 places: P a g e 3

4 HKLM\Software\[Wow6432Node\]NCS\FPolicy -or- HKLM\Software\[Wow6432Node\]NCS\FPolicy\<SVM-Name> Setting them at the FPolicy level will affect all SVMs that the connector is managing. Setting it at the SVM level, will be specific to that SVM only. Setting at the SVM level overrides the FPolicy level. IV. Bug Fixes in QFS v8.5 Fixed a crash in the admin when testing the mail settings. If the admin couldn t load the dll used to send , an error message was to be displayed, but didn t have a valid parent window handle and would crash. Fixed a couple of QFS COM interface leaks in the qfs service. These showed up as consumed handles in the ease service and only if there was a failure in getting information from ease. Fixed a bug with the handling of PST and OLM files that were incorrectly getting quarantined when being opened versus created. Fixed a crash in the UI in retrieving EMC VNX details in certain situations due to a NULL pointer. Potential memory leak fix if the code failed to get the first row of data after a successful search in ADSI. Fixed a bug in the UI in basic view when selecting the quota tab for a file quota policy. Fixed a crash in the QFS service when loading the group cache if a blank sid was stored in the cache. Fixed an interface leak in the QFS service when loading notification text for file removal policies. Fixed an issue in processing home directory server matching logic that would incorrectly match the server names if the server names were differently lengths but identical up until the first character after the length of the shorter name. P a g e 4

5 Bug fix: Deleting FPolicy settings on c-mode was generating an error and was not being deleted. Bug fix: Disabling all directory notifications on c-mode 8.3 and below was not working due to wrong API being called. Bug fix: Memory leak fixes when communicating with management API to NetApp filers. Fixed a bug in the code that was causing the the QFS service to try to resolve the volume name of each managed directory as a share when a new directory was created on the filer. Bug fix: Quarantined files were being deleted before verifying both the file copy and the alternate stream were created successfully in the quarantine share. Fixed the issue with the command line build procedure and our new digital certificate Addressed a memory leak in the connector service when logging a message to the event log Fixed an interface leak in the qfs service if the connector was not running Fixed an interface leak in the qfs service during licensing processing. Fixed a sharing violation when writing the alternate stream data of a quarantined file. This caused the quarantine operation to fail and not remove the quarantined file from the source folder. Fixed a crash in the admin when viewing/setting the event log settings on the properties page of the application. P a g e 5

6 This "Release Notes" is for informational purposes only. NTP SOFTWARE MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS DOCUMENT. NTP Software and other marks are either registered trademarks or trademarks of NTP Software in the United States and/or other countries. Other product and company names mentioned herein may be the trademarks of their respective owners. NTP Software products and technologies described in this document may be protected by United States and/or international patents. NTP Software 119 Drum Hill Road # 383 Chelmsford, MA Phone: info@ntpsoftware.com Web Site: All rights reserved. All trademarks and registered trademarks are the property of their respective owners. Doc#5009EF P a g e 6