<?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 Re: Migrating Splunk data from NFS to Block storage in Knowledge Management</title>
    <link>https://community.splunk.com/t5/Knowledge-Management/Migrating-Splunk-data-from-NFS-to-Block-storage/m-p/92828#M7343</link>
    <description>&lt;P&gt;The only comment I'll make here is that if you rsync a bucket in its hot state (a directory name like hot_v1_15) and then later rsync again, but this time the bucket has been moved to warm (a name like db_1381409248_1381408249_15), Splunk will refuse to start because of the collision between the bucket IDs (the _15 at the end).&lt;/P&gt;

&lt;P&gt;After your first rsync, but before your cutover, remove any hot buckets from the target system.&lt;/P&gt;</description>
    <pubDate>Thu, 10 Oct 2013 16:50:15 GMT</pubDate>
    <dc:creator>sowings</dc:creator>
    <dc:date>2013-10-10T16:50:15Z</dc:date>
    <item>
      <title>Migrating Splunk data from NFS to Block storage</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Migrating-Splunk-data-from-NFS-to-Block-storage/m-p/92826#M7341</link>
      <description>&lt;P&gt;What is the process from migrating Splunk data from NFS based storage to Block based storage?&lt;/P&gt;</description>
      <pubDate>Thu, 10 Oct 2013 14:50:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Migrating-Splunk-data-from-NFS-to-Block-storage/m-p/92826#M7341</guid>
      <dc:creator>brad63</dc:creator>
      <dc:date>2013-10-10T14:50:56Z</dc:date>
    </item>
    <item>
      <title>Re: Migrating Splunk data from NFS to Block storage</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Migrating-Splunk-data-from-NFS-to-Block-storage/m-p/92827#M7342</link>
      <description>&lt;P&gt;There's nothing really special about NFS when storing the data there (other than performance issues).  I'd just use "rsync -avot" to copy over the data.  That way you can run it prior to your cutover time to get it close.  Then shutdown, rsync a final time, change your configs, and start.  When I'd done similar, though on SAN my multi-TB switchover only took about 15min of downtime.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Oct 2013 16:08:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Migrating-Splunk-data-from-NFS-to-Block-storage/m-p/92827#M7342</guid>
      <dc:creator>mikelanghorst</dc:creator>
      <dc:date>2013-10-10T16:08:15Z</dc:date>
    </item>
    <item>
      <title>Re: Migrating Splunk data from NFS to Block storage</title>
      <link>https://community.splunk.com/t5/Knowledge-Management/Migrating-Splunk-data-from-NFS-to-Block-storage/m-p/92828#M7343</link>
      <description>&lt;P&gt;The only comment I'll make here is that if you rsync a bucket in its hot state (a directory name like hot_v1_15) and then later rsync again, but this time the bucket has been moved to warm (a name like db_1381409248_1381408249_15), Splunk will refuse to start because of the collision between the bucket IDs (the _15 at the end).&lt;/P&gt;

&lt;P&gt;After your first rsync, but before your cutover, remove any hot buckets from the target system.&lt;/P&gt;</description>
      <pubDate>Thu, 10 Oct 2013 16:50:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Knowledge-Management/Migrating-Splunk-data-from-NFS-to-Block-storage/m-p/92828#M7343</guid>
      <dc:creator>sowings</dc:creator>
      <dc:date>2013-10-10T16:50:15Z</dc:date>
    </item>
  </channel>
</rss>

