====================
Repair Database Sync
====================

Introduction
============

If your HA Pair is already configured, you can follow this guide to perform a manual re-sync of the database.

Perform a Manual Sync
=====================

To access the High Availability maintenance menus, log in to the Appliance CMI (using PuTTY or the console).

1. From the **Main Menu**, select option ``7`` for **High Availability**.
2. From the **High Availability Main Menu**, select option ``3`` for **Database Replication**.

From this menu, you can check replication status, start reading updates, or repair the replication.

.. code-block:: text

    HA Database Replication Menu
    ----------------------------
    1) Status
    2) Start Reading Updates from Peer
    3) Repair Replication
    8) Back

Repair Replication
------------------

If replication has failed or the databases are out of sync, perform the following steps:

1. From the **HA Database Replication Menu**, select option ``3) Repair Replication``.
2. You will be prompted to select the **canonical database source**. This determines which database is treated as the "correct" version that will overwrite the other.

   .. code-block:: text

      Select canonical database source:
      1) Local Databases
      2) Peer Databases (IP: [Peer_IP])
      8) Cancel

   * **Option 1 (Local Databases):** The database on the machine you are currently logged into will be pushed to the Peer. (Use this if the local unit has the most up-to-date data).
   * **Option 2 (Peer Databases):** The database on the Peer unit will be pulled to the local machine.

3. Enter the number corresponding to your choice (e.g., ``1``).
4. You will be asked to confirm the action (e.g., ``Copy Local Databases to Peer?``). Enter ``y`` to confirm.

If the sync is successful, the system will display a confirmation message:

.. code-block:: text

   INFO: Sent databases to Peer
   Press RETURN to continue:

Check the Status
----------------

After performing a repair, it is important to verify that replication is active.

1. From the **HA Database Replication Menu**, select option ``1) Status``.
2. Select the IP address of the appliance/peer you wish to check.

   .. code-block:: text

      Select IP to check status of:
      1) [Peer IP Address]
      2) [Virtual IP/Other]

3. The system will report the status of the threads. A healthy status should read "True" for both reading updates from Remote and Local.

   .. code-block:: text

      Local: Reading updates from Remote: True
      Remote: Reading updates from Local: True

Verifying Replication (Application Test)
========================================

Once the database replication status reports as "True" in the CMI, it is recommended to perform a functional test via the Web Administration (Core) console. This confirms that data changes are syncing bi-directionally in real-time.

**Step 1: Modify a User on the Primary**

1. Open a web browser and navigate to the **Primary** server's Web Administration console (e.g., ``http://<Primary_IP>:8080/sentry``).
2. From the main menu, navigate to **User Administration**.
3. Select a user account from the list.
4. Click the **Policy** button associated with that user.
5. Locate and **check** the box labeled **PIN never expires**.
6. Click **Apply** (or Update) to save the change to the database.

**Step 2: Verify and Modify on the Standby**

1. Open a new browser tab or window and navigate to the **Standby** server's Web Administration console (e.g., ``http://<Standby_IP>:8080/sentry``).
2. Navigate to **User Administration** and locate the *same* user account accessed in Step 1.
3. Click the **Policy** button.
4. **Verify:** The **PIN never expires** box should be **checked**, indicating the change successfully replicated from the Primary.
5. **Uncheck** the **PIN never expires** box.
6. Click **Apply** (or Update) to save the change.

**Step 3: Confirm Reverse Replication**

1. Return to the browser tab for the **Primary** server.
2. Refresh the User Policy page (or navigate away and back to the user's Policy screen).
3. **Verify:** The **PIN never expires** box should now be **unchecked**.

If these steps complete successfully, Master-Master database replication is fully operational.