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.
Processing ends.
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.
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.