---
title: Upgrading a PingAccess cluster using the incremental update package
description: Upgrade a PingAccess cluster to a newer version using the incremental update package.
component: pingaccess
version: 8.3
page_id: pingaccess:upgrading_pingaccess:pa_upgrading_a_pa_cluster_using_the_incremental_upgrade_package
canonical_url: https://docs.pingidentity.com/pingaccess/9.1/upgrading_pingaccess/pa_upgrading_a_pa_cluster_using_the_incremental_upgrade_package.html
llms_txt: https://docs.pingidentity.com/pingaccess/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: July 16, 2026
superseded_by: https://docs.pingidentity.com/pingaccess/9.1/upgrading_pingaccess/pa_upgrading_a_pa_cluster_using_the_incremental_upgrade_package.html
section_ids:
  before-you-begin: Before you begin
  steps: Steps
  next-steps: Next steps
---

# Upgrading a PingAccess cluster using the incremental update package

Upgrade a PingAccess cluster to a newer version using the incremental update package.

Use the PingAccess incremental update bundle to upgrade from your current environment version (the *source version*) to a more recent maintenance release for that version of PingAccess (the *target version*). For example, use the bundle to upgrade PingAccess 6.3 to the most recent maintenance release for 6.3.

|   |                                                                                                                                                                                              |
| - | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | The upgrade procedure causes some downtime. To upgrade a cluster with no downtime, use the [Zero Downtime Upgrade](../pingaccess_zero_downtime_upgrade/pa_zero_downtime_upgrade.html) guide. |

## Before you begin

* Make a backup copy of the PingAccess home directory. If the upgrade fails, restore your environment from this backup.

* Review the release notes for every version between the source and target version.

* Verify the following:

  * Basic authentication is configured and enabled for the admin API of the source PingAccess instance.

    |   |                                                                                                                                                                                                                                                            |
    | - | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
    |   | You might need to enable basic authentication if you have limited access permissions to OAuth because of your configured role. Learn more in [Configuring API authentication](../pingaccess_user_interface_reference_guide/pa_configuring_api_authn.html). |

  * Each node is using the same PingAccess version.

    You can check the version by viewing the `<PA_HOME>/lib/pingaccess-admin-ui-<version_number>.jar` file.

  * The PingAccess administrative node is running.

  * You have the incremental update `.zip` file for the target version of PingAccess.

## Steps

1. Upgrade the administrative node:

   1. Extract the `.zip` archive for the target version of PingAccess.

   2. Open the `readme` file included in the extracted `.zip` archive.

   3. Make the file changes specified in the `readme` file.

2. Upgrade the replica administrative node:

   1. Extract the `.zip` archive for the target version of PingAccess.

   2. Open the `readme` file included in the extracted `.zip` archive.

   3. Make the file changes specified in the `readme` file.

3. Upgrade each engine node:

   1. Extract the `.zip` archive for the target version of PingAccess.

   2. Open the `readme` file included in the extracted `.zip` archive.

   3. Make the file changes specified in the `readme` file.

4. Shut down the entire cluster.

5. Start the upgraded administrative node.

6. Start the upgraded replica administrative node.

7. Start each upgraded engine node.

## Next steps

Review [Performing post-upgrade tasks](pa_performing_post_upgrade_tasks.html).