<?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 Remove Raw data from splunk server in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Remove-Raw-data-from-splunk-server/m-p/21964#M96527</link>
    <description>&lt;P&gt;We are running splunk 4.2.3 on a RHEL 5.7 server and nearly 250 universal forwarders forwarding data to this splunk server. Right now we have 2 mounts created, 1 for hot/warm db's and 1 for colddbs. We are indexing appr. 80G of data everyday and space is filling up very fast and we have appr.1TB of data. Out of this raw data is consuming more space. I am planning to remove rawdata from the colddb. IS IT OK TO REMOVE THE RAWDATA FROM COLDDB? i guess splunk will not touch rawdata's. &lt;/P&gt;

&lt;P&gt;output from one of the cold db- &lt;/P&gt;

&lt;H1&gt;ls -ltr&lt;/H1&gt;

&lt;P&gt;total 657436&lt;BR /&gt;
-rw------- 1 root root  72262461 Apr  7 23:22 1331548047-1331389182-7634922573347700672.tsidx&lt;BR /&gt;
-rw------- 1 root root   1695441 Apr  7 23:22 1331515778-1331389730-3545913347331342493.tsidx&lt;BR /&gt;
-rw------- 1 root root  69248060 Apr  7 23:22 Strings.data&lt;BR /&gt;
drwx------ 2 root root      4096 Apr  7 23:22 rawdata&lt;BR /&gt;
-rw------- 1 root root     11557 Apr  7 23:22 Hosts.data&lt;BR /&gt;
-rw------- 1 root root  14083668 Apr  7 23:22 1331515766-1331389660-4513270691130261649.tsidx&lt;BR /&gt;
-rw------- 1 root root         0 Apr  7 23:22 splunk-need-optimize.dat&lt;BR /&gt;
-rw------- 1 root root        71 Apr  7 23:22 splunk-autogen-params.dat&lt;BR /&gt;
-rw------- 1 root root      4646 Apr  7 23:22 SourceTypes.data&lt;BR /&gt;
-rw------- 1 root root     23812 Apr  7 23:22 Sources.data&lt;BR /&gt;
-rw------- 1 root root        49 Apr  7 23:22 optimize.result&lt;BR /&gt;
-rw------- 1 root root  72468285 Apr  7 23:22 merged_lexicon.lex&lt;BR /&gt;
-rw------- 1 root root 442641753 Apr  7 23:22 1331547238-1331386067-4874605572483200482.tsidx&lt;/P&gt;</description>
    <pubDate>Mon, 09 Apr 2012 01:46:06 GMT</pubDate>
    <dc:creator>npandith</dc:creator>
    <dc:date>2012-04-09T01:46:06Z</dc:date>
    <item>
      <title>Remove Raw data from splunk server</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Remove-Raw-data-from-splunk-server/m-p/21964#M96527</link>
      <description>&lt;P&gt;We are running splunk 4.2.3 on a RHEL 5.7 server and nearly 250 universal forwarders forwarding data to this splunk server. Right now we have 2 mounts created, 1 for hot/warm db's and 1 for colddbs. We are indexing appr. 80G of data everyday and space is filling up very fast and we have appr.1TB of data. Out of this raw data is consuming more space. I am planning to remove rawdata from the colddb. IS IT OK TO REMOVE THE RAWDATA FROM COLDDB? i guess splunk will not touch rawdata's. &lt;/P&gt;

&lt;P&gt;output from one of the cold db- &lt;/P&gt;

&lt;H1&gt;ls -ltr&lt;/H1&gt;

&lt;P&gt;total 657436&lt;BR /&gt;
-rw------- 1 root root  72262461 Apr  7 23:22 1331548047-1331389182-7634922573347700672.tsidx&lt;BR /&gt;
-rw------- 1 root root   1695441 Apr  7 23:22 1331515778-1331389730-3545913347331342493.tsidx&lt;BR /&gt;
-rw------- 1 root root  69248060 Apr  7 23:22 Strings.data&lt;BR /&gt;
drwx------ 2 root root      4096 Apr  7 23:22 rawdata&lt;BR /&gt;
-rw------- 1 root root     11557 Apr  7 23:22 Hosts.data&lt;BR /&gt;
-rw------- 1 root root  14083668 Apr  7 23:22 1331515766-1331389660-4513270691130261649.tsidx&lt;BR /&gt;
-rw------- 1 root root         0 Apr  7 23:22 splunk-need-optimize.dat&lt;BR /&gt;
-rw------- 1 root root        71 Apr  7 23:22 splunk-autogen-params.dat&lt;BR /&gt;
-rw------- 1 root root      4646 Apr  7 23:22 SourceTypes.data&lt;BR /&gt;
-rw------- 1 root root     23812 Apr  7 23:22 Sources.data&lt;BR /&gt;
-rw------- 1 root root        49 Apr  7 23:22 optimize.result&lt;BR /&gt;
-rw------- 1 root root  72468285 Apr  7 23:22 merged_lexicon.lex&lt;BR /&gt;
-rw------- 1 root root 442641753 Apr  7 23:22 1331547238-1331386067-4874605572483200482.tsidx&lt;/P&gt;</description>
      <pubDate>Mon, 09 Apr 2012 01:46:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Remove-Raw-data-from-splunk-server/m-p/21964#M96527</guid>
      <dc:creator>npandith</dc:creator>
      <dc:date>2012-04-09T01:46:06Z</dc:date>
    </item>
    <item>
      <title>Re: Remove Raw data from splunk server</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Remove-Raw-data-from-splunk-server/m-p/21965#M96528</link>
      <description>&lt;P&gt;Hum, not the best idea, removing raw data means that you will not be able to access the data after, therefore those cold buckets will be useless.&lt;/P&gt;

&lt;P&gt;if you really want to delete cold buckets, then setup a retention policy (on total index size or on time retention.)&lt;/P&gt;</description>
      <pubDate>Mon, 09 Apr 2012 06:06:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Remove-Raw-data-from-splunk-server/m-p/21965#M96528</guid>
      <dc:creator>yannK</dc:creator>
      <dc:date>2012-04-09T06:06:12Z</dc:date>
    </item>
    <item>
      <title>Re: Remove Raw data from splunk server</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Remove-Raw-data-from-splunk-server/m-p/21966#M96529</link>
      <description>&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/4.3.1/admin/Setaretirementandarchivingpolicy"&gt;http://docs.splunk.com/Documentation/Splunk/4.3.1/admin/Setaretirementandarchivingpolicy&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 09 Apr 2012 06:48:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Remove-Raw-data-from-splunk-server/m-p/21966#M96529</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2012-04-09T06:48:57Z</dc:date>
    </item>
  </channel>
</rss>

