option to manually disable secondary collective member synchronization
I have experienced several synchronization errors with data archives running on virtual machines in separate errors, generally after MS updates. Please provide a way to stop synchronization of configurations between collective members, so I can perform MS updates and reboots without fear of having to re-synchronize my secondary archives afterwards.
Microsoft operating system patching should not have caused collective members to go out of sync. Have you reviewed this KB article?
If you continue to run into issues patching, I recommend you contact tech support.