<?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: How do I save data when moving from warm to cold buckets? in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/How-do-I-save-data-when-moving-from-warm-to-cold-buckets/m-p/153903#M5763</link>
    <description>&lt;P&gt;Any specific reason to save the warm buckets?&lt;/P&gt;</description>
    <pubDate>Tue, 04 Aug 2015 16:47:24 GMT</pubDate>
    <dc:creator>somesoni2</dc:creator>
    <dc:date>2015-08-04T16:47:24Z</dc:date>
    <item>
      <title>How do I save data when moving from warm to cold buckets?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-do-I-save-data-when-moving-from-warm-to-cold-buckets/m-p/153901#M5761</link>
      <description>&lt;P&gt;Hi, &lt;/P&gt;

&lt;P&gt;I want to figure out a way to backup the Splunk data when the index is transferring from a Warm bucket to a cold bucket. Preferably I would like a trigger to back up all the stuff in the warm bucket when it's about to be moved to a cold bucket.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Aug 2015 14:32:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-do-I-save-data-when-moving-from-warm-to-cold-buckets/m-p/153901#M5761</guid>
      <dc:creator>jananth1</dc:creator>
      <dc:date>2015-08-04T14:32:24Z</dc:date>
    </item>
    <item>
      <title>Re: How do I save data when moving from warm to cold buckets?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-do-I-save-data-when-moving-from-warm-to-cold-buckets/m-p/153902#M5762</link>
      <description>&lt;P&gt;The first thought, that comes to mind, is to use &lt;CODE&gt;rsync&lt;/CODE&gt; on a cron schedule that a little aggressive so you can make sure that you aren't ever missing any buckets. &lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;rsync -a -v --ignore-existing  src dst&lt;/CODE&gt;&lt;/P&gt;

&lt;P&gt;&lt;CODE&gt;-a&lt;/CODE&gt; archive mode&lt;BR /&gt;
&lt;CODE&gt;-v&lt;/CODE&gt; verbose mode&lt;BR /&gt;
&lt;CODE&gt;--ignore-existing&lt;/CODE&gt; skip updating files (since warm buckets are read only anyways)&lt;/P&gt;

&lt;P&gt;This will allow you to copy to remote location - rsync will check to see if there are buckets that haven't been copied, and if they aren't, it will copy them.&lt;/P&gt;

&lt;P&gt;To be honest though, this is just an idea. I'm sure there are lots of ways to do this.&lt;/P&gt;</description>
      <pubDate>Tue, 04 Aug 2015 16:09:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-do-I-save-data-when-moving-from-warm-to-cold-buckets/m-p/153902#M5762</guid>
      <dc:creator>aljohnson_splun</dc:creator>
      <dc:date>2015-08-04T16:09:24Z</dc:date>
    </item>
    <item>
      <title>Re: How do I save data when moving from warm to cold buckets?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-do-I-save-data-when-moving-from-warm-to-cold-buckets/m-p/153903#M5763</link>
      <description>&lt;P&gt;Any specific reason to save the warm buckets?&lt;/P&gt;</description>
      <pubDate>Tue, 04 Aug 2015 16:47:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-do-I-save-data-when-moving-from-warm-to-cold-buckets/m-p/153903#M5763</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2015-08-04T16:47:24Z</dc:date>
    </item>
  </channel>
</rss>

