---
title: Rolling updates
description: Perform rolling updates on PingDirectory servers using a topology.json file and the manage-profile replace-profile subcommand during deployment automation.
component: pingdirectory
version: 10.3
page_id: pingdirectory:pingdirectory_server_administration_guide:pd_ds_rolling_updates
canonical_url: https://docs.pingidentity.com/pingdirectory/11.1/pingdirectory_server_administration_guide/pd_ds_rolling_updates.html
llms_txt: https://docs.pingidentity.com/pingdirectory/llms.txt
docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md
revdate: 2023-09-13T00:00:00Z
superseded_by: https://docs.pingidentity.com/pingdirectory/11.1/pingdirectory_server_administration_guide/pd_ds_rolling_updates.html
section_ids:
  about-this-task: About this task
  steps: Steps
---

# Rolling updates

## About this task

The presence of the file `server.uuid` in the PingDirectory server's `config` directory indicates whether the server is being set up initially or being updated.

## Steps

1. Create or obtain the `topology.json` file either manually or by using external automation. When promoting from a dev/test environment to a stage/prod environment, you can obtain a `topology.json` file using the `manage-topology export` subcommand.

2. Extract the new server bits to a directory.

3. From the same directory's `bin` directory, replace the new server profile, as follows:

   ```
   manage-profile replace-profile \
     --profile /path/to/server-profile \
     --profileVariablesFile /path/to/instance-specific-variables.properties \
     --serverRoot /path/to/existing/server
   ```