---
title: Bootstrap replication servers
description: A bootstrap replication server is one of the replication servers in a deployment.
component: pingds
version: 8.1
page_id: pingds:config-guide:repl-bootstrap
canonical_url: https://docs.pingidentity.com/pingds/8.1/config-guide/repl-bootstrap.html
revdate: 2025-10-22T14:42:39Z
keywords: ["Features", "LDAP", "Replication", "Setup & Configuration"]
section_ids:
  add-bootstrap-replication-server: Add a bootstrap replication server
  remove-bootstrap-replication-server: Remove a bootstrap replication server
---

# Bootstrap replication servers

A *bootstrap replication server* is one of the replication servers in a deployment.

Every deployment with multiple replicas must have one or more bootstrap replication servers:

* When starting up, a DS server contacts a bootstrap replication server to discover the remaining DS servers in the deployment.

* Being a bootstrap replication server doesn't significantly increase resource use.

  After startup, a server gets its information about the remaining servers in the deployment from any replication server.

* Use at least two bootstrap replication servers for availability.

  You don't need more as long as all other DS servers can contact one of the bootstrap replication servers.

* A replication server takes on the role when other servers configure it as a bootstrap replication server.

  Specify the same list of bootstrap servers each time you set up a replica.

## Add a bootstrap replication server

After you add a replication server to a deployment, add it to the other servers' [bootstrap-replication-server](../configref/objects-replication-synchronization-provider.html#bootstrap-replication-server) settings.

Apply these steps for each server whose configuration references the new replication server to add:

1. Add the bootstrap replication server to the server's configuration:

   ```console
   $ dsconfig \
    set-synchronization-provider-prop \
    --provider-name "Multimaster Synchronization" \
    --add bootstrap-replication-server:new-rs.example.com:8989 \
    --hostname replica.example.com \
    --port 4444 \
    --bindDN uid=admin \
    --bindPassword password \
    --trustStorePath /path/to/opendj/config/keystore \
    --trustStoreType PKCS12 \
    --trustStorePassword:file /path/to/opendj/config/keystore.pin \
    --no-prompt
   ```

2. If the server uses property value substitution to load the list of replication bootstrap servers from the environment, restart the server for the changes to take effect.

## Remove a bootstrap replication server

After you remove a replication server from a deployment, remove it from other servers' `bootstrap-replication-server` settings.

Apply these steps for each server whose configuration references the replication server that you removed:

1. Remove the bootstrap replication server from the server's configuration:

   ```console
   $ dsconfig \
    set-synchronization-provider-prop \
    --provider-name "Multimaster Synchronization" \
    --remove bootstrap-replication-server:removed-rs.example.com:8989 \
    --hostname replica.example.com \
    --port 4444 \
    --bindDN uid=admin \
    --bindPassword password \
    --trustStorePath /path/to/opendj/config/keystore \
    --trustStoreType PKCS12 \
    --trustStorePassword:file /path/to/opendj/config/keystore.pin \
    --no-prompt
   ```

2. If the server uses property value substitution to load the list of replication bootstrap servers from the environment, restart the server for the changes to take effect.