<?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: 2 year retention policy in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/2-year-retention-policy/m-p/81722#M97134</link>
    <description>&lt;P&gt;No, that's not really correct.&lt;/P&gt;

&lt;P&gt;You should have a look at the following reference:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.3/Indexer/Setaretirementandarchivingpolicy"&gt;http://docs.splunk.com/Documentation/Splunk/5.0.3/Indexer/Setaretirementandarchivingpolicy&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;But at a highlevel you will need to use the &lt;CODE&gt;frozenTimePeriodInSecs&lt;/CODE&gt; parameter for each Index stanza OR globally in your &lt;CODE&gt;indexes.conf&lt;/CODE&gt; file.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.3/admin/Indexesconf"&gt;http://docs.splunk.com/Documentation/Splunk/5.0.3/admin/Indexesconf&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Hope this helps.&lt;/P&gt;

&lt;P&gt;P.S. Plan this change correctly... you may lose your data incorrectly... would be a good idea to do a backup of data first!&lt;/P&gt;</description>
    <pubDate>Tue, 02 Jul 2013 12:47:49 GMT</pubDate>
    <dc:creator>MHibbin</dc:creator>
    <dc:date>2013-07-02T12:47:49Z</dc:date>
    <item>
      <title>2 year retention policy</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/2-year-retention-policy/m-p/81721#M97133</link>
      <description>&lt;P&gt;Hi guy, how do I go about setting a limit on our data retention.&lt;/P&gt;

&lt;P&gt;I need the data on the indexer to be deleted after 2 years, is there a way to do tjis via the web interface or is this somthing that must be done in the inputs.conf on the indexer itself.&lt;/P&gt;

&lt;P&gt;Also am I correct in thinking that you have to define the time in seconds if going down the inputs.conf route ?&lt;/P&gt;

&lt;P&gt;Cheers&lt;/P&gt;

&lt;P&gt;Aaron&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jul 2013 10:43:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/2-year-retention-policy/m-p/81721#M97133</guid>
      <dc:creator>AaronMoorcroft</dc:creator>
      <dc:date>2013-07-02T10:43:51Z</dc:date>
    </item>
    <item>
      <title>Re: 2 year retention policy</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/2-year-retention-policy/m-p/81722#M97134</link>
      <description>&lt;P&gt;No, that's not really correct.&lt;/P&gt;

&lt;P&gt;You should have a look at the following reference:&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.3/Indexer/Setaretirementandarchivingpolicy"&gt;http://docs.splunk.com/Documentation/Splunk/5.0.3/Indexer/Setaretirementandarchivingpolicy&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;But at a highlevel you will need to use the &lt;CODE&gt;frozenTimePeriodInSecs&lt;/CODE&gt; parameter for each Index stanza OR globally in your &lt;CODE&gt;indexes.conf&lt;/CODE&gt; file.&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/5.0.3/admin/Indexesconf"&gt;http://docs.splunk.com/Documentation/Splunk/5.0.3/admin/Indexesconf&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Hope this helps.&lt;/P&gt;

&lt;P&gt;P.S. Plan this change correctly... you may lose your data incorrectly... would be a good idea to do a backup of data first!&lt;/P&gt;</description>
      <pubDate>Tue, 02 Jul 2013 12:47:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/2-year-retention-policy/m-p/81722#M97134</guid>
      <dc:creator>MHibbin</dc:creator>
      <dc:date>2013-07-02T12:47:49Z</dc:date>
    </item>
  </channel>
</rss>

