Section 1.5.1, Rolling Upgrades Are Not Supported in a Clustered Environment
Section 1.5.2, Missing Files Due to an Accent Character Need to Be Re-Synchronized after Upgrade
Section 1.5.3, OES 11 SP1 Servers Must Be Updated before Upgrading to Filr 1.1
Section 1.5.4, Updating Password When Using Non-English Keyboard Results in Unknown Password
Rolling upgrades (upgrading one Filr or search index server while another continues to serve clients) are not supported when upgrading from Filr 1.0.1 to Filr 1.1 in a clustered environment.
You must shut down all Filr and search index appliances before you begin the upgrade process. Then re-start the appliances after the upgrade is complete.
This issue does not affect small or non-clustered large installations.
For information about how to upgrade Filr, see Upgrading Filr
in the Novell Filr 1.1 Installation and Configuration Guide.
In the initial Filr release, Filr did not distinguish accent characters in file names. As a result, if one file was synchronized from the file system to a Net Folder and then another file with the same name (except for the presence of an accent character) attempted to synchronize, the synchronization would fail.
This issue was fixed in Filr 1.0.1. Now, separate files or directories with names that are identical other than an accent character can be synchronized to Filr from the file system.
To enable these types of files to synchronize after upgrading from Filr 1.0 to later versions, do one of the following:
Enable Just-in-Time synchronization (JITS) on the Filr site if it is not enabled already. Then navigate to the folder that contains the files, in order to trigger JITS and update the contents of the folder. See Enabling Just-in-Time Synchronization
in the Novell Filr 1.1 Administration Guide.
Perform a full synchronization on the Net Folder that contains the files. See Synchronizing a Net Folder
in the Novell Filr 1.1 Administration Guide.
IMPORTANT:Failure to update your OES 11 SP1 servers can cause the configured eDirectory (LDAP) servers to fail.
Scalability and performance improvements provided in Filr 1.1 require that Filr-targeted servers be able to handle increased file service and other requests.
The NCP server that shipped with OES 11 SP1 cannot handle the increased requests.
If you have any OES 11 SP1 servers that match the following criteria, you must update the OES 11 SP1 server before upgrading to Filr 1.1:
Host Net Folders or Personal Storage Home folders
and
Do not have the December 2012 Scheduled Maintenance Update applied
To prepare the OES 11 SP1 servers to handle Filr 1.1:
Ensure that all Filr-targeted OES 11 SP1 servers have at least the December 2012 Scheduled Maintenance Update applied.
This updates the NCP server to a newer version that is capable of keeping up with the increased service requests of Filr 1.1.
Proceed with the upgrade to Filr 1.1.
NOTE:OES 11 SP2 contains the updated NCP server by default and is able to meet all Filr 1.1 service demands.
When updating the root and vaadmin passwords during the Filr upgrade when using a non-English keyboard, the passwords are recorded as if you were using an English keyboard.
To work around this issue, specify 1234 as the root and vaadmin passwords during the upgrade process (or use another simple password that uses the same keys regardless of the keyboard language). After the system is successfully upgraded, change the password as described in Changing Administrative Passwords
in the Novell Filr 1.1 Administration Guide.
When upgrading the Filr system, some settings might not be preserved. The following settings are not always preserved after upgrading to Filr 1.1:
SSH
Ganglia
WebDAV authentication method
Requests and Connection settings
After upgrading to Filr 1.1, verify that all settings are as desired.