In the event that the replication changelog is compromised (<server-root>/changelogDb), possibly due to a disk or NAS failure, perform the following steps.
  1. Stop the server.
  2. Backup replicationChanges from a remote server with the following command:
    $ bin/backup --backupDirectory /app/backups/replicationChanges \
      --backendID replicationChanges
  3. Copy the replicationChanges backup from the remote server and restore it on the local host as follows:
    $ bin/restore --backupDirectory /app/tmp/replicationChanges
  4. Start the server.