<?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 Migrate and Upgrade at the same time - best practices? in Installation</title>
    <link>https://community.splunk.com/t5/Installation/Migrate-and-Upgrade-at-the-same-time-best-practices/m-p/78583#M1254</link>
    <description>&lt;P&gt;We are planning to migrate from a Splunk 4.3, single server environment to a version 5, scaled new installation (index cluster, etc).   Any experiences or recommendation on this?  Should we upgrade our existing instance to 5 FIRST, then migrate/expand to a new scaled installation - or install the new environment first, and then import/migrate existing data from the existing 4.3 environment?&lt;/P&gt;</description>
    <pubDate>Thu, 28 Mar 2013 21:32:46 GMT</pubDate>
    <dc:creator>shushry</dc:creator>
    <dc:date>2013-03-28T21:32:46Z</dc:date>
    <item>
      <title>Migrate and Upgrade at the same time - best practices?</title>
      <link>https://community.splunk.com/t5/Installation/Migrate-and-Upgrade-at-the-same-time-best-practices/m-p/78583#M1254</link>
      <description>&lt;P&gt;We are planning to migrate from a Splunk 4.3, single server environment to a version 5, scaled new installation (index cluster, etc).   Any experiences or recommendation on this?  Should we upgrade our existing instance to 5 FIRST, then migrate/expand to a new scaled installation - or install the new environment first, and then import/migrate existing data from the existing 4.3 environment?&lt;/P&gt;</description>
      <pubDate>Thu, 28 Mar 2013 21:32:46 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Migrate-and-Upgrade-at-the-same-time-best-practices/m-p/78583#M1254</guid>
      <dc:creator>shushry</dc:creator>
      <dc:date>2013-03-28T21:32:46Z</dc:date>
    </item>
    <item>
      <title>Re: Migrate and Upgrade at the same time - best practices?</title>
      <link>https://community.splunk.com/t5/Installation/Migrate-and-Upgrade-at-the-same-time-best-practices/m-p/78584#M1255</link>
      <description>&lt;P&gt;Same plans here, from 4.3.6 to the latest 5+.&lt;BR /&gt;
I reckon upgrade the existing phys v.4 instance to v.5 first, then plan the expansion, plus we also consider going from phys to virtual when on v.5, have a fast storage now that supports the required I/O and capacity.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jul 2013 20:43:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Migrate-and-Upgrade-at-the-same-time-best-practices/m-p/78584#M1255</guid>
      <dc:creator>cgisplunk</dc:creator>
      <dc:date>2013-07-05T20:43:09Z</dc:date>
    </item>
    <item>
      <title>Re: Migrate and Upgrade at the same time - best practices?</title>
      <link>https://community.splunk.com/t5/Installation/Migrate-and-Upgrade-at-the-same-time-best-practices/m-p/78585#M1256</link>
      <description>&lt;P&gt;First of all it will not matter in some cases. I would consider below points.&lt;BR /&gt;
1) Existing implementation plan&lt;BR /&gt;
2) Whether all the functionality are still available as old versions (Depreciated functionality) &lt;BR /&gt;
3) Some forwarders doesn't work well even if it's newer version (tested on my own/check compatibility)&lt;BR /&gt;
4) Upgrading means splunk will migrate settings to newer version of installation (i.e. almost a single step)&lt;/P&gt;

&lt;P&gt;Hope you will figure out these things before you go for a full implementation&lt;/P&gt;</description>
      <pubDate>Fri, 05 Jul 2013 21:31:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/Migrate-and-Upgrade-at-the-same-time-best-practices/m-p/78585#M1256</guid>
      <dc:creator>linu1988</dc:creator>
      <dc:date>2013-07-05T21:31:59Z</dc:date>
    </item>
  </channel>
</rss>

