Replication error in Cluster Log, "Replication Bundle Publisher Task failed" (4230057)

Errors seen in Cluster Log:
Replication Bundle Publisher Task failed: Full update of replica replica-console (1.1.1.1) to LSN 00000111:00000000:0001: This request operation sent to net.tcp://1.1.1.1:8000/FileTransfer did not receive a reply within the configured timeout (00:10:00)

Replication Bundle Publisher Failed to publish to replica-console (1.1.1.1), will restart task after backing off until at least 19:06:04

Other examples:

The error examples above indicate that the replication updates are not being sent from the Primary to the Replica as expected.

If these errors are seen soon after an upgrade, or soon after other maintenance has been performed, and normal replication is successfully re-established afterwards, then these errors may be safely ignored. In this case, it was simply due to the interruption caused by the maintenance.

Running a manual backup (or waiting for the scheduled backup to complete) may help clearing initial errors after cluster maintenance activity.

If this type of error is seen during normal operation when maintenance is not being performed and an interruption to replication is not expected, then you should investigate to see if there could be any communication issues or other networking problems between the appliances.

If the messages continue to show in the cluster logs "Replication Bundle Publisher Task failed: Incremental update of replica" then try the following steps:

1. Login to Primary /admin interface 
2. Navigate - System Status/Settings - Global Settings - Select Replication from Category Filter drop down menu
3. Increase the "Replication Interval" value from 60 seconds to 300 seconds (5 minutes) - Save Changes
4. Navigate - System Status/Settings - Cluster Management - Click "Restart Clustering"

Monitor the Cluster Logs for the following 30 minutes to verify the replication updates are processing on the Replica appliance as expected.