<?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 Backing up is not automated? in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Backing-up-is-not-automated/m-p/184691#M6897</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;What is the standard practice to clear up space ? for example I have configured splunk to receive syslogs everyday. However now my disk space keeps filling up. I want to backup my index (for the syslogs) , truncate data in the index and start afresh. Isn't there a seamless or "automated" way to do index backing up?&lt;BR /&gt;
thanks&lt;/P&gt;</description>
    <pubDate>Sat, 09 May 2015 15:11:18 GMT</pubDate>
    <dc:creator>michael_lee</dc:creator>
    <dc:date>2015-05-09T15:11:18Z</dc:date>
    <item>
      <title>Backing up is not automated?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Backing-up-is-not-automated/m-p/184691#M6897</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;What is the standard practice to clear up space ? for example I have configured splunk to receive syslogs everyday. However now my disk space keeps filling up. I want to backup my index (for the syslogs) , truncate data in the index and start afresh. Isn't there a seamless or "automated" way to do index backing up?&lt;BR /&gt;
thanks&lt;/P&gt;</description>
      <pubDate>Sat, 09 May 2015 15:11:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Backing-up-is-not-automated/m-p/184691#M6897</guid>
      <dc:creator>michael_lee</dc:creator>
      <dc:date>2015-05-09T15:11:18Z</dc:date>
    </item>
    <item>
      <title>Re: Backing up is not automated?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Backing-up-is-not-automated/m-p/184692#M6898</link>
      <description>&lt;P&gt;I'd suggest you read through &lt;A href="http://wiki.splunk.com/Deploy:BucketRotationAndRetention"&gt;this&lt;/A&gt; and familiarize yourself with how Splunk manages index data for you. Data is stored in buckets, which go through multiple stages, namely from HOT (actively written to) to WARM (read-only) to COLD (read-only) to FROZEN (not searchable).&lt;BR /&gt;
You have full control over how long you keep data in each stage, either by specifying a time period or by limiting how much disk space each stage can consume.&lt;/P&gt;

&lt;P&gt;This is fully automatic, but it DOES NOT replace backing up your data, if you are concerned about data loss. Take a gander &lt;A href="http://wiki.splunk.com/Community:BestPracticesForBackingUp"&gt;at this&lt;/A&gt; for best practices around backing up your index data and/or consider using index replication to guard against indexer/data loss.&lt;/P&gt;</description>
      <pubDate>Sat, 09 May 2015 21:29:30 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Backing-up-is-not-automated/m-p/184692#M6898</guid>
      <dc:creator>s2_splunk</dc:creator>
      <dc:date>2015-05-09T21:29:30Z</dc:date>
    </item>
  </channel>
</rss>

