<?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: When should I restore from backup? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/When-should-I-restore-from-backup/m-p/33373#M5984</link>
    <description>&lt;P&gt;I guess I'm not sure why you want to restore an index from backup. It's an extremely abnormal condition, and I suppose that many things that went wrong could cause it, but if it did, someone is going to see something go wrong in the application, not the log.&lt;/P&gt;</description>
    <pubDate>Thu, 19 Aug 2010 10:39:59 GMT</pubDate>
    <dc:creator>gkanapathy</dc:creator>
    <dc:date>2010-08-19T10:39:59Z</dc:date>
    <item>
      <title>When should I restore from backup?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/When-should-I-restore-from-backup/m-p/33372#M5983</link>
      <description>&lt;P&gt;What events should I be watching for in my Splunk logs?  Does anyone have a list of specific error codes that would indicate the need to restore an index? &lt;/P&gt;</description>
      <pubDate>Thu, 19 Aug 2010 05:35:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/When-should-I-restore-from-backup/m-p/33372#M5983</guid>
      <dc:creator>pdevlin</dc:creator>
      <dc:date>2010-08-19T05:35:55Z</dc:date>
    </item>
    <item>
      <title>Re: When should I restore from backup?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/When-should-I-restore-from-backup/m-p/33373#M5984</link>
      <description>&lt;P&gt;I guess I'm not sure why you want to restore an index from backup. It's an extremely abnormal condition, and I suppose that many things that went wrong could cause it, but if it did, someone is going to see something go wrong in the application, not the log.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Aug 2010 10:39:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/When-should-I-restore-from-backup/m-p/33373#M5984</guid>
      <dc:creator>gkanapathy</dc:creator>
      <dc:date>2010-08-19T10:39:59Z</dc:date>
    </item>
    <item>
      <title>Re: When should I restore from backup?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/When-should-I-restore-from-backup/m-p/33374#M5985</link>
      <description>&lt;P&gt;Index corruption, disk errors or VM/OS failures that cause file corruption, etc.  I'd like to monitor Splunk logs for those specific errors that indicate an index is corrupt and/or not usable. Yes we would notice in the application that something is wrong but knowing the exact errors which indicate a corrupt index is vital for basic maintenance and support. Do you know if there is a complete list of Splunk error codes and what they mean?&lt;/P&gt;</description>
      <pubDate>Fri, 20 Aug 2010 01:14:34 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/When-should-I-restore-from-backup/m-p/33374#M5985</guid>
      <dc:creator>pdevlin</dc:creator>
      <dc:date>2010-08-20T01:14:34Z</dc:date>
    </item>
  </channel>
</rss>

