2.2 Installing Separate Appliances for a Large Installation

In a large installation, the Filr software, the MySQL database, and the search index each run as a separate appliance.

Running the Filr software, the MySQL database, and the search index as separate appliances allows each component to have access to more server memory, disk space, and CPU resources. There can be multiple Filr appliances and multiple search index appliances. There can be only one database appliance.

You should have already installed the Filr appliance, as described in Section 2.1, Installing the Filr Appliance. The following sections describe how to install the search index appliance and the MySQL database appliance. If you have an existing MySQL database that you want to use as the Filr database, you must make certain changes on the database to configure it to work with Filr.

You must configure the MySQL database appliance to change the database administrator password before you configure the Filr appliance for the first time.

2.2.1 Installing the Search Index Appliance

  1. Download the Lucene search index software (Filrsearch-version.ovf.zip) to your management workstation.

    You can access the file from the Novell Downloads page.

  2. Extract the Filrsearch-version.ovf.zip file on your management workstation until the Filrsearch-version file folder appears.

  3. In the vSphere client, click File > Deploy OVF Template.

  4. Browse to and select the .ovf file in the Filrsearch-version file folder.

  5. Click Next.

  6. Click Next again.

  7. In the Name field, rename the Filr appliance to a name of your choosing, then click Next.

  8. Click Next to accept the default for the disk format.

  9. Click Finish.

  10. Adjust the amount of hard disk to allocate for the appliance boot partition (Hard Disk 1). This storage location is primarily for log files.

    1. In the vSphere client, right-click the virtual machine that you just created for which you want to increase the amount of hard disk space allocated to the boot partition, then click Edit Settings.

      The Virtual Machine Properties page is displayed.

    2. Select Hard disk 1, then in the Disk Provisioning section, increase the value in the Provisioned Size field. Novell recommends 25 GB.

      For more information about these storage requirements, see Table 1-2, Search Index Appliance Storage.

  11. Create a separate VMware hard disk for the appliance (Hard Disk 2). This is the /vastorage location where the following types of files are stored:

    • Search index data files

    • Configuration files that are used for appliance upgrades

    • Ganglia files that are used to store monitoring information

    For more information about these storage requirements, see Table 1-2, Search Index Appliance Storage.

    IMPORTANT:If you do not create a separate VMware hard disk as described here, you cannot update to a new version of the appliance.

    1. On the Virtual Machine Properties page, on the Hardware tab, click Add.

      The Add Hardware dialog box is displayed.

    2. Select Hard Disk, then click Next.

    3. Leave Create a new virtual disk selected, then click Next.

    4. Specify the amount of hard disk space that you want to allocate. Novell recommends a minimum of 25 GB. The separate VMware hard disk might require more disk space, depending on the number and size of files in your environment.

    5. In the Disk Provisioning section, select either Thick Provision Eager Zeroed or Support clustering features such as Fault Tolerance, depending on the VMware version that you are running.

    6. In the Location section, select Specify a datastore or datastore cluster, then click Browse.

    7. Select a datastore, then click OK.

    8. Click Next.

    9. In the Virtual Device Node section, select SCSI (1:0) from the drop-down list.

    10. In the Mode section, select Independent, then select Persistent, then click Next.

    11. Click Finish.

  12. Increase the amount of memory that VMware allocates for the appliance.

    The default is 4 GB. This default is appropriate for a system that has a few hundred to 1,000 users. You should increase this if your user count exceeds 1,000. Novell also recommends 2 CPUs.

    1. In the Virtual Machine Properties window, select Memory, then increase the setting to a suitable size for your environment.

      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.

      You cannot do this until after the appliance is installed.

    2. Click OK to exit the Virtual Machine Properties window.

  13. Power on the appliance.

    IMPORTANT:If you are planning to use a separate VMware hard disk to store your Filr files, do not power on the appliance until you have created the hard disk, as described in Step 11.

  14. Click the Console tab. After the appliance starts, select your preferred keyboard layout in the Keyboard Language drop-down, then accept the license agreement.

    You can change the language the license agreement is displayed in from the License Language drop-down.

  15. Specify the following network information:

    Root password and confirmation: The root password for your Search Index appliance.

    Vaadmin password and confirmation: The preferred user to use when logging in to the appliance.

    Hostname: The fully qualified DNS host name associated with the appliance’s IP address. For example, myFilr.mynetwork.example.com.

    IP Address: The static IP address for the appliance. For example, 172.17.2.3.

    Network Mask: The network mask associated with the appliance’s IP address. For example, 255.255.255.0.

    Gateway: The IP address of the gateway on the subnet where your Filr virtual appliance is located. For example, 172.17.2.254.

    DNS Servers: The IP address of a primary DNS server for your network. For example, 172.17.1.1.

    NTP Server: The IP address or DNS name of the reliable external Network Time Protocol (NTP) server your OES server uses. For example, time.example.com.

    Region: Your local region.

    Time Zone: Your local time zone.

    NOTE:If after installation you are not able to access the appliance and you need to change any of these settings, you can use the VACONFIG utility from the command prompt. For more information about how to access the VACONFIG utility, see Section B.1, Using VACONFIG to Modify Network Information.

  16. Click Next.

  17. Select the data storage location. This is the location (/vastorage) where information specific to the appliance is stored and is used when the appliance is upgraded. Each appliance has its own /vastorage location.

    • Hard Disk (recommended): This option is recommended for both small and large deployment scenarios. You should have already assigned a hard disk to the virtual machine before you choose this option, as described in Step 11. If you have not already assigned a hard disk, click Power Off Virtual Machine, modify the virtual machine settings to add a hard disk, then power on the virtual machine.

    • Remote NFS: Do not select this option when installing the search index appliance. The search index appliance is not supported with Remote NFS. If you plan to have multiple Lucene index servers, understand that load balancing is not supported between index servers. Rather, the purpose of having multiple Lucene index servers is to provide fault tolerance or backup in the event that one index server fails.

    For more information about the type of data that is stored here, see Data Storage for the Appliance.

  18. Click Next.

  19. Specify the following options for hard disk data storage location:

    Hard Drive: Select the hard drive you are using.

    If you created a secondary VMware hard disk for this appliance as described in Step 11, it is automatically detected and sdb is displayed as the hard drive. Accept the defaults for the other options on this page and skip to Step 20.

    Use an existing partition: Select this option to use an existing partition.

    Create a new partition: Select this option to create a new partition.

    Partition size: Specify the partition size.

    Filesystem type: Specify the type of file system. If you are sharing this file system between multiple appliances (in a clustered environment), you must select ocfs2 as the file system type when using a hard disk as the data storage location.

  20. Click Configure.

    The appliance might take a few minutes to install. When the installation is complete, you see a message telling you that the appliance is now ready to configure.

  21. (Optional) Create a cluster of Lucene index server appliances (no more than two is recommended). Having multiple Lucene index server appliances provides fault tolerance or backup in the event that one index server fails.

    1. Install another Lucene index server appliance, as described in this section (Section 2.2.1, Installing the Search Index Appliance).

    2. Log in to the Filr appliance administration and configure Lucene for High Availability, as described in Section 4.5, Changing Your Search Index Configuration.

  22. Set a password for the search index appliance. You can also change other configuration options for the search index appliance.

    For information about how to change the search index appliance password and other configuration options, see Section 5.0, Configuring and Maintaining the Search Index Appliance.

  23. Continue with installing the database appliance, as described in Section 2.2.2, Installing the MySQL Database Appliance.

2.2.2 Installing the MySQL Database Appliance

If you already have a MySQL database server that you want the Filr appliance to use, you can skip this section and continue with Section 2.2.3, Configuring an Existing MySQL Database.

To install the MySQL database appliance:

  1. Download the MySQL database software (MySQL.x86_64-version.ovf.zip) to your management workstation.

    You can access the file from the Novell Downloads page.

  2. Extract the MySQL.x86_64-version.ovf.zip file on your management workstation until the MySQL-version file folder appears.

  3. In the vSphere client, click File > Deploy OVF Template.

  4. Browse to and select the .ovf file in the MySQL-version file folder.

  5. Click Next.

  6. Click Next again.

  7. In the Name field, rename the Filr appliance to a name of your choosing, then click Next.

  8. Click Next to accept the default for the disk format.

  9. Click Finish.

  10. Adjust the amount of hard disk to allocate for the appliance boot partition (Hard Disk 1). This storage location is primarily for log files.

    1. In the vSphere client, right-click the virtual machine that you just created for which you want to increase the amount of hard disk space allocated to the boot partition, then click Edit Settings.

      The Virtual Machine Properties page is displayed.

    2. Select Hard disk 1, then in the Disk Provisioning section, increase the value in the Provisioned Size field. Novell recommends 25 GB.

      For more information about these storage requirements, see Table 1-3, MySQL Database Appliance Storage.

  11. Identify the location where you want to store your Filr files. This can be an NFS mount point or a VMware hard disk.

    • If you choose to have a VMware hard disk, continue with Step 12. (Recommended)

    • If you choose to have an NFS mount point, continue with Step 13. You will make this selection during the initial configuration of the appliance.

  12. Create a separate VMware hard disk for the appliance (Hard Disk 2). This is the /vastorage location where the following types of files are stored:

    • MySQL database files

    • Configuration files that are used for appliance upgrades

    • Ganglia files that are used to store monitoring information

    For more information about these storage requirements, see Table 1-3, MySQL Database Appliance Storage.

    IMPORTANT:If you do not create a separate VMware hard disk as described here, you cannot update to a new version of the appliance.

    1. On the Virtual Machine Properties page, on the Hardware tab, click Add.

      The Add Hardware dialog box is displayed.

    2. Select Hard Disk, then click Next.

    3. Specify the amount of hard disk space that you want to allocate. Novell recommends a minimum of 25 GB. The separate VMware hard disk might require more disk space, depending on the number and size of files in your environment.

    4. Leave Create a new virtual disk selected, then click Next.

    5. In the Disk Provisioning section, select either Thick Provision Eager Zeroed or Support clustering features such as Fault Tolerance, depending on the VMware version that you are running.

    6. In the Location section, select Specify a datastore or datastore cluster, then click Browse.

    7. Select a datastore, then click OK.

    8. Click Next.

    9. In the Virtual Device Node section, select SCSI (1:0) from the drop-down list.

    10. In the Mode section, select Independent, then select Persistent, then click Next.

    11. Click Finish.

  13. Increase the amount of memory that VMware allocates for the appliance.

    The default is 4 GB. This default is appropriate for a system that has a few hundred to a thousand users. Novell also recommends 2 CPUs.

    1. In the Virtual Machine Properties window, select Memory, then increase this setting to a suitable size for your environment.

      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.

      You cannot do this until after the appliance is installed.

    2. Click OK to exit the Virtual Machine Properties window.

  14. Power on the appliance.

    IMPORTANT:If you are planning to use a separate VMware hard disk to store your Filr files, do not power on the appliance until you have created the hard disk, as described in Step 12.

  15. Click the Console tab. After the appliance starts, select your preferred keyboard layout in the Keyboard Language drop-down, then accept the license agreement.

    You can change the language the license agreement is displayed in from the License Language drop-down.

  16. Specify the following network information:

    Root password and confirmation: The root password for your database appliance.

    Vaadmin password and confirmation: The preferred user to use when logging in to the appliance.

    Hostname: The fully qualified DNS host name associated with the appliance’s IP address. For example, myFilr.mynetwork.example.com.

    IP Address: The static IP address for the appliance. For example, 172.17.2.3.

    Network Mask: The network mask associated with the appliance’s IP address. For example, 255.255.255.0.

    Gateway: The IP address of the gateway on the subnet where your database appliance is located. For example, 172.17.2.254.

    DNS Servers: The IP address of a primary DNS server for your network. For example, 172.17.1.1.

    NTP Server: The IP address or DNS name of the reliable external Network Time Protocol (NTP) server your OES server uses. For example, time.example.com.

    Region: Your local region.

    Time Zone: Your local time zone.

    NOTE:If after installation you are not able to access the appliance and you need to change any of these settings, you can use the VACONFIG utility from the Filr command prompt. For more information about how to access the VACONFIG utility, see Section B.1, Using VACONFIG to Modify Network Information.

  17. Click Next.

  18. Select the data storage location. This is the location (/vastorage) where information specific to the appliance is stored and is used when the appliance is upgraded. Each appliance has its own /vastorage location.

    • Hard Disk (recommended): This option is recommended for both small and large deployment scenarios. You should have already assigned a hard disk to the virtual machine before you choose this option, as described in Step 12. If you didn’t, power off this virtual machine, modify the virtual machine settings to add a hard disk, then power on the virtual machine.

    • Remote NFS: Use a remote NFS location only in a large deployment scenario, where you plan to configure all Filr servers (Filr, Filr Search, and MySQL) as separate virtual machines. You must export the remote directory before you choose this option. Also, set the rw and no_root_squash options on the remote directory.

      Remote NFS is not supported with Windows.

    For more information about the type of data that is stored here, see Data Storage for the Appliance.

  19. Click Next.

  20. (Conditional) If you selected Hard Disk in Step 18, specify the following options:

    Hard Drive: Select the hard drive you are using.

    If you created a secondary VMware hard disk for this appliance as described in Step 11, it is automatically detected and sdb is displayed as the hard drive. Accept the defaults for the other options on this page and skip to Step 22.

    Use an existing partition: Select this option to use an existing partition.

    Create a new partition: Select this option to create a new partition.

    Partition size: Specify the partition size.

    Filesystem type: Specify the type of file system.

  21. (Conditional) If you selected Remote NFS in Step 18, specify the following options:

    NFS Server Hostname: Specify the hostname of the NFS server.

    Windows servers are not supported.

    Remote Directory: Specify the path to the remote directory.

  22. Click Configure.

    The appliance might take a few minutes to install. When the installation is complete, you see a message telling you that the appliance is now ready to configure.

  23. Configure the MySQL database appliance to change the database administrator password, as described in Section 6.0, Configuring and Maintaining the MySQL Database Appliance.

    IMPORTANT:You must do this before you configure the Filr appliance for the first time.

  24. Continue with Section 3.0, Configuring Filr for the First Time.

2.2.3 Configuring an Existing MySQL Database

When configuring Filr to use an existing MySQL database rather than the database appliance, Filr supports MySQL 5.0.96 through 5.5.x.

IMPORTANT:Filr cannot be used with MySQL 5.6 and later.

If you want to use an existing MySQL database as the Filr database, you must make the following changes on the database to configure it to work with Filr:

  1. Make the following changes on the MySQL server:

    [client] 
    default-character-set = utf8
    
    [mysqld]
    character-set-server = utf8
    max_connections = 900
    transaction-isolation = READ-COMMITTED
    expire_logs_days = 7
    

    The expire_logs_days setting is optional, but is recommended. It is used to clean up mysql-bin-* files. If these files are not cleaned up on a regular basis, they can begin to consume a significant amount of disk space in the vastorage directory.

  2. Uncomment the InnoDB tables section.

  3. Increase the buffer pool size to approximately 60 percent of the amount of RAM that has been allocated to the dedicated MySQL server. For example, a dedicated MySQL server with 4 GB of RAM should have a buffer pool size of 2560 MB, as follows:

    innodb_buffer_pool_size = 2560M
    
  4. Continue with Section 3.0, Configuring Filr for the First Time.