12.2 Upgrading a Large Filr Deployment

Before upgrading a Filr deployment, you must ensure certain requirements are met. See Before You Upgrade! and then complete the instructions in the following sections in order:

Before You Upgrade!

Failure to comply with the following critical points could 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 Point	Details
Review the Release Notes and Limitations	Check the Release Notes for any upgrade issues and Upgrade before you start the upgrade process.
Plan the upgrade order and follow it.	You must upgrade the appliances in order of dependency upon each other. Shut Down Order: Prepare a list of your appliances that defines the correct shut down order: Filr: All Filr appliances must be shut down first. Filrsearch: Next, you shut down the Filrsearch appliances. MySQL (if applicable): If you are using MySQL appliance (shipped with Filr), then ensure it is running. Deployment Order: Prepare a second list of that defines the correct upgrade and deployment order: Filrsearch: You must upgrade and deploy the Filrsearch appliances before the Filr appliances. Filr: When the upgraded Filrsearch appliances are up and running, upgrade and deploy the first Filr appliance. Then upgrade and deploy the additional Filr appliances. If there are things you need to remember about individual appliances, include those reminders in the appropriate list. Use the shut down list as you complete the steps in Upgrading the VMs. Use the upgrade list as you complete the steps in Deploying the Upgraded (Replacement) VMs.
Ensure that the VM host has enough unformatted disk space.	The VM host server must have enough unallocated disk space to contain the following disks for each appliance. This is only temporary because after the upgrade completes, old appliances can be deleted and their disk space reclaimed. System Disk (/): This is created automatically as you deploy the downloaded software. Size is 20 GB per appliance. Disk 2 (/vastorage): You make a copy of each old appliance’s Disk. Size needed equals the total size of all disks to be copied. Each Disk 3 (/var): You create this disk for each appliance in conjunction with the upgrade process. Size recommendation for Filr is 4 GB plus 3 times the RAM allocation for each appliance being upgraded. NOTE:The existing /vashare mount point is used by the upgraded Filr appliances. No new disk space is required for upgrading.
Make sure that existing appliances are running version 3.x with the latest patches.	Make sure that all appliances are running version 3.x with the latest patches applied. See Managing Field Test Patches in the Filr 3.4 Administrative UI Reference. The earlier version of Filr must be upgraded to Filr 3.x for upgrading to Filr 4.0.
Remove all VMware Snapshots	Before copying Disk 2, make sure to remove all VMware snapshots so that the /vastorage disk has the correct disk file and latest configuration settings.
Make sure that upgraded appliances meet the system requirements.	See Section 3.0, Filr System Requirements.
Do not attempt unsupported path migrations.	No Cross-platform: You cannot upgrade from one virtualization platform to another. You can only upgrade VMware to VMware, and so forth. No Mixed Versions: All of the Filr and Filrsearch appliances in an expandable deployment must be upgraded to the same version. No Cross-Deployment-Types: You can only upgrade small to small, non-expandable to non-expandable, or expandable to expandable. If you have a small or non-expandable deployment, and you need an expandable deployment, you must either install a new system or contact Micro Focus Consulting to assist you with the migration.
Appliances with two network adapters.	You should manually add the additional network card on successfully upgrading the appliance.
Plan when to upgrade.	Filr services must be offline during the upgrade. Schedule the upgrade for a block of time that is least disruptive from a production standpoint. Notify Filr users about the upgrade.

After ensuring that you have met the prerequisites and cautions above, complete the instructions in the following sections in order.

12.2.1 Understanding the Appliance Upgrade Process

The process of upgrading Micro Focus appliances is illustrated in Figure 12-1.

Figure 12-1 Overview of the Appliance Upgrade Process

12.2.2 Downloading and Preparing Software for the Upgrades

Download and prepare the software for your virtualization platform as described in the following sections:

VMWare

Download the Filr software shown below to your management workstation.

IMPORTANT:Registration with Micro Focus is required to receive an email with a software-download link.

Appliance Type	Filename
Filr	Filr.x86_64-version.ovf.zip
Search	Filrsearch.x86_64-version.ovf.zip
PostgreSQL	PostgreSQL-version.ovf.zip

Extract each .ovf.zip file on your management workstation until an ApplianceType-version folder appears.
Launch the vSphere Client and navigate to the datastore where you plan to host the upgraded VMs.
Create a folder for each appliance that you plan to upgrade.

Name each folder with a name that is easily associated with (but not the same as) the VM name of the associated appliance being upgraded.
Continue with Copying Each Appliance’s /vastorage Disk (Disk 2).

Hyper-V

Download the Filr software shown below to the location where you plan to host your upgraded VMs.

IMPORTANT:Registration with Micro Focus is required to receive an email with a software-download link.

Appliance Type	Filename
Filr	Filr.x86_64-version.vhd.zip
Search	Filrsearch.x86_64-version.vhd.zip
PostgreSQL	PostgreSQL-version.vhd.zip

Extract each .vhd.zip file in the directory where you downloaded it until an ApplianceType-version.vhd archive file appears.
Create a new directory for each virtual machine you are upgrading.

As a best practice, name these directories with names that are easily associated with, but not the same as the VM name of each appliance being upgraded.
Move the filr-version.vhd archive file to the first Filr appliance-type folder and then copy the file to the remaining Filr appliance type folders.
Move the filrsearch-version.vhd archive file to the first Filrsearch appliance-type folder and then copy the file to the second Filrsearch folder.
Continue with Copying Each Appliance’s /vastorage Disk (Disk 2).

Xen

Log in to the Xen VM host server either locally or from a remote workstation.

If you are connecting from a remote Linux workstation, use the following command:

ssh -X root@host_ip_address

The -X in the command in required for the GUI installation program upon which the steps in this section are based.

Download the Filr software shown below to the Xen VM host server in the location where you plan to host your upgraded VMs.

IMPORTANT:Registration with Micro Focus is required to receive an email with a download link.

Appliance Type	Filename
Filr	Filr.x86_64-version.xen.tar.gz
Search	Filrsearch.x86_64-version.xen.tar.gz
PostgreSQL	PostgreSQL-version.xen.tar.gz

Untar each *.gz file in the directory where you downloaded it.

You can use the following command to untar the file:

tar -Sxvzf ApplianceType.x86_64-version.xen.tar.gz

An ApplianceType-version directory is created for each appliance type.
Copy and rename the ApplianceType-version directories until you have one directory for each appliance that you are upgrading.

IMPORTANT:Only change the directory names.

Do not change the names of the .raw or .xenconfig files within the directories that you have copied and renamed.

For example:
1. Rename the Filr-version directory to filr-1-30-192.168.1.61.
2. Copy the filr-1-30-192.168.1.61 directory and rename it to filr-1-30-192.168.1.62, and so on until you have a directory for each appliance you are upgrading.
3. In a similar manner, copy and rename the Filrsearch-version directory until you have two Filrsearch appliances.
Continue with Copying Each Appliance’s /vastorage Disk (Disk 2).

Citrix Xen

On a workstation with Citrix XenCenter installed, download the Filr software shown below.

IMPORTANT:Registration with Micro Focus is required to receive an email with a download link.

Appliance Type	Filename
Filr	Filr.x86_64-version.xva.tar.gz
Search	Filrsearch.x86_64-version.xva.tar.gz
PostgreSQL	PostgreSQL-version.xva.tar.gz

Using a program such as 7-Zip, extract each .xva.tar.gz file on your management workstation until an ApplianceType-version folder appears.
Continue with Copying Each Appliance’s /vastorage Disk (Disk 2).

12.2.3 Copying Each Appliance’s /vastorage Disk (Disk 2)

IMPORTANT:

VMware requires shutting down an appliance before copying a disk.

This doesn’t mean that the entire service must be down while disk copying takes place.

If you have a Filr-clustered deployment, you can minimize service interruption by shutting down one Filr or Filrsearch appliance, copying the disk, restarting the appliance and continuing with the next appliance.
On Citrix Xen you export rather than copying Disk 2.

Copying each appliance’s disk is at the heart of the upgrade process because it uses the corresponding old appliance’s configuration settings on Disk 2 to create an upgraded version of the appliance with minimal input on your part.

Disk copying can take a while, depending on disk size and the VM host environment.

Therefore, we recommend keeping service downtime to a minimum by making the copies while the Filr system is still running.

Using the tools provided by your hypervisor, copy the /vastorage (second disk) to its associated folder or directory that you created for your upgraded appliances in Downloading and Preparing Software for the Upgrades.

12.2.4 Upgrading the VMs

Shutting Down the Appliances

Shut down all of your existing appliances in the shut down order that you identified earlier:
Continue with the instructions for your VM platform:
- VMware
- Hypter-V
- Xen
- Citrix Xen

Upgrading VMware VMs

Complete the steps in Table 12-1 for each appliance that you are upgrading

Table 12-1 Upgrading a VMware VM

Page, Dialog, or Option	Do This
	1 - Launching the vSphere Client. On your management workstation, start the vSphere Client.
vSphere Client	2 - Deploying the OVF Template and naming the VM. Click File > Deploy OVF Template.
Deploy OVF Template	Click Browse.
Open	For the appliance type you are deploying, navigate to the contents of the folder that you downloaded and extracted in Downloading and Preparing Software for the Upgrades. Select and open the.ovf file.
Deploy OVF Template	Name the appliance with the same name of the folder that you created for this upgraded appliance in Step 4. Click Next. Choose the datastore and folder were you copied the appliance’s Disk 2. Click Next to accept the default for the disk format. Do not select Power on after deployment. Click Finish. The boot disk is created and the appliance is deployed as specified to this point.
	3 - Editing the VM settings.
vSphere Client	In the vSphere Client, right-click the VM you just deployed and select Edit Settings. The Virtual Machine Properties dialog displays.
Virtual Machine Properties	Set the Memory and CPU settings to match the appliance you are replacing, or increase them as planned.
	4 - Configuring Disk 2 (/vastorage)
Virtual Machine Properties	Click Add.
Add Hardware	Select Hard Disk, click Next and select Use an existing Virtual disk. Click Next > Browse, then navigate to and select the copy of Disk 2 that you made for this appliance. Click Next > Next > Finish.
	5 - Adding and Configuring Disk 3 (/var)
Virtual Machine Properties	Click Add.
Add Hardware	Select Hard Disk. Click Next > Next. Adjust the Disk Size to the same size as disk 3 (/var) on the appliance you are replacing. Under Disk Provisioning, select either: Thick Provision Eager Zeroed or Support clustering features such as Fault Tolerance Depending on the VMware version that you are running. Under Location, select Specify a datastore or Datastore cluster Click Browse. Select the datastore and folder for this appliance. Click OK. Click Next. Under the Virtual Device Node section, select SCSI. Click Next. Click Finish. If you need to add network adapters, continue with 6 - (Optional) Adding a Network Adapter. Otherwise, click OK, return to 2 - Deploying the OVF Template and naming the VM., and deploy the next appliance that you have planned for When all of your planned appliances have been deployed, continue with Deploying the Upgraded (Replacement) VMs.
	6 - (Optional) Adding a Network Adapter You can add a network adapter if your Filr deployment accesses a separate network for one or more of the following reasons: Appliance administration. NFS mount or CIFS access to the /vashare mount point. Security of Memcached. IMPORTANT:Bonding or teaming NICs is not supported with Filr.
Virtual Machine Properties	Click Add.
Add Hardware	Select Ethernet Adapter. Click Next. Under Network Connection, select the secondary network associated with the Filr installation. Click Next > Finish > OK.
vSphere Client	Repeat the steps in this table from 2 - Deploying OVF Template until all of your planned appliances have been deployed, then continue with Deploying the Upgraded (Replacement) VMs.

Upgrading Hyper-V VMs

Complete the steps in Table 12-2 for each appliance that you are upgrading.

Table 12-2 Upgrading a Hyper-V VM

Page, Dialog, or Option	Do This
	1 - Open Hyper-V Manager.
Hyper-V Host Server	Open the Hyper-V Manager.
	2 - Create a new VM.
Hyper-V Manager	In the left pane, right-click the server where you have planned to create the new virtual machine, then click New > Virtual Machine. The New Virtual Machine Wizard displays. Click Next.
Specify Name and Location	Name the appliance with the name of the directory that you created for it in Step 4. Click Next.
Specify Generation	Make sure that Generation 1 is selected. Click Next.
	3 - Specify memory
Assign Memory	In the Startup RAM field, specify the same amount of memory (in MB) of the appliance that you are replacing, or increase the memory as planned. Click Next.
	4 - Assign network adapter
Configure Networking	On the Configure Networking page, select the networking card for this VM. Click Next.
	6 - Identify the system disk
Connect Virtual Hard Disk	Select Use an existing virtual hard disk. Browse to and select the .vhd that you created for this appliance. Click Open. Click Next.
Summary	Click Finish. The VM is created and appears in the list of Virtual Machines.
	7 - Specify processors
Hyper-V Manager	In Hyper-V Manager, right-click the VM that you just created. Click Settings.
Processor	Click Processor. In the Number of virtual processors field, specify the number of processors for this VM. Click Next.
	8 - Use existing copy of hard Disk 2 (/vastorage).
Settings for VM on Host Server	Add the copy you made of Disk 2 to this VM. When you have added the disk, review the VM summary information and click Finish.
	9 - Add hard Disk 3 (/var).
Hyper-V Manager	In Hyper-V Manager, right-click the VM that you just created. Click Settings. Create a new blank virtual disk the same size as disk 3 on the appliance you are upgrading.
Summary	Review the summary information. Click Finish > OK
	10 - (Optional) Add a Network Adapter If the appliance you are upgrading has a secondary network adapter, add that now.
Hyper-V Manager	11 - Repeat until all VMs have upgraded copies Repeat the steps in this table until all of your planned appliances have been deployed, then continue with Deploying the Upgraded (Replacement) VMs.

Upgrading and Deploying Xen VMs

IMPORTANT:Unlike the other virtualization platforms, which you power on and deploy separately from the upgrade process, upgraded Xen VMs power on automatically when the upgrade process completes. You must then deploy the appliance before continuing with the next one.

Therefore, it is critical that you make sure to follow the deployment order that you identified earlier.

Complete the steps in Table 12-3 for each appliance that you are upgrading and deploying.

Table 12-3 Upgrading and Deploying a Xen VM

Page, Dialog, or Option	Do This
	1 - Launch the installer.
Terminal prompt on Xen VM Host Server	Run the following command to launch the GUI configuration menu: virt-manager NOTE:The vm-install command is deprecated from SLES 12 releases.
Create a new virtual machine	Click File > New Virtual Machine. The Create a new virtual machine wizard is displayed. Select Import existing disk image. Click Forward.
Storage path and Operating System	Browse and select the existing disk image. Select SUSE Linux Enterprise Server 12 SP4. Click Forward.
Choose Memory and CPU settings	Set the amount of memory (in MB) to match that of the VM you are upgrading. Specify the CPUs to match the number of the VM you are upgrading. Click Forward.
	2 - Name the VM.
Name of Virtual Machine	Specify the name of the appliance. Select Customize configuration before install. Click Finish.
	3 - Configure Disk 2 (/vastorage)
Hardware	Click Add Hardware at the bottom left of the screen. Select the option Select or create custom storage. Add the copy you made of Disk 2 to this VM. Select the .raw file. Click Open > Finish.
	4 - Configure Disk 3 (/var)
	Click Add Hardware at the bottom left of the screen. Select the option Select or create custom storage. Navigate to the contents of the folder for the appliance you are creating. Select the .raw file. Click Open > Finish.
	5 - (Optional) Add a Network Adapter You can add a network adapter if your Filr deployment accesses a separate network for one or more of the following reasons: Appliance administration. NFS mount or CIFS access to the /vashare mount point. Security of Memcached. IMPORTANT:Bonding or teaming NICs is not supported with Filr.
Summary	Click Network Adapters.
Network Adapters	Click New.
Virtual Network Adapter	Specify the settings for the adapter. Click Apply.
Network Adapters	Click Apply.
Summary	Click OK. The virtual machine is created, the appliance starts, and the configuration process begins.
Console	6 - Deploy the Appliance Access the appliance’s console. When prompted, enter the root and vaadmin passwords for the appliance being replaced. The upgrade process proceeds automatically. When the appliance displays the final screen in the console window, open your management browser and log in to the appliance on port 9443 as the vaadmin user.
Port 9443 Admin Console	Depending on the appliance type you are upgrading, check the following: Filrsearch: Click the Filrsearch configuration icon. Ensure that all of the settings are in place as expected. If the configuration wizard displays, there was a problem with the configuration. Resolve the configuration issues, then click Finish to reconfigure the system. Filr: Click the Filr configuration icon. Ensure that all of the settings are in place as expected. If the configuration wizard displays, there was a problem with the configuration. Resolve the configuration issues, then click Finish to reconfigure the system. Common configuration issues include: If your system is not using DNS, the most likely problem is unresolvable DNS names and missing /etc/hosts entries. If the appliance doesn’t have access to the database, ensure that all of the settings are as expected.
	7 - Upgrade the Next Appliance Return to the top of the table and repeat the process for the next appliance in your list. When all of your appliances are running, continue with Performing Post-Upgrade Tasks.

Upgrading Citrix Xen VMs

Table 12-4 Upgrading a Citrix Xen VM

Page, Dialog, or Option	Do This
	1 - Launch XenCenter.
Management Workstation	Start XenCenter.
XenCenter	Connect to the Citrix XenServer where you are deploy the upgraded appliances. Right-click the server and select Import.
	2 - Import the system disk
Locate the File you want to import	Browse to and select the .xva file on your management workstation for the appliance that you are upgrading. Click Open. Click Next.
Select the location where the imported VM will be placed	Select the XenServer. Click Next.
Select target storage	Select the storage repository for the VM. Click Import.
	3 - Select the network adapter
Select network to connect VM	Select the virtual network adapter. Click Next.
Review the import settings	Deselect Start VM(s) after import. Click Finish. IMPORTANT:Depending on network latency and other factors, it can take a while to import the system disk.
	4 - Specify Memory
	If you need to adjust the memory to the amount of memory, select the newly created VM in the left pane. Click the Memory tab. Click Edit, change the setting, and click OK.
	5 - Specify Processors
	If you need to adjust the CPUs, right-click the newly created VM in the left pane. Select Properties. Click CPU, change the setting, and click OK.
	6 - Link to Disk 2 (/vastorage)
	With the newly created VM selected in the left pane, add the copy of Disk 2 for this appliance.
	8 - Add Disk 3 (/var)
Virtual Disks	Click Add....
Add Virtual Disk	Type a disk name that reflects the appliance name and that this is disk 3. For example, Filr-1-disk-3. Change the Size field value to match that of the appliance you are replacing. Click Add.
	9 - (Optional) Add a Network Adapter You can add a network adapter if your Filr deployment accesses a separate network for one or more of the following reasons: Appliance administration. NFS mount or CIFS access to the /vashare mount point. Security of Memcached. IMPORTANT:Bonding or teaming NICs is not supported with Filr.
	With the newly created VM selected in the left pane, click the Networking tab. Select the secondary network associated with the Filr installation..
XenCenter	Repeat the steps in this table until all of your planned appliances have been upgraded, then continue with Deploying the Upgraded (Replacement) VMs.

12.2.5 Deploying the Upgraded (Replacement) VMs

IMPORTANT:

Make sure that you deploy (Start and configure) your appliances one at a time.

Attempting to start and configure multiple upgraded appliances at the same time causes timing, synchronization, and other problems.
Also make sure that you deploy the appliances in the deployment order that you identified earlier:
1. Filrsearch
2. Filr

Power on the first (or next) appliance in your deployment order list.
Access the appliance’s console.
When prompted, enter the root and vaadmin passwords for the appliance being replaced.

The upgrade process proceeds automatically.
When the appliance displays the final screen in the console window, open your management browser and log in to the appliance on port 9443 as the vaadmin user.

Depending on the appliance type you are upgrading, check the following:

Filrsearch	Filr
Click the Filrsearch configuration icon. Ensure that all of the settings are in place as expected. If the configuration wizard displays, there was a problem with the configuration. Resolve the configuration issues, then click Finish to reconfigure the system.	Click the Filr configuration icon. Ensure that all of the settings are in place as expected. If the configuration wizard displays, there was a problem with the configuration. Resolve the configuration issues, then click Finish to reconfigure the system. Common configuration issues include: If your system is not using DNS, the most likely problem is unresolvable DNS names and missing /etc/hosts entries. If the appliance doesn’t have access to the database, ensure that all of the settings are as expected.

Filrsearch

Filr

Click the Filrsearch configuration icon.
Ensure that all of the settings are in place as expected.
If the configuration wizard displays, there was a problem with the configuration.

Resolve the configuration issues, then click Finish to reconfigure the system.

Click the Filr configuration icon.
Ensure that all of the settings are in place as expected.
If the configuration wizard displays, there was a problem with the configuration.

Resolve the configuration issues, then click Finish to reconfigure the system.

Common configuration issues include:

If your system is not using DNS, the most likely problem is unresolvable DNS names and missing /etc/hosts entries.
If the appliance doesn’t have access to the database, ensure that all of the settings are as expected.

When the appliance is running, deploy the next appliance.
When all of your appliances are running, continue with Performing Post-Upgrade Tasks.

12.2.6 Performing Post-Upgrade Tasks

After upgrading to a new version of Filr, you should perform the following tasks to ensure a fully functional Filr system:

Install Your New Filr License

The newly upgraded Filr appliances have a 60-day evaluation license installed. The evaluation license is expired in most cases since it considers the day of deployment as the day when it was installed with the earlier version.

To prevent a service interruption, you must install your new license by following the instructions in Installing/Updating the Filr License in the Filr 4.3: Administrative UI Reference.

Java Heap

For optimal performance of Filr appliance, the minimum Java heap space should be 9 GB. After upgrading the appliance, the Java heap space is overwritten with the value that was set for the earlier Filr appliance. If new value is less, then ensure to update it to 9 GB or greater.

(Optional) Filr MySQL to Filr PostgreSQL Database Migration

The default database of Filr 4.0 is PostgreSQL. If you have configured Filr 3.x with default Filr MySQL database then on reindexing the Filr site, you must perform the following steps to migrate the database to PostgreSQL.

Before You Peform Migration

Ensure that the /vastorage of PostgreSQL appliance has enough disk space ( equal to or greater than the Filr MySQL appliance).
Ensure that the Filr MySQL appliance and Filr PostgreSQL appliance have uninterrupted connectivity.
When migration is in progress, do not refresh the browser or logout from the 9443 console.

Deploying PostgreSQL Appliance

Deploy the Filr PostgreSQL Appliance similar to the Filr Appliance. The binary is available under your entitlements in sld.microfocus.com location.
Open a browser and log in to the PostgreSQL appliance on port 9443 as the vaadmin user.
Under PostgreSQL Appliance Tools, click Configure PostgreSQL.
Specify a password for the “postgres” user, then click OK.

Creating User Roles for Accessing PostgreSQL

Under PostgreSQL Appliance Tools, click phpPgAdmin.
Click PostgreSQL, then specify the Username as “postgres” and password that you specified in Step 4.
Click Roles > Create role.
Specify all the required details to create a user. Ensure to select the options: Create DB? and Can login? and click Create.

Stopping Filr Service On All Nodes

Open a browser and log in to the Filr appliance on port 9443 as the vaadmin user.
Stop Filr service on all the Filr Nodes.

Migrating MySQL Database to PostgreSQL Database

Open a browser and log in to one of the Filr appliance node on port 9443 as the vaadmin user.
Under Filr Appliance Tools, click Configuration.
Click Database.
On the Database Connection page,
1. In the Database Type, select MySQL.
2. Select the option Migrate Filr MySQL Database. This option is enabled only if its a large deployment or if you have configured Filr 3.x with Filr MySQL. This displays fields to specify the PostgreSQL details.
3. Specify the PosgreSQL address and port.
4. Specify the username (role) and password that you created in Step 4.
  
  The name of the database is same as the MySQL database. This field cannot be modified.
5. Click Ok.
  
  This starts the migration process. Status is available on completion of migration.
On successful migration, Click Reconfigure Filr Server.

The Filr appliance is reconfigured and restarted.

If migration fails, refer to the /var/opt/novell/va/logs/migration.log file.
To ensure Filr Admin console is available, open a browser and log in to one of the Filr appliance node on port 8443.
Power down the Filr 3.x MySQL Appliance.
Open a browser and log in to the next Filr appliance node on port 9443 as the vaadmin user.
1. In the Database Type, select PostgreSQL.
2. Specify the PosgreSQL address and port.
3. Specify the username (role) and password that you created in Step 4.
4. Specify a name for the new database.
5. Click OK.
6. Click Reconfigure Filr Server.
To ensure Filr Admin console is available, open a browser and log in to one of the Filr appliance node on port 8443.
Repeat Step 8 to Step 9 on all the Filr nodes.

Troubleshooting Issues

Migration Fails And An Error Message Is Displayed in the 9443 Console

Refer to the /var/opt/novell/va/logs/migration.log file for the detailed information.
Resolve the issue.
Drop the PostgreSQL database.
Restart migration.

Progress of Migration Not Available

The Filr Appliance 9443 console displays the process of migration. Alternatively, you can login to the PostgreSQL appliance 9443 console > phpPgAdmin > PostgreSQL > Specify credentials, then monitor the size of the database.

If the size of the database does not change after 10 to 20 minutes, reboot the Filr appliance.
Refer to the /var/opt/novell/va/logs/migration.log file for detailed information.
Resolve the issue.
Drop the PostgreSQL database.
Restart migration.

On Successful Migration and Reconfiguration of Filr Appliance, Migration Data Is Not Listed Or 8443 Page Fails To Launch

Refer to the /var/opt/novell/va/logs/migration.log file for detailed information.
Resolve the issue.
Drop the PostgreSQL database.
Restart migration.
The issue should be resolved, launch 8443 console to verify if the page is launched successfully.

Unresolved Migration Issues

If migration continues to fail, contact the Micro Focus Customer Center with the following log files:

/var/opt/novell/va/logs/
/var/opt/novell/datamodel-service/logs

Using the Dedicated Filr Appliance to Complete the Indexing Setup

Table 12-5 Index with the Dedicated Appliance

Page, Dialog, or Option	Do This
	Open a management browser on your administrative workstation and access the Port 8443 Administration Utility on the Dedicated Filr Appliance using the following URL: https://dedicated_filr_IP_Address:8443 Where IP_Address is the IP address of the dedicated Filr appliance.
Filr Sign In Dialog	Log in as user admin with password admin, or with the alternate administrator name/password if you specified one for this appliance in . When prompted, change the user password.
Product Improvement (first login only)	Click OK.
Filr Main Window (Web access)	Click the Admin user name in the upper-right corner. Select Administration Console.
Administration Console	Click Index in the left frame.
Search Index	IMPORTANT:If you have users across multiple zones, ensure to perform reindexing on every zone. Take the first search index node out of service to rebuild it while the other is still running. Set this node as “Write Only”. For information about how to take a node out of service, see Maintaining Your High Availability Lucene Index in the Filr 4.3: Maintenance Best Practices Guide. Select Re-Index Everything in the Search Index section of the Administration Console. After the first search index node is rebuilt, put it back into service. Set the node as “Read and Write”. For information about how to take a node out of service, see Maintaining Your High Availability Lucene Index in the Filr 4.3: Maintenance Best Practices Guide. Repeat Step 1 to Step 3 for any additional search index node. To view when indexing is complete, keep the Search Index dialog box open to see the status. Alternatively, a message is displayed in either of the appserver.log files stating that reindexing is complete. To ensure that the rebuild was successful, verify that the following messages appear in the appserver.log file: Completed indexing of tree with xxx binders. Time taken for indexing is xxx.xxx msAdministrative reindexing completed on binders [1] For information about how to access the appserver.log file, see Accessing Filr System Log Files in the Filr 4.3: Administrative UI Reference.
Indexing has finished!	Click Close.
Administration Console	Click Nodes in the left frame.
Search Nodes	Change the User Mode Access option for the second Filrsearch appliance to Read and Write. Click Apply > Close. The dedicated Filr appliance will now handle all of the re-indexing workload.