Starting and stopping replication on a given node

Run the nzdr command with the replication option to start or stop replication on your system.

Tip:

By default, the replication time interval on each Cloud Pak for Data System is set to 180 minutes. As a result, database changes are captured on the primary Cloud Pak for Data System and applied on the replica Cloud Pak for Data System every 180 minutes.

Before you start replication, you can change this interval on the system, which is primary for the database. For more information, see Changing replication interval.

Procedure

To start replication:

Run the nzdr command with the replication subcommand for each of the replication nodes.

nzdr replication start --node-name NODE NAME

Example:

nzdr replication start --node-name CPDS-A

Successfully started replication scheduler on node CPDS-A.

To stop replication:
1. Log in to the Netezza Performance Server container as the nz user.
```
ssh nz@APPLIANCE HOSTNAME -p 51022
```
2. Before you stop replication, make sure any capture or apply jobs are not running on each system respectively. Run the following commands, for monitoring the backupmgr.log or restoremgr.log on primary and replica system respectively.
  On primary
```
ssh e2n1
cd /opt/ibm/appliance/storage/nrs/logs/replmgmt
vi backupmgr.log
```
  On replica
```
ssh e2n1
cd /opt/ibm/appliance/storage/nrs/logs/replmgmt
vi restoremgr.log
```
3. Once you have confirmed no jobs are running, run the following command to stop replication.
```
nzdr replication stop --node-name NODE NAME
```
  Example:
```
nzdr replication stop --node-name CPDS-A
Successfully stopped replication scheduler on node CPDS-A.
```
4. Verify whether replication was stopped successfully. Navigate to the backupmgr.log/restoremgr.log and check for the keyword. You get following message if the replication has stopped.
```
Stopping scheduler
```