https://community.splunk.com/t5/Deployment-Architecture/Splunk-high-availability-failover-and-loadbalancers/m-p/80901#M2880 <P>Hello,</P> <P>We are setting up our splunk environment up with a loadbalancer with a failover search head and have found this article that discusses rsync to keep our search heads up to date together <A href="http://wiki.splunk.com/Community:HighAvailabilityAndSplunk">http://wiki.splunk.com/Community:HighAvailabilityAndSplunk</A>. </P> <P>A couple questions come up with this though...</P> <P>1) Are there any other files that should be rsynced other than whats mentioned?<BR /> 2) For certain .conf files that have a hashed password how do we overcome syncing these files and allowing the secondary instance to decrypt the passwords?<BR /> 3) Would you even recommend using loadbalancers in this fashion with rysnc? If not, any alternatives/recommendations?<BR /> 4) Any considerations that I may be missing? </P> <P>Right now we have about 30 users on one search head but would like our deployment to be scalable and resilient.</P> <P>Thanks for the help! </P> Mon, 01 Jul 2013 13:51:07 GMT aaronkorn 2013-07-01T13:51:07Z https://community.splunk.com/t5/Deployment-Architecture/Splunk-high-availability-failover-and-loadbalancers/m-p/80901#M2880 <P>Hello,</P> <P>We are setting up our splunk environment up with a loadbalancer with a failover search head and have found this article that discusses rsync to keep our search heads up to date together <A href="http://wiki.splunk.com/Community:HighAvailabilityAndSplunk">http://wiki.splunk.com/Community:HighAvailabilityAndSplunk</A>. </P> <P>A couple questions come up with this though...</P> <P>1) Are there any other files that should be rsynced other than whats mentioned?<BR /> 2) For certain .conf files that have a hashed password how do we overcome syncing these files and allowing the secondary instance to decrypt the passwords?<BR /> 3) Would you even recommend using loadbalancers in this fashion with rysnc? If not, any alternatives/recommendations?<BR /> 4) Any considerations that I may be missing? </P> <P>Right now we have about 30 users on one search head but would like our deployment to be scalable and resilient.</P> <P>Thanks for the help! </P> Mon, 01 Jul 2013 13:51:07 GMT https://community.splunk.com/t5/Deployment-Architecture/Splunk-high-availability-failover-and-loadbalancers/m-p/80901#M2880 aaronkorn 2013-07-01T13:51:07Z https://community.splunk.com/t5/Deployment-Architecture/Splunk-high-availability-failover-and-loadbalancers/m-p/80902#M2881 <P>Can't help with the other bits as we're running search head pooling ourselves but the shared secret part of the following link might be useful for point 2: <A href="http://wiki.splunk.com/Community:How_to_add_a_search_head_to_your_pool">http://wiki.splunk.com/Community:How_to_add_a_search_head_to_your_pool</A></P> Mon, 01 Jul 2013 14:01:08 GMT https://community.splunk.com/t5/Deployment-Architecture/Splunk-high-availability-failover-and-loadbalancers/m-p/80902#M2881 samhughe 2013-07-01T14:01:08Z