Upgrading a Multi-Server Environment (2.8 or newer)

Owned by Jeremy Sommer (Deactivated)
Last updated: Jan 27, 2020 by Steinar Skjerven
2 min read

On the Primary Locator server:


If using Microsoft SQL Server, complete the installer normally, then proceed to the Secondary Server section.

If using PostgreSQL, follow these steps:

  1. Perform a full PostgreSQL backup by executing a command similar to this:

    "%ProgramFiles%\ayfie\Locator \PostgreSQL\bin\pg_dump.exe" -i -h localhost -p 5432 -U postgres -F c -f "F:\Backups\Locator.bak" Locator 

    (where "F:\Backups\Locator.bak" is the path to the backup file)


  2. Backup the custom configuration files (although they should not be overwritten by the upgrade):

    copy “%ProgramData%\ayfie\Locator\Database\pg_hba.conf” F:\Backups
    copy %ProgramData%\ayfie\Locator\Database\postgresql.conf F:\Backups


  3. Proceed to upgrade. During the upgrade, the Locator IndexBuilder service will be stopped, upgraded and re-started. If there many pending conversions the system may be CPU bound, slowing down the upgrade process. It’s safe to temporarily stop the Index Builder service until the system is completely upgraded.

  4. Verify that the custom configuration in “%ProgramData%\ayfie\Locator\Database\pg_hba.conf” and %ProgramData%\ayfie\Locator\Database\postgresql.conf are still there. These configurations were originally set in Installing/configuring a Primary Server in a multi-server environment

On the Secondary Locator server:

Note: If the secondary server is a SolrCloud node and part ot the ViaWorksCloud collection, make sure your schema_overrides.xml and solrconfig_overrides.xml in %ProgramData%\ayfie\Locator\Solr\configsets\ViaWorksCloud\conf are identical to these files on the primary node. Also make sure schema.xml and solrconfig.xml exists. There is a bug in Locator 2.11 SR2 where these files aren't created on install.

If using Microsoft SQL Server, complete the installer normally.

If using Postgres, follow these steps:

  1. From an elevated command prompt, first make a backup copy and then edit the file %ProgramFiles%\ayfie\Locator\Config\DataAccess.config
    Essentially we will revert the changes back to default settings:

    1. Change the value of the “ViaDatabaseServer” key to 127.0.0.1. Save the current value as you need it for a later step.

    2. Remove this line before the </appSettings> line:

      <add key="LicensingServiceServer" value="      <IPv4_addr>" />


  2. Start the Locator.Database.Service.

  3. Proceed with the Locator upgrade.


  4. The upgrade will enable and start all of the services. Some of the services below might not exist, depending on which component was selected during install. Stop all Locator services again in this order if exist:
    1. All Fetch Services, in any order (e.g. ayfie/Locator FileServer Fetch Service, ayfie/Locator Exchange Fetch Service, etc.)
    2. Locator Index Service
    3. Locator IndexBuilder Service 
    4. Locator Licensing Service
    5. Locator Database Service

  5. From an elevated command prompt, first make a backup copy and then edit the file %ProgramFiles%\ayfie\Locator\Config\DataAccess.config

    1. Change the value of the “ViaDatabaseServer” key back to reflect the IPv4 address of the Primary Locator server as opposed to the default value of 127.0.0.1.

    2. Edit the ZookeeperHost value from "localhost:9983" to be the host name of the primary server, eg: "hostname:9983"

    3. Edit the LicensingServiceServer value from "localhost" to the host name of the primary server.

  6. Edit the Rest Service web.config: "[Drive]:\Program Files\ayfie\Locator\RestService\web.config": change <add key="LicenseHostName" value="localhost" /> to <add key="LicenseHostName value="FQDN_of_primary_server" />

  7. Disable the appropriate services by selecting the appropriate option for your setup below:
    1. If on a search server: Disable all ayfie/Locator services except Locator Index Service.
    2. If on a fetch server: Disable all ayfie/Locator services except ayfie/Locator Fetch Services.
    3. If on a search and fetch server: Disable all ayfie/Locator services except Locator Index Service and ayfie/Locator Fetch Services.
  8. Start all of the ayfie/Locator services that were not set as disabled in previous step.

ayfie