How to Correct Propagation of Modified snaprep/snapha Configuration Files

Situation: Issue where CIFS shares became unavailable after a takeover operation that was performed from the target while HA was active. Several GBs of data were written to two volumes with HA deactivated. After the write completed, a new write of data to both volumes was in progress.  Halfway through the replication a Takeback was initiated from the target node. After the failover completed and the VIP was moved, CIFS volume access was not working.  Restarting of the samba and win bind services did not resolve the issue

This is a rare corner case and is working as designed. 

Any changes made to a HA source node while deactivated will not propagate until HA is reactivated and a full replication cycle completes.

Restart replication within the SoftNas and wait until a full replication cycle has completed

Open