Starting and stopping replication for a given database

Run the nzdr command with the replication option to start or stop replication on a specific database. You can start/stop replication on all the replication nodes of a given database or on a specific node of that database.

Note: Stopping replication at node level takes precedence over the database level start and stopping.

Replication on all the active databases on a specific node will be automatically started when replication is restarted on a given replication node.

Before you begin

  1. Ensure that no capture or apply jobs are active for the specified database before stopping its replication process.
  2. For capture monitor, check backupmgr.log on primary and for apply monitor, check restoremgr.log on replica. Run the following commands for checking the logs:
    
ssh e2n1
docker exec -it nrs_replmgmt bash
cd /var/log/replmgmt
tail -vf <backupmgr.log> or <restoremgr.log>

Procedure

  • To start replication:
    1. Log in to the Netezza Performance Server container as the nz user.
      ssh nz@APPLIANCE HOSTNAME -p 51022
    2. Run the nzdr command with the replication subcommand for each of the replication databases.
      nzdr replication start --db-name DATABASE NAME
      Example:
      nzdr replication start --db-name MYDB-1

Successfully started replication scheduler on db MYDB-1.
  • To stop replication:
    1. Log in to the Netezza Performance Server container as the nz user.
      ssh nz@APPLIANCE HOSTNAME -p 51022
    2. Run the nzdr command with the replication subcommand for each of the replication databases.
      nzdr replication stop --db-name DATABASE NAME
      Example:
      nzdr replication stop --db-name MYDB-1

Successfully stopped replication scheduler on db MYDB-1.
  • To display DB status: 
    nzdr status db --db-name DATABASE NAME
    Example:
    Databases -
 1. NRS1
    Primary:
       Node: CPDS-A (Active)
       Last capture timestamp: Thu 21 Sep 2023 10:27 PM PDT
       Last capture seq no: 1
       Last pruned capture seq no: -1
       Last reported capture error: None
       Replication status: Active/Suspended/Capturing/Retrieving/Applying/Queuing (Current)/Queuing (Pending)
    Replicas:
       Node: CPDS-B (Active)
       Last apply timestamp: Thu 21 Sep 2023 10:29 PM PDT
       Last apply seq no: 1
       Last pruned apply seq no: -1
       Last reported apply error: None
       Replication status: Active/Suspended/Capturing/Retrieving/Applying/Queuing (Current)/Queuing (Pending)