---
title: Configuration-archive deployment
description: Uploading configuration archives is an alternate method of copying configurations to clustered PingFederate servers.
component: pingfederate
version: 13.1
page_id: pingfederate:server_clustering_guide:pf_config_archiv_deploy
canonical_url: https://docs.pingidentity.com/pingfederate/13.1/server_clustering_guide/pf_config_archiv_deploy.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: May 5, 2023
section_ids:
  runtime-state-management-services: Runtime state-management services
---

# Configuration-archive deployment

Uploading configuration archives is an alternate method of copying configurations to clustered PingFederate servers.

After you configure or reconfigure the console, you can also update cluster nodes by downloading a configuration archive from the **System > Server > Configuration Archive** window and then deploying it either manually or using a scripted process to the `<pf_install>/pingfederate/server/default/data/drop-in-deployer` directory on each cluster node or provisioning-failover server.

To enable automatic replication of a configuration data archive to server nodes, you must enable the `replicate.after.drop.in.deploy` attribute in the `cluster-config-replication.conf` file to `true`. Learn more in [Upgrading configuration data](../upgrading_pingfederate/pf_upgrading_config_data.html).

|   |                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
| - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | If you use the drop-in deployment process:- To ensure successful importation of the configuration archive file with this process, you must rename the file `data.zip`.

- If the data archive is from an older version, PingFederate will automatically upgrade archive data to be compatible with the current version. Learn more in [Upgrading configuration data](../upgrading_pingfederate/pf_upgrading_config_data.html).

- On startup, the heartbeat endpoint will not return `200` until the archive import completes. If you have configured a health check or probe that can trigger a restart of the server, crash loop behavior can result. Review the configuration of these checks to ensure time thresholds are set appropriately. |

A configuration archive contains the same information sent during the [configuration push](pf_console_config_push.html) from the administrative console.

## Runtime state-management services

If you have configured one of the following runtime state-management services on the engine nodes, you must manually migrate the configuration files to the engine nodes. The configuration files are locted at `<pf_install>/pingfederate/server/default/conf`

**Configuration file and service implementation**

| Configuration file                         | RPC-based service implementation                                                                |
| ------------------------------------------ | ----------------------------------------------------------------------------------------------- |
| `cluster-account-locking.conf`             | [Account Locking Service](pf_acc_lock_service.html)                                             |
| `cluster-artifact.conf`                    | [Artifact-Message Persistence and Retrieval Service](pf_artif_mess_persis_retriev_service.html) |
| `cluster-assertion-replay-prevention.conf` | [Assertion Replay Prevention Service](pf_assertion_replay_prevention_service.html)              |
| `cluster-idp-session-registry.conf`        | [IdP Session Registry Service](pf_idp_session_registry_service.html)                            |
| `cluster-inter-request-state.conf`         | [Inter-Request State-Management (IRSM) Service](pf_irsm_service.html)                           |
| `cluster-session-revocation.conf`          | [Back-Channel Session Revocation Service](pf_bac_chann_sess_revoc_service.html)                 |
| `cluster-sp-session-registry.conf`         | [SP Session Registry Service](pf_sp_sess_regist_service.html)                                   |