In our content database enabled by RBS SharePoint 2013, we found that some files that meet the minimum size threshold of blob objects to be stored in RBS are directly stored in the database. We have 2 WFE / APP servers with RBS installed. I suspect that the secondary server is not configured correctly with RBS and that any request that is routed to it to create documents causes it to be stored directly in the database.
Looking at our installation scripts, I find that for the secondary server, the RBS installation command contains only the following components.
ADDLOCAL = EnableRBS, FilestreamRunScript
I guess this is incorrect, and requires these:
ADDLOCAL = Client, Docs, Maintainer, ServerScript, FilestreamClient, FilestreamServer
Without affecting the primary server and the RBS store, can I simply safely uninstall RBS on the secondary SharePoint server from the Control Panel, and then run the command-line installation with the appropriate features to install it? again?