K2 Upgrade Options

K2 blackpearl has a number of versions spanning from the release version of K2 blackpearl to the current version. Each release of the platform has provided either enhancements, bug fixes or new features. The platform, which has undergone extensive evolutionary growth since its original release, is now poised for the next step in the current release iteration of version K2 blackpearl 4.6.

For a complete listing of K2 release upgrade compatibility, see the K2 Compatibility Matrix: Release Upgrade Compatibility.

Prerequisites Check

Ensure that the installed prerequisites are correct before the upgrade proceeds.

To verify that your existing system is configured correctly, or if there are any additional components that can be used in the K2 blackpearl environment, consult the Prerequisites by Component listing or the Prerequisites by Role listing.

Be sure to clear the cache after an upgrade, see the topic Clear cache after deploying K2 blackpearl for more information.

K2 Database checks

When upgrading your K2 blackpearl system, two checks are performed on the K2 database and if the checks fail you will receive notification on the K2 blackpearl Maintenance screen:

1. Database Consolidation check - if your legacy K2 databases (versions prior to K2 blackpearl 4.6) are not yet consolidated, you will receive the following note:
   “You have not consolidated your K2 databases. In order to upgrade in the future, you must have a single, consolidated K2 database. For more information about database consolidation, please see KB001628.”
2. Database Backup check - if your K2 database has not yet been backed up you will receive the following note:
   "K2 recommends backing up the database before upgrading. This database has never been backed up. For more information about backing up your database, search the K2 Knowledge Center."
   For more information on backing up your database, refer to KB001281.

Permissions

Ensure that you have the correct permissions to run the upgrade to avoid installation issues such as upgrading the workstations using a local domain admin will result in the client not being registered in the database. For the correct installation and upgrade permissions refer to the permissions topic.