2 of 2 people found this helpful
I would first check the Network Manager Statistics (SMT->Operations->NetMgrStats) and make sure that the connection from the secondary comes in as the same identity as the primary. You can see this even when it is not the primary member. Make sure that it has read access to the source and write access to the target.
Thanks for your inputs. As suggested, I have checked the connections from the secondary node. We had two trusts created, one with host name and another with the ip address of the machine. I noticed an issue with the trust that was created for the machine ip, I corrected it and restarted the interface. The errors are cleared now.
Thanks for your help.
1 of 1 people found this helpful
You may want to inspect the data and make sure you do not have a gap on the secondary. If you do, then you can simply run a history recovery to cover that period.