The method of updating is the same for the Filr appliance, search appliance, and the database appliance.
Though it is possible to install a new search index appliance and subsequently re-index your data, Novell recommends that in a production environment you update your existing search index appliances rather than install new appliances and re-index your data. However, because of changes made to the search index since the previous release, you should re-index your Filr site after updating from Filr 1.0.
The data location for the original appliance that you are updating from must be independent of the appliance on a separate VMware, Xen, or Hyper-V hard disk, as described in Section 9.1, Prerequisites.
The update process differs depending on your virtual platform.
IMPORTANT:You can update only to the same virtual platform as the platform where you deployed your original Filr system. For example, if your original Filr system was deployed on VMware, you can update only to VMware.
Because Filr 1.0 was available only on VMware, the update process to Filr 1.0.1 is available only in a VMware environment. Updating from version 1.0 to version 1.0.1 in a Xen or Hyper-V environment is not possible.
Download the software to your management workstation.
Filr Appliance: Filr.x86_64-version.ovf.zip
Search Appliance: Filrsearch-version.ovf.zip
Database Appliance: MySQL.x86_64-version.ovf.zip
You can access the software from the Novell Customer Center (NCC). Or, you can access an evaluation version of the software from this location on the Novell Downloads page.
Extract the file that you downloaded in Step 1 on your management workstation until one of the following folders appears, depending on which appliance you are updating:
Filr-version
Filrsearch-version
MySQL-version
In the vSphere client, click
> .Browse to and select the .ovf file in the Filr-version file folder.
Click
.Click
again.In the
field, rename the Filr appliance to a name of your choosing, then click .Click
to accept the default for the disk format.Click
.Shut down the appliance you are updating.
IMPORTANT:When shutting down the appliance, be aware of the following limitations:
In a large deployment, always bring down Filr first before you bring down the search appliance or database appliance. When restarting, start the Filr appliance last.
In a clustered deployment, all instances of the previous Filr or search index appliance must be shut down before a single instance of the updated Filr or search index appliance is started.
Rolling upgrades (updating one Filr or search index server while another continues to serve clients) are not supported when updating from Filr 1.0 to Filr 1.0.1 in a clustered environment. This issue does not affect small or non-clustered large installations.
When you shut down the appliance, use the Section 7.9, Shutting Down and Restarting the Novell Appliance), or use the init 0 command from the appliance console when you are logged in as root.
button from the Novell Appliance Configuration screen (as described inBefore you power on the new appliance, point it to the VMware data disk that your previous appliance used. For example, for ESX 5.x:
In the vSphere client, right-click the virtual machine that you just created, and for which you want to create secondary storage, then click
.The Virtual Machine Properties page is displayed.
On the
tab, click .The Add Hardware dialog box is displayed.
Select
, then click .Select
, then click .Next to the
field, click , then browse to and select the datastore or datastore cluster that you selected for the appliance that you are updating from.Click
.Click
.In the
section, select from the drop-down list.In the
section, select , select , then click .Click
.Click
.WARNING:If for any reason you need to delete the new or the previous appliance, you must unlink (remove) the disk. Otherwise, the disk is deleted. Having the disk linked to the original or to the new appliance does not provide the expected safeguard. In other words, if the disk is linked to multiple appliances and you delete one of them, the disk is deleted despite the remaining link.
Increase the amount of memory that VMware allocates for the Filr appliance.
The default of 8 GB is the recommended minimum amount of memory for a large deployment. Novell also recommends 2 CPUs.
For an all-in-one deployment, you should increase the default to at least 12 GB of memory and 4 CPUs.
Small deployments require more CPUs and memory because in a small deployment, all components are running on a single virtual machine.
IMPORTANT:When you increase or decrease server memory for the Filr appliance or the search index appliance, you should also modify the Java heap size, as described in Section 4.10, Changing the Java JDK Configuration Settings and Section 5.0, Configuring and Maintaining the Search Index Appliance.
At least half of the memory should be dedicated to the Java heap. You cannot adjust the Java heap until after the appliance is installed.
In the Virtual Machine Properties window, select
, then increase the setting to a suitable size for your environment.Click
to exit the Virtual Machine Properties window.Power on the appliance (virtual machine).
IMPORTANT:In a large installation, you must power on the search index and database appliances before you power on the Filr appliance. These appliances must be running at the time you power on the Filr appliance.
Click the
tab. After the appliance starts, accept the license agreement.Specify the same configuration information that you did when installing the original appliance.
If you entered incorrect configuration information, you can log in as root and use the VACONFIG utility. For more information, see Section D.1, Using VACONFIG to Modify Network Information.
Click
.The data storage location that you used when installing the original appliance should already be selected. If it is not, select it.
For more information about the type of data that is stored here, see Data Storage for the Appliance.
Click
.(Filr appliance only) If you configured Filr for a clustered environment, you must select
. Then click .For more information about possible configurations when running Filr in a clustered environment, see Section 1.8, Recommended Hardware Configurations Based on System Performance.
Click
.A message indicating that the installation was successful is displayed.
In a browser, navigate to the following URL:
https://ip_address:9443
Use the IP address or DNS name of the server that you specified during the appliance installation.
Log in to the appliance using the vaadmin user and the password that you set.
The Novell Filr Appliance, Novell MySQL Appliance, or Novell Filr Search Appliance landing page is displayed, depending on which appliance you are updating.
(Conditional) If you are updating the search appliance:
Click the
icon.The Search Settings page is displayed.
Ensure that all of the settings are set to your desired specifications.
(Conditional) If you are updating the database appliance:
Click the
icon.Verify that the database is populated.
(Conditional) If you are updating the Filr appliance:
Click the
icon.The Filr Configuration Wizard is displayed.
Click
to update the appliance.Depending on the size of your database, the update process can take over an hour to complete. For example, a 14 GB database might take 30 minutes to complete, and a 30 GB database might take an hour or more.
Continue with Section 9.3, Rebuilding the Search Index.
IMPORTANT:You can update only to the same virtual platform as the platform where you deployed your original Filr system. For example, if your original Filr system was deployed on VMware, you can update only to VMware.
Because Filr 1.0 was available only on VMware, the update process to Filr 1.0.1 is available only in a VMware environment. Updating from version 1.0 to version 1.0.1 in a Xen or Hyper-V environment is not possible.
The following steps are provided for future reference, when updating from Filr 1.0.1 to a future version.
Log in to the host server either locally or from a remote workstation.
You can use the following command to log in to the host server from a remote workstation on Linux:
ssh -X root@host_ip_address
You must use the -X in the command in order to display the GUI installation program. The steps in this section use the GUI installation program to configure the server.
Navigate to the /var/lib/xen/images directory on the host server.
Create a new directory inside the images directory where you can download the Filr software. The name of this directory must be the same as the name that you plan to use for your Filr virtual appliance. For example, if you plan to name the Filr appliance Filr1, the name of this new directory must also be Filr1.
Change to the directory that you just created. For example, /var/lib/xen/images/Filr1.
Download the software to the current directory on the host server. For example:
/var/lib/xen/images/Filr1
Filr Appliance: Filr.x86_64-version.xen.tar.gz
Search Appliance: Filrsearch-version.xen.tar.gz
Database Appliance: MySQL.x86_64-version.xen.tar.gz
You can access the software from the Novell Customer Center (NCC). Or, you can access an evaluation version of the software from this location on the Novell Downloads page.
Untar the file that you downloaded in Step 5 in the directory where you downloaded it.
You can use the following command to untar the file:
tar -Sxvzf Filr.x86_64-version.xen.tar.gz
A filr-version directory is created, which contains a .raw file that you will use to run the virtual image. This process can take a few minutes.
From the host server, run the following command to launch the GUI configuration menu:
vm-install
The Create a Virtual Machine wizard is displayed.
Click
.Select
, then click .Leave
selected, then click .Rename the virtual machine by clicking Filr1.
, and specifying a new name in the field. Then click . For example,Configure the amount of memory and number of CPUs that Xen allocates for the Filr appliance.
On the Summary page, click
, then specify the following information:Available Memory: Displays the amount of available memory that is available on the host server.
Initial Memory: 8 GB is the recommended minimum for a large deployment.
For an all-in-one deployment, you should increase the default to at least 12 GB of memory.
Small deployments require more memory because in a small deployment, all components are running on a single virtual machine.
IMPORTANT:When you increase or decrease server memory for the Filr appliance or the search index appliance, you should also modify the Java heap size, as described in Section 4.10, Changing the Java JDK Configuration Settings and Section 5.0, Configuring and Maintaining the Search Index Appliance.
At least half of the memory should be dedicated to the Java heap. You cannot adjust the Java heap until after the appliance is installed.
Maximum Memory: Set this to the same value as you set for Initial Memory.
Available Processors: Displays the number of available processors on the host server.
Virtual Processors: Specify 2 CPUs for a large deployment and 4 CPUs for a small deployment. At least half of the memory should be dedicated to the Java heap. (Java heap is set in the Filr configuration.)
Small deployments require more CPUs because in a small deployment, all components are running on a single virtual machine.
Click
.Configure the bootable disk image:
On the Summary page, click
s.Click
.On the Virtual Disk page, specify the following information:
Source: Click .raw file that you untared in Step 6.
, then browse to theProtocol: Select
.Size (GB): The default size is 40.1 GB. This cannot be changed.
Create Sparse Image File: This option is not available.
Read-Only Access: Do not select this option.
Click OK.
Shut down the appliance that you are updating.
IMPORTANT:When shutting down the appliance, be aware of the following limitations:
In a large deployment, always bring down Filr first before you bring down the search appliance or database appliance. When restarting, start the Filr appliance last.
In a clustered deployment, all instances of the previous Filr or search index appliance must be shut down before a single instance of the updated Filr or search index appliance is started.
Rolling upgrades (updating one Filr or search index server while another continues to serve clients) are not supported when updating from Filr 1.0 to Filr 1.0.1 in a clustered environment. This issue does not affect small or non-clustered large installations.
When you shut down the appliance, use the Section 7.9, Shutting Down and Restarting the Novell Appliance), or use the init 0 command from the appliance console when you are logged in as root.
button from the Novell Appliance Configuration screen (as described inBefore you power on the new appliance, point it to the Xen data disk that your previous appliance used:
On the Disks page, click
.On the Virtual Disk page, specify the following information:
Source: This field should already contain the path to the .raw file that will be created when the virtual machine is created. If desired, you can rename the disk in the source field from disk0 to a name of your choosing.
Protocol: Select
.Size (GB): Specify the amount of hard disk space that you want to allocate. The recommended minimum is 100 GB.
Create Sparse Image File: Select this option.
Read-Only Access: Do not select this option.
WARNING:If for any reason you need to delete the new or the previous appliance, you must unlink (remove) the disk. Otherwise, the disk is deleted. Having the disk linked to the original or to the new appliance does not provide the expected safeguard. In other words, if the disk is linked to multiple appliances and you delete one of them, the disk is deleted despite the remaining link.
Power on the appliance (virtual machine).
IMPORTANT:In a large installation, you must power on the search index and database appliances before you power on the Filr appliance. These appliances must be running at the time you power on the Filr appliance.
Click the
tab. After the appliance starts, accept the license agreement.Specify the same configuration information that you did when installing the original appliance.
If you entered incorrect configuration information, you can log in as root and use the VACONFIG utility. For more information, see Section D.1, Using VACONFIG to Modify Network Information.
Click
.The data storage location that you used when installing the original appliance should already be selected. If it is not, select it.
For more information about the type of data that is stored here, see Data Storage for the Appliance.
Click
.(Filr appliance only) If you configured Filr for a clustered environment, you must select
. Then click .For more information about possible configurations when running Filr in a clustered environment, see Section 1.8, Recommended Hardware Configurations Based on System Performance.
Click
.A message indicating that the installation was successful is displayed.
In a browser, navigate to the following URL:
https://ip_address:9443
Use the IP address or DNS name of the server that you specified during the appliance installation.
Log in to the appliance using the vaadmin user and the password that you set.
The Novell Filr Appliance, Novell MySQL Appliance, or Novell Filr Search Appliance landing page is displayed, depending on which appliance you are updating.
(Conditional) If you are updating the Filr appliance:
Click the
icon.The Filr Configuration Wizard is displayed.
Click
to update the appliance.(Conditional) If you are updating the search appliance:
Click the
icon.The Search Settings page is displayed.
Ensure that all of the settings are set to your desired specifications.
(Conditional) If you are updating the database appliance:
Click the
icon.Verify that the database is populated.
Continue with Section 9.3, Rebuilding the Search Index.
IMPORTANT:You can update only to the same virtual platform as the platform where you deployed your original Filr system. For example, if your original Filr system was deployed on VMware, you can update only to VMware.
Because Filr 1.0 was available only on VMware, the update process to Filr 1.0.1 is available only in a VMware environment. Updating from version 1.0 to version 1.0.1 in a Xen or Hyper-V environment is not possible.
The following steps are provided for future reference, when updating from Filr 1.0.1 to a future version.
Log in to the host server either locally or from a remote workstation.
You can use Windows Remote Desktop to log in to the host server from a remote workstation.
Create a new directory in the location where you want each virtual machine to reside (for example, C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks). In a later step, you will download the Filr software to this directory.
As a best practice, give this directory the same name that you plan to use for your Filr virtual appliance. For example, if you plan to name the Filr appliance Filr1, the name of this new directory should also be Filr1.
Download the software to your management workstation.
Filr Appliance: Filr.x86_64-version.ovf.zip
Search Appliance: Filrsearch-version.ovf.zip
Database Appliance: MySQL.x86_64-version.ovf.zip
You can access the software from the Novell Customer Center (NCC). Or, you can access an evaluation version of the software from this location on the Novell Downloads page.
Extract the file that you downloaded in Step 3 to a the directory on the host server that you created in Step 2.
Open the Hyper-V Manager.
In Hyper-V Manager, right-click the disk name in the Action Pane where you want to create the new virtual machine, then click
> .The New Virtual Machine Wizard is displayed.
Review the Before You Begin page, then click
.In the Filr1.
field, specify a name for the new virtual machine. For example,Click
.In the
field, specify the amount of memory (in MB) to allocate to the virtual machine. 8 GB (8192 MB) is the recommended minimum for a large deployment of Filr.For an all-in-one (small) deployment, you should increase the default to at least 12 GB (12288 MB) of memory. Small deployments require more memory because in a small deployment, all components are running on a single virtual machine.
IMPORTANT:When you increase or decrease server memory for the Filr appliance or the search index appliance, you should also modify the Java heap size, as described in Section 4.10, Changing the Java JDK Configuration Settings and Section 5.0, Configuring and Maintaining the Search Index Appliance.
At least half of the memory should be dedicated to the Java heap. You cannot adjust the Java heap until after the appliance is installed.
Click
.On the Configure Networking page, select the networking card of your choice, then click
.Configure the bootable disk image:
On the Connect Virtual Hard Disk page, select .vhd file that was in the downloaded .zip file that you extracted in Step 4.
, then browse to theClick
to select the file, then click .Click
.WARNING:If for any reason you need to delete the new or the previous appliance, you must unlink (remove) the disk. Otherwise, the disk is deleted. Having the disk linked to the original or to the new appliance does not provide the expected safeguard. In other words, if the disk is linked to multiple appliances and you delete one of them, the disk is deleted despite the remaining link.
Shut down the appliance that you are updating.
IMPORTANT:When shutting down the appliance, be aware of the following limitations:
In a large deployment, always bring down Filr first before you bring down the search appliance or database appliance. When restarting, start the Filr appliance last.
In a clustered deployment, all instances of the previous Filr or search index appliance must be shut down before a single instance of the updated Filr or search index appliance is started.
Rolling upgrades (updating one Filr or search index server while another continues to serve clients) are not supported when updating from Filr 1.0 to Filr 1.0.1 in a clustered environment. This issue does not affect small or non-clustered large installations.
When you shut down the appliance, use the Section 7.9, Shutting Down and Restarting the Novell Appliance), or use the init 0 command from the appliance console when you are logged in as root.
button from the Novell Appliance Configuration screen (as described inPower on the appliance (virtual machine).
IMPORTANT:In a large installation, you must power on the search index and database appliances before you power on the Filr appliance. These appliances must be running at the time you power on the Filr appliance.
Click the
tab. After the appliance starts, accept the license agreement.Specify the same configuration information that you did when installing the original appliance.
If you entered incorrect configuration information, you can log in as root and use the VACONFIG utility. For more information, see Section D.1, Using VACONFIG to Modify Network Information.
Click
.The data storage location that you used when installing the original appliance should already be selected. If it is not, select it.
For more information about the type of data that is stored here, see Data Storage for the Appliance.
Click
.(Filr appliance only) If you configured Filr for a clustered environment, you must select
. Then click .For more information about possible configurations when running Filr in a clustered environment, see Section 1.8, Recommended Hardware Configurations Based on System Performance.
Click
.A message indicating that the installation was successful is displayed.
In a browser, navigate to the following URL:
https://ip_address:9443
Use the IP address or DNS name of the server that you specified during the appliance installation.
Log in to the appliance using the vaadmin user and the password that you set.
The Novell Filr Appliance, Novell MySQL Appliance, or Novell Filr Search Appliance landing page is displayed, depending on which appliance you are updating.
(Conditional) If you are updating the Filr appliance:
Click the
icon.The Filr Configuration Wizard is displayed.
Click
to update the appliance.(Conditional) If you are updating the search appliance:
Click the
icon.The Search Settings page is displayed.
Ensure that all of the settings are set to your desired specifications.
(Conditional) If you are updating the database appliance:
Click the
icon.Verify that the database is populated.
Continue with Section 9.3, Rebuilding the Search Index.