Upgrading a Verba system consist of various steps executed by the installer and includes some manual step also. Before starting the upgrade make sure you have the followings available:
...
Verba supports upgrade from version 5 up to the latest version following the procedures described in this document.
Note |
---|
Upgrades are not supported to specific builds such as 9.8.5.1111, where 1111 is the build version. However, you can upgrade to a major, minor, or service version such as 9.0.0.0000, 9.8.0.0000, or 9.8.5.0000. |
If you are aware of any customization (custom database procedures, triggers or customized web interface including branding) in your system, please contact your Verba representative before the upgrade.
...
- Backup Verba database and prepare it for the upgrade process
- (optional) Backup existing servers and verify server and OS compatibility
- Uninstall the existing Verba software
- Install the new Verba software
- Configure servers
- Test the new system
...
For more information, see: Database table partitioning
(Optional) Backup Verba servers and verify server and OS compatibility
In order to ensure that you can restore the system at any point during the upgrade procedure, you need to make a backup of the entire system.
...
Step 1 - Make a note of all active Verba services on the servers by navigating to Service Activation tab under System / Servers for 9.x or later versions and under Administration / Verba Serves in earlier versions. You will need this information when you re-apply the configuration on the servers running the new version.
Step 2 - Stop all Verba services on all servers. If you need to continue recording or you want to minimize downtime, you can continue recording on the Verba Recording Servers by disabling the database access. Before doing so, please consult your Verba representatives to confirm the available options and compatibility issues between the existing and the new system.
Step 3 - Check if your media folders or storage targets are not under C:\Program Files (x86)\Verba. If your media folders or storage targets are under C:\Program Files (x86)\Verba, move the folder to another, more appropriate location.
Step 4 - Optionally - Optionally, make a copy of your log folders to an external location on all servers.
Step 53 - Optionally, make a copy of the C:\Program Files (x86)\Verba\resources\webapp\ folder on the Media Repository server to backup branding and other web application customization.
Step 6 - Make a copy of the server registry under HKLM\SOFTWARE\Wow6432Node\Verba key.Step 7 - 4 - Check server configuration (CPU, memory, disk, network), operating system and database version compatibility for the new Verba version.
Uninstall Verba servers
Step 1 - Check that you have valid and up to date backups of your servers, and you verified server and OS compatibility with the new version.
Step 2 - Uninstall the Verba Media Repository Server first, unless you have a single server in your deployment.
Step 3 - Check that you do not have remaining files under C:\Program Files (x86)\Verba folder. If you have, check that no media folder is used under this folder and you made a backup of all relevant content (for instance log files). After checking all of these, delete the content of the folder.
Step 4 - Check that you do not have remaining entries under HKLM\SOFTWARE\Wow6432Node\Verba key. If you have, delete them completely.
Step 5 - Repeat Step 2 through Step 4 for all other Verba servers, including the ones installed on external servers such as Lync/SfB servers.
Install Verba servers
...
Install Verba servers
After uninstalling the servers, follow Install the Verba software and install the new versions of the servers.
Step 1 - Run the prerequisites tool from the new installer package to check if there is any missing prerequisite. Install the missing ones and make sure you have Java Runtime version 11 installed on Verba Media Repository and Verba Recording Servers.
...
Step 1 - Login to the web interface and navigate to the Verba server and select the Service Activation tab. Activate all Verba service according to the previous configuration.
Step 2 - Navigate Go to Change Configuration Settings tab. The system will offer you an option to apply the previous configuration (the configuration in the database) on the server. Select the Use configuration only from central database option, or you can manually select the appropriate option below.
...
Step 3 - Press Start and follow the instructions on the screen to apply the new configuration on the server.
Step 4 - On the Configuration Tasks tab, select Apply Extension Configuration and follow the instructions on the screen.
Step 5 - Repeat these steps for all Verba servers in your deployment.
Step 56 - If you have added new servers during the upgrade, simply configure them using an existing configuration template or direct server configuration.
Step 67 - Now you have finished the upgrade. Check all configuration settings (especially the new ones) and execute your test plan to ensure that your system is functioning properly.
Step 8 - (Optional) If the C:\Program Files\Verba\tomcat\conf\server.xml file included the certificateChainFile value before the upgrade, ensure that the value is still present after the upgrade and it specifies the correct certificate.
Roll back to the previous version
If you encounter any issues during the upgrade and you are unable to resolve them, you need to roll back to the previous, working copy.
Info |
---|
If you |
...
created server snapshots, you can simply restore them instead of completing the rollback procedure. |
If you need to manually restore the system, follow the steps below:
Step 1 - Uninstall the new Verba servers by following the uninstall steps above. Make sure you execute the manual checks also.Step 2 - Run the prerequisites tool from the previous installer package. Make sure you have the right Java Runtime on the server.
Step 3 2 - Restore the Verba database from the backup.
Step 4 3 - Install the Verba Media Repository server first.
Step 54 - Install the previous version on all other servers.
Step 65 - Apply the configuration on the servers and test the configuration by following the steps described above.
...