8.0 Upgrading Filr

Critical Prerequisites and Cautions for Successful Upgrades

Failure to comply with any of the following critical points can result in a non-functional Filr system.

NOTE:As an additional resource to the information in this section, TID 7017288 has a “Pre-Flight Checklist” that can help you ensure a successful upgrade.

Critical Points

Details

  • You cannot upgrade directly from Filr 1.0 or 1.0.1 to Filr 2.0

You must first upgrade to Filr 1.2, apply all patches, ensure that all desktop clients are updated, and then upgrade to Filr 2.0.

  • You cannot upgrade from Small to Large

If you have a small, all-in-one deployment, and you need a large, separate-appliance deployment, you must install new appliances.

  • You cannot upgrade from non-clustered Large to clustered Large

If you have a large non-clustered deployment, and you need a large clustered deployment, you must install a new system. (The shared storage location, /vashare, must be configured during the initial installation.)

Or, contact Novell Consulting to assist you with the migration.

  • Meet all hardware and software requirements

See Section 1.2, Filr System Requirements

IMPORTANT:Memory requirements for the Filr and database appliances have increased with Filr 1.2 (see Memory Requirements).

  • Ensure that each appliance has unformatted disk space available for a new /var disk

For each appliance you are upgrading, you must plan to create a third disk for storing system event log files.

  • Ensure that each Filr 1.2 system is fully patched before upgrading to Filr 2.0

See Managing Field Test Patches in the Filr 2.0: Administration Guide.

  • Do not copy the entire VM when upgrading

Copying the entire VM causes various problems, including the reassignment of the Eth0 interface to Eth1. Filr supports only Eth0 as the primary network interface.

Copy only the datastore disk to the new VM location, as specified in Section 8.3, Copying the Appliance Data Storage Location to Prepare for the Upgrade.

  • (VMware) Remove all snapshots prior to upgrading an appliance

This is required to ensure that the correct disk file and the latest configuration settings get migrated.

  • You must upgrade the appliances in the proper order.

Successful upgrades require that appliances be upgraded in the order of dependency upon each other, as follows:

  1. Upgrade the MySQL appliance first.

  2. Upgrade the Filr Search appliances next, one at a time.

  3. When the upgraded MySQL and Filr search appliances are up and running, upgrade the first Filr appliance in the cluster. Then upgrade the additional Filr appliances, one at a time.

IMPORTANT:All of the Filr and Filr Search appliances in a Large clustered deployment must run the same version.

  • If you are migrating the Filr database to Microsoft SQL ...

Carefully follow the instructions in Section B.0, Migrating the Filr Database from MySQL to Microsoft SQL, including running the Post-Migration script.

  • If your appliances have multiple Network Adapters ...

Carefully follow the instructions in Section 8.2, Preparing Network Interface Controllers to Be Upgraded, including running the networkprep script.

  • Fully patch any OES 11 SP1 target servers

Ensure that any Filr target servers running OES 11 SP1 have at least the December 2012 Scheduled Maintenance Update applied. This ensures that the NCP server can keep up with the increased service requests of Filr 2.0.

Failure to update your OES 11 SP1 servers can cause the configured eDirectory (LDAP) servers to fail.

Complete the instructions in the following sections as applicable to upgrade from Filr 1.1 or 1.2 to Filr 2.0.