---
title: Replicating configurations
description: Use the Cluster Management window to replicate the configuration and license settings from the PingFederate administrative console node to the cluster's engine nodes.
component: pingfederate
version: 13.1
page_id: pingfederate:administrators_reference_guide:pf_replicat_config
canonical_url: https://docs.pingidentity.com/pingfederate/13.1/administrators_reference_guide/pf_replicat_config.html
llms_txt: https://docs.pingidentity.com/pingfederate/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: July 5, 2022
section_ids:
  about-this-task: About this task
  steps: Steps
  result: Result:
  troubleshooting: Troubleshooting
---

# Replicating configurations

Use the **Cluster Management** window to replicate the configuration and license settings from the PingFederate administrative console node to the cluster's engine nodes.

## About this task

The replication process takes only a moment. The engine nodes continue to process requests coming while they load updated replication data into memory. When the reload is complete, the updated configuration is activated for new requests.

## Steps

1. Go to **System > Server > Cluster Management**.

   ![Use the Cluster Management window to replicate the configuration from the console to the engine nodes in the cluster.](_images/jhq1657065342595.png)

2. Click **Replicate**.

   ### Result:

   PingFederate generates new replication data, updates the **Last Replicated** timestamp, and notifies the engine nodes that a new configuration is available. Then each node retrieves and applies the replication data, quickly going through the following **Replication Status** states:

   * Out-of-Date

   * Retrieving

   * Applying

   * Succeeded

## Troubleshooting

If, after a few minutes, the **Replication Status** of any node is Failed, investigate if a network communication failure, improper file permissions at the node, or another problem is causing the replication failure.