<?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 using of year in cron schedule in Reporting</title>
    <link>https://community.splunk.com/t5/Reporting/using-of-year-in-cron-schedule/m-p/71526#M1627</link>
    <description>&lt;P&gt;How can one make a cron schedule in Splunk run just in specific year? This can be easily done in 8-digit type of cron schedules but splunk uses just 5 digits.&lt;/P&gt;

&lt;P&gt;The case is that I need to backfill summary index only for several months of current year, but our statistics has these months in 2012 and 2011 years so setting schedule like &lt;CODE&gt;0 0 * 7-9 *&lt;/CODE&gt; will index data in both years that will be redundant and also will take twice more time and space.&lt;/P&gt;

&lt;P&gt;p.s. I can't set earliest time in search or limit time in other way as we need the search to count for all the time.  &lt;/P&gt;</description>
    <pubDate>Wed, 26 Sep 2012 15:08:03 GMT</pubDate>
    <dc:creator>iKate</dc:creator>
    <dc:date>2012-09-26T15:08:03Z</dc:date>
    <item>
      <title>using of year in cron schedule</title>
      <link>https://community.splunk.com/t5/Reporting/using-of-year-in-cron-schedule/m-p/71526#M1627</link>
      <description>&lt;P&gt;How can one make a cron schedule in Splunk run just in specific year? This can be easily done in 8-digit type of cron schedules but splunk uses just 5 digits.&lt;/P&gt;

&lt;P&gt;The case is that I need to backfill summary index only for several months of current year, but our statistics has these months in 2012 and 2011 years so setting schedule like &lt;CODE&gt;0 0 * 7-9 *&lt;/CODE&gt; will index data in both years that will be redundant and also will take twice more time and space.&lt;/P&gt;

&lt;P&gt;p.s. I can't set earliest time in search or limit time in other way as we need the search to count for all the time.  &lt;/P&gt;</description>
      <pubDate>Wed, 26 Sep 2012 15:08:03 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/using-of-year-in-cron-schedule/m-p/71526#M1627</guid>
      <dc:creator>iKate</dc:creator>
      <dc:date>2012-09-26T15:08:03Z</dc:date>
    </item>
    <item>
      <title>Re: using of year in cron schedule</title>
      <link>https://community.splunk.com/t5/Reporting/using-of-year-in-cron-schedule/m-p/71527#M1628</link>
      <description>&lt;P&gt;I didn't think you can specify retroactive cron schedules. Cron schedules dictate when jobs will run in the future. &lt;/P&gt;

&lt;P&gt;Did you look at backfill script ($SPLUNK_HOME/bin/fill_summary_index.py)?&lt;/P&gt;

&lt;P&gt;&lt;A href="http://docs.splunk.com/Documentation/Splunk/4.3.4/Knowledge/Managesummaryindexgapsandoverlaps" target="_blank"&gt;Manage summary index gaps and overlaps&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 12:30:43 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/using-of-year-in-cron-schedule/m-p/71527#M1628</guid>
      <dc:creator>reed_kelly</dc:creator>
      <dc:date>2020-09-28T12:30:43Z</dc:date>
    </item>
    <item>
      <title>Re: using of year in cron schedule</title>
      <link>https://community.splunk.com/t5/Reporting/using-of-year-in-cron-schedule/m-p/71528#M1629</link>
      <description>&lt;P&gt;Yes, I am using this script. And it's exactly about running and writing to summary index your searches, like they were launched in the past with periodicity set in the (cron)schedule.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Sep 2012 22:05:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Reporting/using-of-year-in-cron-schedule/m-p/71528#M1629</guid>
      <dc:creator>iKate</dc:creator>
      <dc:date>2012-09-26T22:05:45Z</dc:date>
    </item>
  </channel>
</rss>

