<?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: How to back up hot buckets ? in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-back-up-hot-buckets/m-p/104783#M3882</link>
    <description>&lt;P&gt;Hi Martin,&lt;/P&gt;

&lt;P&gt;How do you determine the updated bucket across muti-site cluster?&lt;/P&gt;

&lt;P&gt;Any link or script to get information ?&lt;/P&gt;

&lt;P&gt;Regards,&lt;/P&gt;</description>
    <pubDate>Wed, 15 Feb 2017 01:17:01 GMT</pubDate>
    <dc:creator>anand_singh17</dc:creator>
    <dc:date>2017-02-15T01:17:01Z</dc:date>
    <item>
      <title>How to back up hot buckets ?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-back-up-hot-buckets/m-p/104780#M3879</link>
      <description>&lt;P&gt;Hi Splunkers,&lt;/P&gt;

&lt;P&gt;I'm now considering of backing up Splunk indexes to prepare for recovery.&lt;BR /&gt;
I know that any buckets without hot are able to back up by copy.&lt;BR /&gt;
Hot buckets are not able to copy because it's always under Splunk process (writing, and so on).&lt;/P&gt;

&lt;P&gt;So we have an option of rolling from hot to warm manually, &lt;BR /&gt;
but it may be not recommended in terms of search performance that we always do that.&lt;/P&gt;

&lt;P&gt;And there is an other way to back up hot buckets. That is a snapshot.&lt;BR /&gt;
According to Splunk documentation, it seems that snapshots enable us to get backups of hot buckets.&lt;BR /&gt;
However, we don't always have such tools or environments. Splunk clustering either.&lt;/P&gt;

&lt;P&gt;Now I want to ask everyone that how to back up hot buckets ?&lt;BR /&gt;
Giving up to backup hot buckets ?&lt;BR /&gt;
Thank you for your help.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jul 2013 02:44:19 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-back-up-hot-buckets/m-p/104780#M3879</guid>
      <dc:creator>sunrise</dc:creator>
      <dc:date>2013-07-24T02:44:19Z</dc:date>
    </item>
    <item>
      <title>Re: How to back up hot buckets ?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-back-up-hot-buckets/m-p/104781#M3880</link>
      <description>&lt;P&gt;I see at least two strategies that work regardless of special tools or snapshot capability.&lt;/P&gt;

&lt;P&gt;First, you could schedule a full backup every day or week, and roll hot buckets before that - depending on your specific environment, adding one roll per day or week should not impact search performance too badly. For high-volume indexes you might go from five to six buckets per day, and for low-volume indexes you may go from one bucket per week to one bucket per day - maybe a bit worse if you have several open hot buckets at roll time.&lt;/P&gt;

&lt;P&gt;Second, you could rsync (or similar) your warm buckets as soon as splunk rolls them on its own. That way you always loose hot buckets in a crash, but your warm buckets that were backed up may be newer than with method 1. That pretty much depends on how long a bucket remains hot - if that can be weeks then you're better off forcing a roll every now and then.&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jul 2013 07:59:45 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-back-up-hot-buckets/m-p/104781#M3880</guid>
      <dc:creator>martin_mueller</dc:creator>
      <dc:date>2013-07-24T07:59:45Z</dc:date>
    </item>
    <item>
      <title>Re: How to back up hot buckets ?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-back-up-hot-buckets/m-p/104782#M3881</link>
      <description>&lt;P&gt;Thank you, martin_mueller. Very good answer !!&lt;/P&gt;</description>
      <pubDate>Wed, 24 Jul 2013 08:07:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-back-up-hot-buckets/m-p/104782#M3881</guid>
      <dc:creator>sunrise</dc:creator>
      <dc:date>2013-07-24T08:07:37Z</dc:date>
    </item>
    <item>
      <title>Re: How to back up hot buckets ?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-back-up-hot-buckets/m-p/104783#M3882</link>
      <description>&lt;P&gt;Hi Martin,&lt;/P&gt;

&lt;P&gt;How do you determine the updated bucket across muti-site cluster?&lt;/P&gt;

&lt;P&gt;Any link or script to get information ?&lt;/P&gt;

&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Wed, 15 Feb 2017 01:17:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-back-up-hot-buckets/m-p/104783#M3882</guid>
      <dc:creator>anand_singh17</dc:creator>
      <dc:date>2017-02-15T01:17:01Z</dc:date>
    </item>
    <item>
      <title>Re: How to back up hot buckets ?</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/How-to-back-up-hot-buckets/m-p/104784#M3883</link>
      <description>&lt;P&gt;2017 update.  I'm not sure this is even a valid question any more.  Every decent Linux distribution -and- modern copy of Windows supports snapshots natively as part of the operating system.  In today's world, I can't think of a good reason why you can't use snapshots as your primary backup mechanism, unless you are still using Windows 2003 or Red Hat 5.  In which case, upgrading to a modern operating system will give you snapshotting natively.&lt;/P&gt;</description>
      <pubDate>Wed, 15 Feb 2017 04:02:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/How-to-back-up-hot-buckets/m-p/104784#M3883</guid>
      <dc:creator>dwaddle</dc:creator>
      <dc:date>2017-02-15T04:02:48Z</dc:date>
    </item>
  </channel>
</rss>

