Replicate data between primary and secondary sites - The process of replicating the data between the primary and the secondary site involves database replication using publisher and subscriber models in Microsoft SQL Server Management Studio , server repository replication using Windows Distributed File System (DFS), and backing up Elasticsearch (audit log) data.

Automation 360

The process of replicating the data between the primary and the secondary site involves database replication using publisher and subscriber models in Microsoft SQL Server Management Studio, server repository replication using Windows Distributed File System (DFS), and backing up Elasticsearch (audit log) data.

Before you begin

  • The DFS requires Automation 360 v.29 or later version.
  • Ensure that you have set up your secondary site before installing Automation 360 installer.

About this task

Configure the database and shared repository in the secondary site that is used for disaster recovery. Back up your Elasticsearch data by setting up the backup cluster.

Procedure

  1. Replicate the database from the primary site to the secondary site using the publisher and subscriber models in Microsoft SQL Server Management Studio.
    Recommendations:
    • Use the Microsoft SQL Server Developer or Enterprise edition for database replication.

      The publisher and subscriber versions must be the same, or the gap between the two versions must not be more than two releases. For example, do not use Microsoft SQL Server 2012 publisher with Microsoft SQL Server 2019 subscriber.

    • Configure the publisher and distributor on the same system to avoid latency in data sharing.

      Use different systems only for load distribution, for example, for data larger than 200 GB.

    1. Connect to the primary database to create a snapshot publication for your local publications.
    2. Add the tables and views as articles.
    3. Use the snapshot agent option to create a snapshot and keep the snapshot available to initialize subscriptions.
    4. Schedule the snapshot agent to back up the data at regular intervals (for example, every 10 seconds from 12 AM to 11:59:59 PM).
    5. To select the account to run the snapshot agent, configure the security and agent settings.
    6. Add a publication option.
    7. Run all agent and distributors after ensuring that the publisher and database names are correct.
    8. To add subscribers to the local subscriptions, connect to the database server and provide connection details for the database at the secondary site.
    For detailed steps, see Database Mirroring and Replication (SQL Server).
  2. Replicate the repository (bots and data files) using the Windows DFS from the primary site to the secondary site.
    1. Open the DFS on the machine where the shared repository is saved.
    2. Create a new multipurpose replication group to add replication group members.
      The group members include the source machine in the primary site and the destination machine in the secondary site to store the shared repository.
    3. Use the full mesh option for DFS replication groups composed of less than 10 servers.
    4. Use the full bandwidth option to replicate the data continuously.
    5. Add the machine where you are configuring the repository as a primary member.
    6. Add a backup folder for the shared repository from the destination machine.
    7. Verify that the data is replicated in the backup folder on the destination machine.
    For detailed steps, see Distributed File System Replication.
  3. Back up the Elasticsearch (audit log) data by adding the secondary site cluster IP address in the Control Room on the primary site.
    For detailed steps, see Configure disaster recovery site for OpenSearch IP addresses.