Before upgrading

Before starting any architecture or content updates, review these important notes:

• We recommend that you first implement updates in a test environment. Portal personalizations and customizations must be validated before you activate the new content in a production environment.

  To see which components have changed in any updated content version, you can use a comparison tool, such as KDiff3. This will help you determine if the changes affect the same components you have customized. See Comparing content versions for an update.

• A content version update may prompt you to update schema, which is a non-reversible operation. Before updating a content version, make sure you have a backup for the database associated with your LocalDataStore data source. If any problems occur, you can use the backup to restore the database.
• If you are installing the March 2020 portal content, you must enable full-text indexing for your portal knowledge content database(s). These databases are used for your LocalDataStore data source(s). The installation cannot complete successfully if full-text indexing is not enabled.
• Make sure no incomplete jobs exist in the farm. Incomplete jobs cause the farm to be locked, so it cannot be updated.

  You can check for incomplete jobs in the Farm Manager on the Farm Jobs tab under Farm Job Management. If any exist, cancel or retry them and then refresh the farm on the Farms tab under Farm Configuration.