Table of Contents |
---|
The 4.0 4 release of FileFly features a new user interface, significant changes to plugins, improvements to AdminCenter, charts and reportsLinkConnect, NetApp, S3, security, and performance enhancements.
...
Info |
---|
Upgrade impacts
|
NetApp Customers Only
ONTAP 9.6 is the minimum supported version.
This version transitions to using the ONTAP REST API for FPolicy management. This is necessary since ONTAP 9.12.1 will be the final version to support the legacy Management SDK (ONTAPI).
Changes in 4.
...
4
Destination plugins are no longer installed separately.
Destination plugin Config Tools and plugin
.cfg
files are no longer used.
The Config Tools can be uninstalled completely – plugin selection and configuration is now performed via the Servers page in the Admin Portal.Some scheme/plugin names have changed in this release (see below)
...
Fixed email report GUI issue for non-English Windows locales
Various GUI and error-handling improvements
Revised minimum system requirements (now 12GB RAM, 10GB disk space for log files)
File system browser improvements
Improved logging for Post-Restore Revalidate operations: no longer logs excessive messages pertaining to files for which no secondary storage update was required
Eliminated potential race condition when backing up Server configurations
Changes in Agent (General)
Windows and SMB File traversal no longer traverses out of read-only volumes (e.g. a snapshot)
Fixed CONCURRENT_MODIFICATION errors during policy operations on read-only files
SECURITY: Updated openssl libraries
Revised minimum system requirements (now 8GB RAM)
Security Improvements
Support TLSv1.3 (TLSv1.2 and TLSv1.3 are available for all components)
Require TLS forward secrecy by default
...
Fixed Moonwalk FPolicy Server failure that caused an inability to access stubs or run policies (introduced in 4.4)
ONTAP 9.6 is now the minimum supported version
Transitioned to ONTAP REST API
Added SACL handling options to GUI instead of manual overrides
Changes related to Azure
Raised maximum object size limit (now ~190.7 TiB)
Fixed GUI issue when listing containers of an empty storage account
...
Improved compatibility with 3rd party S3 implementations
Fixed missing sddl-infomask metadata field
Updated support for new AWS regions
Upgrading from 3.x
Must to Know
Do not attempt a FileFly upgrade until all running tasks have been completed. The FileFly scheduler (responsible for launching scheduled tasks) must also be disabled before performing an upgrade.
Info |
---|
ACTION REQUIRED prior to upgrading For each Vserver:
|
FileFly Tools must always be upgraded first, followed by all FileFly Agent and FileFly FPolicy Server components. Any installed plugins are upgraded automatically during FileFly Agent upgrade. Upgrade all components to the same version unless otherwise specified.
Download the release bundle from the Downloads page and expand it on your FileFly Tools server.
Go to Settings > Scheduler > Suspend Scheduler.
View file name Invalid file id - UNKNOWN_MEDIA_ID Run the
DataCore FileFly Tools.exe
installer.If the license has changed (such as from FileFly 2.x), upload a new license file from Caringo / DataCore.
Upgrade all FileFly Agents and FileFly FPolicy Servers:
Automated (recommended) — From the Admin Portal 'Servers' tab, click Upgrade Servers. The automated process transfers installers to each server and performs the upgrades in parallel to minimize downtime. If a server fails or is offline during the upgrade, manually upgrade it later. Once the automated upgrade procedure is finalized, the 'Servers' tab updates to display the health of the upgraded servers.
Manual — Run the FileFly Agents and FileFly FPolicy Servers executables directly and follow the instructions. Check the Admin Portal 'Servers' tab for warnings.
Resolve any warnings if displayed.
Click Start Scheduler.