Page created: 24 Jul 2019 | Page updated: 6 Nov 2019 | 1 min read7.3 Product PingDirectory In the event that the replication changelog is compromised (<server-root>/changelogDb), possibly due to a disk or NAS failure, perform the following steps. Stop the server. Backup replicationChanges from a remote server with the following command: $ bin/backup --backupDirectory /app/backups/replicationChanges \ --backendID replicationChanges Copy the replicationChanges backup from the remote server and restore it on the local host as follows: $ bin/restore --backupDirectory /app/tmp/replicationChanges Start the server.
In the event that the replication changelog is compromised (<server-root>/changelogDb), possibly due to a disk or NAS failure, perform the following steps. Stop the server. Backup replicationChanges from a remote server with the following command: $ bin/backup --backupDirectory /app/backups/replicationChanges \ --backendID replicationChanges Copy the replicationChanges backup from the remote server and restore it on the local host as follows: $ bin/restore --backupDirectory /app/tmp/replicationChanges Start the server.