DRS client audit

Last Updated : Mar 03, 2014 |

You can configure Data Replication Service (DRS) client elements in the Geographic Redundancy (GR) mode or GR-unaware mode.

A GR-aware DRS client must conform to the norms for a GR-aware element. A GR-aware element must work with the virtual FQDN configuration.

When you activate the secondary System Manager or when you enable GR after the system restores the primary System Manager, DRS marks all client nodes that are GR-aware for audit. The system displays the nodes marked for audit as Pending Audit. When you activate the secondary System Manager, DRS configures all GR-unaware DRS client nodes to deny recording any database change events. The system displays the state of DRS client nodes that are GR-unaware as Not Managed.

During the restoration of the primary System Manager, if you select the database of:

  • The primary System Manager, the system marks all configured GR-aware client nodes for audit.

  • The secondary System Manager, the system marks all DRS client nodes that are GR-aware for audit. Also, the system marks all DRS client nodes that are GR-unaware for repair.

When the system marks a node for audit, the system denies any further requests from the node until the audit is complete for that node. DRS service on System Manager sends a request to the DRS client element for audit data. DRS performs the audit for the DRS client and determines whether the client node requires a full synchronization. If the audit reveals that the client has more recent data than the data on System Manager, DRS schedules a full-synchronization for the element. This phase marks the completion of audit and the system configures DRS to accept requests from the element.

Using DRS, the system initiates the client audit under following situations:

  • Manual: When an administrator activates the secondary System Manager, DRS flags all configured clients for audit. This action ensures that none of the configured client elements have more data than the secondary System Manager. DRS flags similar client audit when the primary System Manager is recovered.

  • Automated: During situations such as split network, when an administrator activates the secondary System Manager server, a node changes to the secondary System Manager server. However, in split network scenario, you cannot predict the network condition and the node can change back to the primary System Manager server.