Changing Hardware During a Software Upgrade - Mitigating Risk in OnBase Upgrades - English - Foundation 22.1 - OnBase - Essential - Premier - Standard - external - Standard - Essential - Premier

Mitigating Risk in OnBase Upgrades

Platform
OnBase
Product
Mitigating Risk in OnBase Upgrades
Release
Foundation 22.1
License
Standard
Essential
Premier

Organizations are often tempted to replace hardware (e.g., servers) as part of an upgrade project. The new servers will come with new operating systems, often preloaded with different installation versions and processes than the servers in the test environment. These differences have caused issues where the OnBase software worked as expected in the test system but failed in the production system.

Servers should be upgraded independently of the OnBase upgrade process. A recommended approach for upgrading hardware is to deploy the new hardware in the test environment and then test to ensure that the existing OnBase production configuration runs successfully using the new servers.

Database server upgrades sometimes include a database software upgrade, adding another layer of risk that should also be separated from an OnBase upgrade. Changes to the database version should also include upgrades to the database client software. Many issues have occurred with mismatched versions of database client and server software.