https://community.splunk.com/t5/Deployment-Architecture/How-to-clone-indexers-image/m-p/353587#M19348 <P>It is not recommended to clone the indexers configurations by copying the whole $SPLUNK_HOME directory. We suggest you to instal Splunk software package and have deployment server to distribute configurations to indexers. As just copying the whole directory image, the indexer's GUID will all be the same and it will cause some unexpected behaviour. </P> <P>If you have used copying files to clone indexer's image, you can use the below command and generate another GUID. </P> <P>./splunk clone-prep-clear-config </P> Fri, 28 Apr 2017 08:58:35 GMT mwong 2017-04-28T08:58:35Z https://community.splunk.com/t5/Deployment-Architecture/How-to-clone-indexers-image/m-p/353586#M19347 <P>I plan to install multiple indexers with same configuration. Can I copy all the $SPLUNK_HOME files and create indexer instance?</P> Fri, 28 Apr 2017 08:51:36 GMT https://community.splunk.com/t5/Deployment-Architecture/How-to-clone-indexers-image/m-p/353586#M19347 tlam_splunk 2017-04-28T08:51:36Z https://community.splunk.com/t5/Deployment-Architecture/How-to-clone-indexers-image/m-p/353587#M19348 <P>It is not recommended to clone the indexers configurations by copying the whole $SPLUNK_HOME directory. We suggest you to instal Splunk software package and have deployment server to distribute configurations to indexers. As just copying the whole directory image, the indexer's GUID will all be the same and it will cause some unexpected behaviour. </P> <P>If you have used copying files to clone indexer's image, you can use the below command and generate another GUID. </P> <P>./splunk clone-prep-clear-config </P> Fri, 28 Apr 2017 08:58:35 GMT https://community.splunk.com/t5/Deployment-Architecture/How-to-clone-indexers-image/m-p/353587#M19348 mwong 2017-04-28T08:58:35Z