Chapter 2. Recovering a single server with replication If a single server is severely disrupted or lost, having multiple replicas ensures you can create a replacement replica and quickly restore the former level of redundancy. If your IdM topology contains an integrated Certificate Authority (CA), the steps for removing and replacing a damaged replica differ for the CA renewal server and other replicas. 2.1. Recovering from losing the CA renewal server If the Certificate Authority (CA) renewal server is lost, you must first promote another CA replica to fulfill the CA renewal server role, and then deploy a replacement CA replica. Prerequisites Your deployment uses IdM's internal Certificate Authority (CA). Another Replica in the environment has CA services installed. Warning An IdM deployment is unrecoverable if: The CA renewal server has been lost. No other server has a CA installed. No backup of a replica with the CA role exists. It is critical to make backups from a replica with the CA role so certificate data is protected. For more information about creating and restoring from backups, see Preparing for data loss with IdM backups . Procedure From another replica in your environment, promote another CA replica in the environment to act as the new CA renewal server. See Changing and resetting IdM CA renewal server . From another replica in your environment, remove replication agreements to the lost CA renewal server. See Removing server from topology using the CLI . Install a new CA Replica to replace the lost CA replica. See Installing an IdM replica with a CA . Update DNS to reflect changes in the replica topology. If IdM DNS is used, DNS service records are updated automatically. Verify IdM clients can reach IdM servers. See Adjusting IdM clients during recovery . Verification Test the Kerberos server on the new replica by successfully retrieving a Kerberos Ticket-Granting-Ticket as an IdM user. Test the Directory Server and SSSD configuration by retrieving user information. Test the CA configuration with the ipa cert-show command. Additional resources Using IdM CA renewal server 2.2. Recovering from losing a regular replica To replace a replica that is not the Certificate Authority (CA) renewal server, remove the lost replica from the topology and install a new replica in its place. Prerequisites The CA renewal server is operating properly. If the CA renewal server has been lost, see Recovering from losing the CA renewal server . Procedure Remove replication agreements to the lost server. See Uninstalling an IdM server . Deploy a new replica with the corresponding services (CA, KRA, DNS). See Installing an IdM replica . Update DNS to reflect changes in the replica topology. If IdM DNS is used, DNS service records are updated automatically. Verify IdM clients can reach IdM servers. See Adjusting IdM clients during recovery . Verification Test the Kerberos server on the new replica by successfully retrieving a Kerberos Ticket-Granting-Ticket as an IdM user. Test the Directory Server and SSSD configuration on the new replica by retrieving user information.

Commands:
kinit admin Password for admin@EXAMPLE.COM: klist Ticket cache: KCM:0 Default principal: admin@EXAMPLE.COM Valid starting Expires Service principal 10/31/2019 15:51:37 11/01/2019 15:51:02 HTTP/server.example.com@EXAMPLE.COM 10/31/2019 15:51:08 11/01/2019 15:51:02 krbtgt/EXAMPLE.COM@EXAMPLE.COM
ipa user-show admin User login: admin Last name: Administrator Home directory: /home/admin Login shell: /bin/bash Principal alias: admin@EXAMPLE.COM UID: 1965200000 GID: 1965200000 Account disabled: False Password: True Member of groups: admins, trust admins Kerberos keys available: True
ipa cert-show 1 Issuing CA: ipa Certificate: MIIEgjCCAuqgAwIBAgIjoSIP Subject: CN=Certificate Authority,O=EXAMPLE.COM Issuer: CN=Certificate Authority,O=EXAMPLE.COM Not Before: Thu Oct 31 19:43:29 2019 UTC Not After: Mon Oct 31 19:43:29 2039 UTC Serial number: 1 Serial number (hex): 0x1 Revoked: False
kinit admin Password for admin@EXAMPLE.COM: klist Ticket cache: KCM:0 Default principal: admin@EXAMPLE.COM Valid starting Expires Service principal 10/31/2019 15:51:37 11/01/2019 15:51:02 HTTP/server.example.com@EXAMPLE.COM 10/31/2019 15:51:08 11/01/2019 15:51:02 krbtgt/EXAMPLE.COM@EXAMPLE.COM
ipa user-show admin User login: admin Last name: Administrator Home directory: /home/admin Login shell: /bin/bash Principal alias: admin@EXAMPLE.COM UID: 1965200000 GID: 1965200000 Account disabled: False Password: True Member of groups: admins, trust admins Kerberos keys available: True