<?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: Dynatrace Migration to Different Hardware Configuration in Dynatrace Managed Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-migration-to-a-different-hardware-configuration/m-p/121884#M1583</link>
    <description>&lt;P&gt;That &lt;EM&gt;must &lt;/EM&gt;is for supported production operation, not a strict technical restriction. &lt;/P&gt;&lt;P&gt;For a short term you will be fine if the new machines have at least the same size / are bigger and you have the same number or more nodes in the new cluster. &lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;So for you migration use case with the replication method you will be fine.&lt;/P&gt;</description>
    <pubDate>Wed, 17 Feb 2021 13:28:06 GMT</pubDate>
    <dc:creator>pahofmann</dc:creator>
    <dc:date>2021-02-17T13:28:06Z</dc:date>
    <item>
      <title>Dynatrace migration to a different hardware configuration</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-migration-to-a-different-hardware-configuration/m-p/121882#M1581</link>
      <description>&lt;P&gt;We're planning to move our POC cluster to a new Producton cluster .&lt;/P&gt;
&lt;P&gt;2 POC nodes are installed on a virtualized environment and the new production nodes will be 4 physical machines with better CPU/RAM/Storage configuration.&lt;/P&gt;
&lt;P&gt;According to the Dynatrace documentation (&lt;A href="https://docs.dynatrace.com/managed/shortlink/managed-add-node" target="_blank" rel="noopener noreferrer"&gt;1&lt;/A&gt;, &lt;A href="https://docs.dynatrace.com/managed/shortlink/managed-cluster-migration" target="_blank" rel="noopener noreferrer"&gt;2&lt;/A&gt;, &lt;A href="https://docs.dynatrace.com/managed/shortlink/managed-cluster-restore" target="_blank" rel="noopener noreferrer"&gt;3&lt;/A&gt;) new nodes "must" be in identical configuration as the old ones, so if we go with the data replication method by adding new cluster nodes, we will have incompatibilities.&lt;/P&gt;
&lt;P&gt;How do you think we should proceed?&lt;/P&gt;</description>
      <pubDate>Mon, 17 Mar 2025 14:21:30 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-migration-to-a-different-hardware-configuration/m-p/121882#M1581</guid>
      <dc:creator>serhat_balik</dc:creator>
      <dc:date>2025-03-17T14:21:30Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace Migration to Different Hardware Configuration</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-migration-to-a-different-hardware-configuration/m-p/121883#M1582</link>
      <description>&lt;P&gt;Yes, all nodes should be equal to ensure nodes are equally balanced. In case of upgrade or failures, other nodes can equally handle the load. &lt;/P&gt;&lt;P&gt;In case this is a temporary solution for the migration time, it's fine they are not the same (with the side-effect I mentioned). &lt;/P&gt;&lt;P&gt;Good luck with migration!&lt;/P&gt;</description>
      <pubDate>Wed, 17 Feb 2021 13:26:57 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-migration-to-a-different-hardware-configuration/m-p/121883#M1582</guid>
      <dc:creator>Radoslaw_Szulgo</dc:creator>
      <dc:date>2021-02-17T13:26:57Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace Migration to Different Hardware Configuration</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-migration-to-a-different-hardware-configuration/m-p/121884#M1583</link>
      <description>&lt;P&gt;That &lt;EM&gt;must &lt;/EM&gt;is for supported production operation, not a strict technical restriction. &lt;/P&gt;&lt;P&gt;For a short term you will be fine if the new machines have at least the same size / are bigger and you have the same number or more nodes in the new cluster. &lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;So for you migration use case with the replication method you will be fine.&lt;/P&gt;</description>
      <pubDate>Wed, 17 Feb 2021 13:28:06 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-migration-to-a-different-hardware-configuration/m-p/121884#M1583</guid>
      <dc:creator>pahofmann</dc:creator>
      <dc:date>2021-02-17T13:28:06Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace Migration to Different Hardware Configuration</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-migration-to-a-different-hardware-configuration/m-p/121885#M1584</link>
      <description>&lt;P&gt;Hello &lt;A rel="user" href="https://answers.dynatrace.com/users/41751/view.html" nodeid="41751"&gt;@MUSTAFA SERHAT B.&lt;/A&gt;&lt;/P&gt;&lt;P&gt;In my opinion, the cluster backup and restore procedures should be suitable in your situation.&lt;/P&gt;&lt;P&gt;Secondly, you are also going to provide better hardware and more nodes. According to the below-documented information.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;EM&gt;Make sure the target nodes meet the hardware requirements.&lt;/EM&gt;&lt;/LI&gt;&lt;LI&gt;&lt;EM&gt;For a typical scenario, it's assumed that the number of target nodes is equal to or higher than the number of source nodes.&lt;/EM&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Babar&lt;/P&gt;</description>
      <pubDate>Wed, 17 Feb 2021 13:34:31 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-migration-to-a-different-hardware-configuration/m-p/121885#M1584</guid>
      <dc:creator>Babar_Qayyum</dc:creator>
      <dc:date>2021-02-17T13:34:31Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace Migration to Different Hardware Configuration</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-migration-to-a-different-hardware-configuration/m-p/121886#M1585</link>
      <description>&lt;P&gt;It depends on how important the transaction detail data is. With the Backup method you lose the transaction detail data for the last 10 days as it is not backed up. &lt;/P&gt;&lt;P&gt;If that is ok you can use the backup, if not stick with the replication method where the data will still be available on the old nodes till phased out.&lt;/P&gt;</description>
      <pubDate>Wed, 17 Feb 2021 14:50:13 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-migration-to-a-different-hardware-configuration/m-p/121886#M1585</guid>
      <dc:creator>pahofmann</dc:creator>
      <dc:date>2021-02-17T14:50:13Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace Migration to Different Hardware Configuration</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-migration-to-a-different-hardware-configuration/m-p/121887#M1586</link>
      <description>&lt;P&gt;Thank you guys for all the suggestions. The idea of starting from scratch and reconfiguring all the months of work was making me nervous.&lt;/P&gt;</description>
      <pubDate>Sun, 21 Feb 2021 13:28:32 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-migration-to-a-different-hardware-configuration/m-p/121887#M1586</guid>
      <dc:creator>serhat_balik</dc:creator>
      <dc:date>2021-02-21T13:28:32Z</dc:date>
    </item>
  </channel>
</rss>

