--- title: "show ha replication data status" slug: "show-ha-replication-data-status" tags: ["Reference", "CMS 11.x", "EX 11.x", "HX 10.x", "FX 11.x", "AX 11.x", "NX 11.x", "IVX 11.x", "Customer", "Network Security"] updated: 2026-08-04T17:22:26Z published: 2026-08-04T17:22:26Z canonical: "docs.trellix.com/show-ha-replication-data-status" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # show ha replication data status Displays the database replication status of a Central Management System High Availability (HA) cluster. ### Syntax ``` show ha replication data status ``` ### Parameters None ### Output fields The following table describes the output fields for this command. | Field | Description | | --- | --- | | **Database Replication Status** | The database replication status of each node in the cluster: - **Running**—All services are running, all communication links are up, and all nodes are online. - **Stopped**—At least one service is not running on at least one node. - **Starting**—At least one service is starting up on at least one node, or the database synchronization is being set up on the secondary node. - **Updating**—A software upgrade or downgrade is being performed on a node in the cluster. - **Degraded**—Backup links of the same type are down, or the secondary node is configured, but currently offline. - **Error**—Communication links are down or broken, or a service failed to start. - **Unknown**—The node is not accessible. | | **Now** | The date and time of database replication. | | **Streaming replication** | Information about the latest database replication. | | **Base database sync** | The status of base database synchronization. | | **Event history** | The events and duration of the database synchronization for the primary and secondary nodes. | | **Database fail-over** | Information about the database failover. | | **Event history** | The events and duration of the database failover. | | **Most recent events** | The most recent events. | ### Example The following example shows the status of the HA database replication services when the HA primary node is running a full database sync with the HA secondary node. You view the database sync progress through the event history. > [!NOTE] > Note > > The output is the same when you display the status from the secondary node, except `(self)` is not displayed in the `Primary Node:` line. ``` node1# show ha replication data status Database Replication Status: Primary:    node1 (self) (fedb running) Secondary:  node2        (fedb stopped) Now:        2019/06/14 21:57:31 Streaming replication Latest status:       replication information unavailable Last updated time:   2019/06/14 21:23:32.045 (33 min 59 sec ago) Base database sync Status:              in progress Latest status:       running full db sync with secondary for 1743 sec at marker 000154B1 Last updated time:   2019/06/14 21:23:32.045 (33 min 59 sec ago) Event history   Duration  29 min  4.904 sec  (on-going event)    2019/06/14 21:28:18.998  node2  secondary  initializing full db sync    2019/06/14 21:57:23.902  node1  primary    running full db sync with secondary for 1743 sec at marker 000154B1 Database fail-over Latest status:       node1 was promoted to new master Last updated time:   2019/06/14 21:23:12.380 (34 min 18 sec ago) Event history 1   2019/06/14 21:23:12.380  node1  secondary  fedb          qa-cm7500-4-9-12 was promoted to new master 2   2019/06/14 21:17:16.808  node2  secondary  fedb          qa-cm7500-4-9-10 was promoted to new master 3   2019/06/14 21:08:31.089  node2  secondary  fedb          qa-cm7500-4-9-10 was promoted to new master 4   2019/06/14 21:03:48.307  node2  secondary  fedb          qa-cm7500-4-9-10 was promoted to new master Most recent events 1   2019/06/14 21:57:23.902  node1  primary    full-db-sync  running full db sync with secondary for 1743 sec at marker 000154B1 2   2019/06/14 21:57:07.498  node2  secondary  full-db-sync  full db sync in progress 78% completed 3   2019/06/14 21:56:52.570  node1  primary    full-db-sync  running full db sync with secondary for 1711 sec at marker 000154B1 4   2019/06/14 21:56:52.570  node1  primary    full-db-sync  running full db sync with secondary for 1711 sec at marker 000154B1 5   2019/06/14 21:56:37.474  node2  secondary  full-db-sync  full db sync in progress 77% completed . . . ``` ### User role Admin, Operator, or Monitor ### Command mode Enable ### Supported appliances This command is supported on the following appliance running the specified release or later: - **Central Management System**: Release 8.6.0. > [!NOTE] > Note > > For more information about Central Management System HA, see the Central Management System High Availability Guide.