<?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: Upgrading a splunk server hardware in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Upgrading-a-splunk-server-hardware/m-p/86982#M18052</link>
    <description>&lt;P&gt;What options do recommend for using rsync to move the splunk database (indexes) to the new server? I have my splunkDB outside of the /opt/splunk directory tree because it is a separate volume (raid array). I've already successfully used tar to get /opt/splunk over there and unpacked it and have it running, but I think that tar is not the tool for moving the index data as it is so large. I'm planning to shut down both splunk instances before moving the splunkdB, is there anything else to do before moving (copying it, actually).&lt;/P&gt;</description>
    <pubDate>Tue, 21 Feb 2017 19:24:48 GMT</pubDate>
    <dc:creator>wrangler2x</dc:creator>
    <dc:date>2017-02-21T19:24:48Z</dc:date>
    <item>
      <title>Upgrading a splunk server hardware</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Upgrading-a-splunk-server-hardware/m-p/86978#M18048</link>
      <description>&lt;P&gt;We are in the process of upgrading our splunk server hardware and I was looking for some sort of best practice.  I am hoping to keep everything the same in the new server (ip, name ect ect)  So it is more of a clone that I am looking to do.&lt;/P&gt;

&lt;P&gt;Any feed back would be appreciated.&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jan 2013 21:51:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Upgrading-a-splunk-server-hardware/m-p/86978#M18048</guid>
      <dc:creator>freeborn</dc:creator>
      <dc:date>2013-01-14T21:51:33Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading a splunk server hardware</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Upgrading-a-splunk-server-hardware/m-p/86979#M18049</link>
      <description>&lt;P&gt;Hi freeborn&lt;/P&gt;

&lt;P&gt;as long as the OS stays the same, meaning during your hardware update you will not change the OS, it is more a matter of how to clone the OS and data.&lt;/P&gt;

&lt;P&gt;If you setup both servers (old and new in parallel) Splunk itself can be moved/cloned/migrated onto new hardware, read more about this in the &lt;A href="http://wiki.splunk.com/Deploy:Migrating_a_Splunk_Install"&gt;Migrating a Splunk Install&lt;/A&gt; wiki.&lt;/P&gt;

&lt;P&gt;Here is the link &lt;A href="http://wiki.splunk.com/Deploy:Migrating_a_Splunk_Install"&gt;http://wiki.splunk.com/Deploy:Migrating_a_Splunk_Install&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;hope this helps.....&lt;/P&gt;

&lt;P&gt;cheers,&lt;/P&gt;

&lt;P&gt;MuS&lt;/P&gt;</description>
      <pubDate>Tue, 15 Jan 2013 08:31:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Upgrading-a-splunk-server-hardware/m-p/86979#M18049</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2013-01-15T08:31:35Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading a splunk server hardware</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Upgrading-a-splunk-server-hardware/m-p/86980#M18050</link>
      <description>&lt;P&gt;Your link is missing one 'l'. Correct link is &lt;A href="http://wiki.splunk.com/Deploy:Migrating_a_Splunk_Install"&gt;http://wiki.splunk.com/Deploy:Migrating_a_Splunk_Install&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 28 Dec 2016 18:19:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Upgrading-a-splunk-server-hardware/m-p/86980#M18050</guid>
      <dc:creator>dale_lakes8769</dc:creator>
      <dc:date>2016-12-28T18:19:17Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading a splunk server hardware</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Upgrading-a-splunk-server-hardware/m-p/86981#M18051</link>
      <description>&lt;P&gt;Thanks for the hint @dale.lakes8769 ! &lt;BR /&gt;
I had to add a line break after the link otherwise the second &lt;CODE&gt;l&lt;/CODE&gt; is being cut off - very strange ?!? Anyway added the link as well.&lt;/P&gt;</description>
      <pubDate>Thu, 29 Dec 2016 20:07:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Upgrading-a-splunk-server-hardware/m-p/86981#M18051</guid>
      <dc:creator>MuS</dc:creator>
      <dc:date>2016-12-29T20:07:57Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrading a splunk server hardware</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Upgrading-a-splunk-server-hardware/m-p/86982#M18052</link>
      <description>&lt;P&gt;What options do recommend for using rsync to move the splunk database (indexes) to the new server? I have my splunkDB outside of the /opt/splunk directory tree because it is a separate volume (raid array). I've already successfully used tar to get /opt/splunk over there and unpacked it and have it running, but I think that tar is not the tool for moving the index data as it is so large. I'm planning to shut down both splunk instances before moving the splunkdB, is there anything else to do before moving (copying it, actually).&lt;/P&gt;</description>
      <pubDate>Tue, 21 Feb 2017 19:24:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Upgrading-a-splunk-server-hardware/m-p/86982#M18052</guid>
      <dc:creator>wrangler2x</dc:creator>
      <dc:date>2017-02-21T19:24:48Z</dc:date>
    </item>
  </channel>
</rss>

