ANR0340E   command: Outbound replication operations are disabled because the database was restored.

Explanation

The database for this server was restored. Data that was on this server but that is not referenced by the restored database is no longer accessible. To prevent this server from deleting copies of data that might exist on the target replication servers, replication operations originating from this server are disabled.

System action

Processing ends.

User response

Disabling replication after a database restore is a precautionary step to alert the user of the potential that a restored database might contain node inventory that could result in the loss of filespace data on a target replication server that is using node replication. If replication was not used on this server before the database restore, issue the ENABLE REPLICATION command to resume replication operations.

To preserve the data that exists on target replication servers, determine whether copies of data that are on the target replication server are needed. If they are, you must replicate data that is on the target replication server to the source replication server. After the replication is complete, issue the ENABLE REPLICATION command to resume replication operations.

For example, suppose that PRODSRV is the source replication server. The data belonging to client node NODE1 was replicated from PRODSRV to DRSRV, the target replication server. The database on PRODSRV was restored.

To resume replication, complete the following steps:
  1. On PRODSRV and DRSRV, remove NODE1 from replication by issuing the following command: REMOVE REPLNODE NODE1.
  2. Update NODE1 definitions. When replication occurs, DRSRV will send the data to PRODSRV that was lost because of the database restore.
    1. On DRSRV, issue the following command: UPDATE NODE NODE1 REPLSTATE=ENABLED REPLMODE=SYNCSEND.
    2. On PRODSRV, issue the following command: UPDATE NODE NODE1 REPLSTATE=ENABLED REPLMODE=SYNCRECEIVE.
  3. On DRSRV, set the replication rules to match those on PRODSRV. For example, if only archive data was being replicated from PRODSRV to DRSRV, set the rules on DRSRV to replicate only archive data from DRSRV to PRODSRV. Backup and space-managed data will not be replicated to PRODSRV.
  4. On DRSRV, set the target replication server by issuing the following command: SET REPLSERVER PRODSRV.
  5. On DRSRV, replicate data belonging to NODE1 by issuing the following command: REPLICATE NODE NODE1. Replication processing changes the replication mode of NODE1 to SEND on DRSRV and to RECEIVE on PRODSRV.
  6. On PRODSRV and DRSRV, remove NODE1 from replication by issuing the following command: REMOVE REPLNODE NODE1.
  7. Update NODE1 definitions:
    1. On PRODSRV, issue the following command: UPDATE NODE NODE1 REPLSTATE=ENABLED REPLMODE=SYNCSEND.
    2. On DRSRV, issue the following command: UPDATE NODE NODE1 REPLSTATE=ENABLED REPLMODE=SYNCRECEIVE.
  8. On PRODSRV, enable replication by issuing the following command: ENABLE REPLICATION.
  9. On PRODSRV, replicate data belonging to NODE1 by issuing the following command: REPLICATE NODE NODE1. Replication processing changes the replication mode of NODE1 to SEND on PRODSRV and to RECEIVE on DRSRV.

The original replication configuration is restored. PRODSRV has all the data that was lost because of the database restore.

REMEMBER: To replicate data that was on DRSRV, you set the target replication server to PRODSRV. In your original configuration, if you were replicating data from DRSRV to another server, for example, BKUPDRSRV, you must reset the target replication server. To reset the target replication server, issue the following command on DRSRV: SET REPLSERVER BKUPDRSRV.