Upgrading a Multi-Server Environment (2.7 or older to 2.8 or newer)

On the Primary ViaWorks server:

1. Perform a full PostgreSQL backup by executing a command similar to this:
   
   "%ProgramFiles%\Virtual Works\ViaWorks\PostgreSQL\bin\pg_dump.exe" -i -h localhost -p 5432 -U postgres -F c -f "F:\Backups\viaworks.bak" ViaWorks
   
   (where "F:\Backups\viaworks.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%\Virtual Works\ViaWorks\Database\pg_hba.conf” F:\Backups
   copy %ProgramData%\Virtual Works\ViaWorks\Database\postgresql.conf F:\Backups

   
   

3. Proceed to upgrade. During the upgrade, the ViaWorksIndexBuilder 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.

On the Secondary ViaWorks server:

1. The upgrade of the secondary server will fail if the ViaWorks.Database.Service is not running.

   
   

2. From an elevated command prompt, first make a backup copy and then edit the file %ProgramFiles%\Virtual Works\ViaWorks\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.
      
      

   2. Remove this line before the </appSettings> line:
      
      <add key="LicensingServiceServer" value="<IPv4_addr>" />
      

      
      

3. Start the ViaWorks.Database.Service

   
   

4. Proceed with the ViaWorks upgrade.

   
   

5. The upgrade will enable and start all of the services. Repeat the instructions above for configuring the secondary ViaWorks server, including updating the DataAccess.config to point to the primary server, and disabling unnecessary ViaWorks services.