Upgrading from V6 to V8

WestOderman

When upgrading from V6 to V8, there are a few things to consider such as what version to upgrade to, recommended requirements for V8, and some general strategies to minimize risk.

If a server is running V6 and is intending to upgrade to V9, it is recommended to upgrade first to V8 then to upgrade to V9 to minimize corruption, broken features, and unsupported configurations.

Version of V8 to Upgrade To

When upgrading to V8, it is recommended to upgrade to the latest version (8.22.0). This is because it has the latest patches minimizing potential bugs that could create complications in the transfer.

Recommended/Minimum Requirements for upgrading

The recommended requirements vary between types of servers. It is always suggested to check with expertise prior to deployment to verify specifications due to the variation from server to server. Additionally, refer to this link (https://documentation.decisions.com/v8/docs/installation-requirements?highlight=minimum%20requirements) for any additional components that will be added to your server.

For a production server, a 4-core CPU, 16GB of RAM, and at least 100GB of storage is recommended

For a non-production server, a 4-core CPU, 8GB of RAM, and 100GB is recommended.

When upgrading to 8.22.0, .NET 8.0 and .NET Core 6.0 SDK is required

Minimizing Risk

One of the most important things one can do to minimize risk of corruption is to make a backup of the settings.xml file, the Database (make sure to note the DB server and DB name), keys.dat, the FileStorage folder, and databaseid.txt files prior to beginning the upgrade.

It is suggested to follow the guide on the Documentation site to make the process as streamlined as possible. This should also be referred to in case of troubleshooting. https://documentation.decisions.com/v8/docs/upgrading-decisions-v6-to-v8