https://community.splunk.com/t5/Knowledge-Management/SmartStore-Role-of-file-buckets-synced-to-remote-storage-in/m-p/611662#M8991 <P>Do NOT remove this file unless you also change the indexer GUID using splunk clone-prep-clear-config or it will possible corrupt previously uploaded buckets that have been evicted from the local cache.</P><P>clone-prep-clear-config is safe to use because it emulates a new indexer being added to the cluster and it will not upload buckets that already exist that were uploaded by a different indexer.</P><P>If there is any possibility that your data on the indexer is not 100% complete due to eviction, you MUST change the guid when removing .buckets_synced_to_remote_storage</P> Thu, 01 Sep 2022 18:55:07 GMT mdoyle_splunk 2022-09-01T18:55:07Z https://community.splunk.com/t5/Knowledge-Management/SmartStore-Role-of-file-buckets-synced-to-remote-storage-in/m-p/402531#M3487 <P>Lets assume that I have 20 node Indexer cluster deployments. Enabled smart store and migration started but due to a network issue the migration was interrupted. We are trying to figure out the best way to restart a migration. How can that be done? What is role of file .buckets_synced_to_remote_storage in migration?</P> Mon, 28 Apr 2025 20:19:28 GMT https://community.splunk.com/t5/Knowledge-Management/SmartStore-Role-of-file-buckets-synced-to-remote-storage-in/m-p/402531#M3487 rbal_splunk 2025-04-28T20:19:28Z https://community.splunk.com/t5/Knowledge-Management/SmartStore-Role-of-file-buckets-synced-to-remote-storage-in/m-p/402532#M3488 <P>Please contact Splunk Support on detailed process.<BR />Never touch&nbsp;.buckets_synced_to_remote_storage</P><P>&nbsp;</P> Mon, 28 Apr 2025 20:20:21 GMT https://community.splunk.com/t5/Knowledge-Management/SmartStore-Role-of-file-buckets-synced-to-remote-storage-in/m-p/402532#M3488 rbal_splunk 2025-04-28T20:20:21Z https://community.splunk.com/t5/Knowledge-Management/SmartStore-Role-of-file-buckets-synced-to-remote-storage-in/m-p/611662#M8991 <P>Do NOT remove this file unless you also change the indexer GUID using splunk clone-prep-clear-config or it will possible corrupt previously uploaded buckets that have been evicted from the local cache.</P><P>clone-prep-clear-config is safe to use because it emulates a new indexer being added to the cluster and it will not upload buckets that already exist that were uploaded by a different indexer.</P><P>If there is any possibility that your data on the indexer is not 100% complete due to eviction, you MUST change the guid when removing .buckets_synced_to_remote_storage</P> Thu, 01 Sep 2022 18:55:07 GMT https://community.splunk.com/t5/Knowledge-Management/SmartStore-Role-of-file-buckets-synced-to-remote-storage-in/m-p/611662#M8991 mdoyle_splunk 2022-09-01T18:55:07Z