Problem with one node of a four cluster FileServer

That doesn’t seem to be out of the ordinary. Do you have to sync that node up every time the backup runs? If it’s only when the cluster is brought back that should be normal if changes were made that would\could have affected the registry that tells the plugin service how to work. 

Are you able to manually bring the plugin service online when that node is introduced again? 

Hi @Aplynx, 
 

Does this mean that I only need to do the manual syn the first time a node is added back to the cluster and when these resources automatically change, this is also automatically noticed by the plugin ? 
The remaining three nodes have no problems here when a resource moves to another node. 
On the node I can not start the plugin. As soon as I force all nodes to sync via Commvault, the resources that were moved to the new node come online with the Commvault plugin. 

It sounds like the cluster is missing the registry information to start the plugin which is what the sync process is bringing back. It’s odd that you have to sync the plugin, but the physical WinFS itself is intact. It’s usually not a bad idea to sync it either way when it’s brought back online just to make sure that any changes are seen by that machine. You should only need to do it the one time, unless it’s removed again.

Appreciate the status update, @thomas.S !  Looking forward to confirmation.

Hi @thomas.S , following up to see if this was resolved based on @Aplynx ‘s advice.

Thanks!

Sorry for the late feedback. 
Since we have not seen any more problems so far, I assume that the problem can also be considered fixed.

All good!  Glad to get late good news versus early bad news!