<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic How to copy data from an index to another machine in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/How-to-copy-data-from-an-index-to-another-machine/m-p/691289#M114982</link>
    <description>&lt;P&gt;Hi&lt;BR /&gt;I have a use case that involves copying historical data from a 3-indexer cluster (6 months old) to another machine. I have considered two potential solutions:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Stop one of the indexers and copy the index from the source to the destination. The only drawback could be that the data might be incomplete, but this is not a concern as the data is for testing purposes. Given the volume of data, this process could take a significant amount of time.&lt;/LI&gt;&lt;LI&gt;Create a new index using the collect command with the required set of data, then copy the index to the other machine. I believe this would be the best way to implement this use case. However, the downside is that the data volume is quite large and might take a considerable amount of time to execute the SPL in the search head, potentially affecting the performance of the SH. I am unsure if the collect command can handle such a large search and create an index. Is there a limitation on the size of the data when using the collect command?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;BR /&gt;Please advise on how to best handle this scenario.&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Pravin&lt;/P&gt;</description>
    <pubDate>Fri, 21 Jun 2024 11:53:40 GMT</pubDate>
    <dc:creator>_pravin</dc:creator>
    <dc:date>2024-06-21T11:53:40Z</dc:date>
    <item>
      <title>How to copy data from an index to another machine</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/How-to-copy-data-from-an-index-to-another-machine/m-p/691289#M114982</link>
      <description>&lt;P&gt;Hi&lt;BR /&gt;I have a use case that involves copying historical data from a 3-indexer cluster (6 months old) to another machine. I have considered two potential solutions:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Stop one of the indexers and copy the index from the source to the destination. The only drawback could be that the data might be incomplete, but this is not a concern as the data is for testing purposes. Given the volume of data, this process could take a significant amount of time.&lt;/LI&gt;&lt;LI&gt;Create a new index using the collect command with the required set of data, then copy the index to the other machine. I believe this would be the best way to implement this use case. However, the downside is that the data volume is quite large and might take a considerable amount of time to execute the SPL in the search head, potentially affecting the performance of the SH. I am unsure if the collect command can handle such a large search and create an index. Is there a limitation on the size of the data when using the collect command?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;BR /&gt;Please advise on how to best handle this scenario.&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Pravin&lt;/P&gt;</description>
      <pubDate>Fri, 21 Jun 2024 11:53:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/How-to-copy-data-from-an-index-to-another-machine/m-p/691289#M114982</guid>
      <dc:creator>_pravin</dc:creator>
      <dc:date>2024-06-21T11:53:40Z</dc:date>
    </item>
  </channel>
</rss>

