---
title: Resuming configuration replication
description: Resume the configuration replication that was disabled by the Upgrade Utility. Perform this step for all engine nodes in the cluster.
component: pingaccess
version: 9.0
page_id: pingaccess:pingaccess_zero_downtime_upgrade:pa_resuming_configuration_replication
canonical_url: https://docs.pingidentity.com/pingaccess/9.0/pingaccess_zero_downtime_upgrade/pa_resuming_configuration_replication.html
revdate: February 6, 2023
section_ids:
  about-this-task: About this task
  steps: Steps
  example: Example:
  result: Result:
---

# Resuming configuration replication

Resume the configuration replication that was disabled by the Upgrade Utility. Perform this step for all engine nodes in the cluster.

## About this task

You will use the PingAccess Admin API to GET and PUT the relevant configuration data for each of these items.

![Flowchart showing a deployment as configuration replication is resumed.](_images/rxs1564006860388.png)

In the previous flowchart:

1. A user with a WebSession Cookie sends a request to the load balancer.

2. The load balancer directs the request to one of the un-upgraded engine nodes. The first engine node is using the target version of PingAccess, and its connection to the administrative node is resuming.

3. The administrative node is using the target version of PingAccess.

|   |                                                             |
| - | ----------------------------------------------------------- |
|   | Perform the following steps for each engine in the cluster. |

To resume configuration replication:

## Steps

1. In a browser, go to https\://*\<host>*:*\<admin-port>*/pa-admin-api/v3/api-docs/.

   ### Example:

   https\://localhost:9000/pa-admin-api/v3/api-docs/

2. For engines, expand the **/engines** endpoint.

3. Click the **GET /engines** operation.

4. Click **Try it out!** and note the engine id for each engine.

5. Click the **GET /engines/{id}** operation.

6. In the **ID** field, enter the id of the engine you want to update and click **Try it out!**

7. Copy the entire Response Body.

8. Click the **PUT /engines/{id}** operation and enter the id of the engine you want to update.

9. In the **Engine** field, paste the response body you copied and change `"configReplicationEnabled"` to `true`.

10. Click **Try it out!**

    ### Result:

    If the operation is successful, you will receive a response code of `200`.

11. Start the node.

12. Repeat the previous steps for each node.

13. Click **Settings**, then go to **Clustering > Engines**.

14. Ensure the engines are displayed and reporting. A healthy engine shows a green status indicator.

    |   |                                                                                                                                                                                                 |
    | - | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
    |   | There might be a delay in bringing the engine to a running status. If the engine does not immediately show as reporting, refresh the page until the engine status indicator is green (running). |

![This flowchart shows a deployment after configuration replication has resumed.](_images/svh1564006861224.png)

In the previous flowchart:

1. A user with a WebSession Cookie sends a request to the load balancer.

2. The load balancer directs the request to one of the un-upgraded engine nodes. The first engine node is using the target version of PingAccess, and its connection to the administrative node has resumed.

3. The administrative node is using the target version of PingAccess.