<?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: Data Retention Policy in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Data-Retention-Policy/m-p/141862#M29062</link>
    <description>&lt;P&gt;The point I was making is that your requirements don't add up - how do you know that you need 30 days of cold data, if you don't know how much data you have in hot/warm? If you're indexing 10 MB/day, the &lt;CODE&gt;hot+warm&lt;/CODE&gt; storage would last for almost 10 years - then what's the point of another 30 days of &lt;CODE&gt;cold&lt;/CODE&gt; (300 MB)? &lt;/P&gt;

&lt;P&gt;If you index 150GB/day, the &lt;CODE&gt;hot+warm&lt;/CODE&gt; lasts 2 days, and the &lt;CODE&gt;cold&lt;/CODE&gt; storage would be almost 5 TB. These two extremes will change the storage needs quite a lot. &lt;/P&gt;

&lt;P&gt;Normally, you'll have a retention time requirement for data that is online (&lt;CODE&gt;hot+warm+cold&lt;/CODE&gt;) and offline (&lt;CODE&gt;frozen&lt;/CODE&gt;).&lt;/P&gt;</description>
    <pubDate>Mon, 10 Feb 2014 07:36:56 GMT</pubDate>
    <dc:creator>kristian_kolb</dc:creator>
    <dc:date>2014-02-10T07:36:56Z</dc:date>
    <item>
      <title>Data Retention Policy</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Data-Retention-Policy/m-p/141859#M29059</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;

&lt;P&gt;I am trying to setup the data retention policy in a way that my data in hot db stays for 1 day, 10 GB of data in warm and 30 days in cold. I have defined frozenTimePeriodInSecs = 7776000. However i am not able to identify the parameters to be set for hot db and warm db. please suggest.&lt;/P&gt;

&lt;P&gt;regards,&lt;BR /&gt;
Sourabh &lt;/P&gt;</description>
      <pubDate>Fri, 07 Feb 2014 11:22:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Data-Retention-Policy/m-p/141859#M29059</guid>
      <dc:creator>sourabh_v</dc:creator>
      <dc:date>2014-02-07T11:22:46Z</dc:date>
    </item>
    <item>
      <title>Re: Data Retention Policy</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Data-Retention-Policy/m-p/141860#M29060</link>
      <description>&lt;P&gt;It's hard to make this kind of combination without knowing how much data you are actually indexing on a daily basis. There are simply no configuration parameters that fully implement such a retention policy. Also, it's a bit hard to understand the underlying requirements for such a policy.&lt;/P&gt;

&lt;P&gt;Normally you would have a retention time requirement, say one year or 3 months, and possibly some constraint on the size or cost for fast/slow storage, which would force you to play around with when to move from warm to cold.&lt;/P&gt;

&lt;P&gt;Given the docs for indexes.conf, I would suggest;&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[your_index]
maxDataSize = 500
maxHotSpanSecs = 86400
homePath.maxDataSizeMB = 11000
maxTotalDataSizeMB = large number here, possibly larger than the default 500000
frozenTimePeriodInSecs = your actual retention time for all data
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;/k&lt;/P&gt;</description>
      <pubDate>Fri, 07 Feb 2014 12:16:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Data-Retention-Policy/m-p/141860#M29060</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2014-02-07T12:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: Data Retention Policy</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Data-Retention-Policy/m-p/141861#M29061</link>
      <description>&lt;P&gt;Thanks Kristian for your input. indexs.conf spec file says that the maxHotSpanSecs will induce the snapping behavior and its for both hot/warm buckets. My requirement is&lt;BR /&gt;
1. Data to be retained in hot bucket - 1 day (86400 secs)&lt;BR /&gt;
2. Data in warm bucket = 300 GB&lt;BR /&gt;
3. Data in Cold bucket = 30 Days&lt;/P&gt;

&lt;P&gt;I am not sure how the snapping behavior would affect my data?&lt;/P&gt;</description>
      <pubDate>Mon, 10 Feb 2014 06:09:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Data-Retention-Policy/m-p/141861#M29061</guid>
      <dc:creator>sourabh_v</dc:creator>
      <dc:date>2014-02-10T06:09:24Z</dc:date>
    </item>
    <item>
      <title>Re: Data Retention Policy</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Data-Retention-Policy/m-p/141862#M29062</link>
      <description>&lt;P&gt;The point I was making is that your requirements don't add up - how do you know that you need 30 days of cold data, if you don't know how much data you have in hot/warm? If you're indexing 10 MB/day, the &lt;CODE&gt;hot+warm&lt;/CODE&gt; storage would last for almost 10 years - then what's the point of another 30 days of &lt;CODE&gt;cold&lt;/CODE&gt; (300 MB)? &lt;/P&gt;

&lt;P&gt;If you index 150GB/day, the &lt;CODE&gt;hot+warm&lt;/CODE&gt; lasts 2 days, and the &lt;CODE&gt;cold&lt;/CODE&gt; storage would be almost 5 TB. These two extremes will change the storage needs quite a lot. &lt;/P&gt;

&lt;P&gt;Normally, you'll have a retention time requirement for data that is online (&lt;CODE&gt;hot+warm+cold&lt;/CODE&gt;) and offline (&lt;CODE&gt;frozen&lt;/CODE&gt;).&lt;/P&gt;</description>
      <pubDate>Mon, 10 Feb 2014 07:36:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Data-Retention-Policy/m-p/141862#M29062</guid>
      <dc:creator>kristian_kolb</dc:creator>
      <dc:date>2014-02-10T07:36:56Z</dc:date>
    </item>
  </channel>
</rss>

