<?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>Question Re: High Availability installation in Technology Q&amp;A</title>
    <link>https://community.sap.com/t5/technology-q-a/high-availability-installation/qaa-p/9456357#M3367544</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;If your customer wants to go for this 2 phase approach no problem:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't recommend to convert an non HA system to an HA system.&lt;/P&gt;&lt;P&gt;As said in the comment above the best approach is to do a homogenous system copy. This is new instalation with HA mode and using the UAT system as source for the copy. &lt;/P&gt;&lt;P&gt;In ABAP only stacks systems (as SRM ?) this is as easy as installing a new system and copying the database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I do not recommend client copy for migrating production systems as more risks for errors and things missing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Before going live in HA mode you need to do some test (dry run) and check all works OK.&lt;/P&gt;&lt;P&gt;Best approach is separate boxes per system&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Luis&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 11 May 2013 14:12:11 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2013-05-11T14:12:11Z</dc:date>
    <item>
      <title>High Availability installation</title>
      <link>https://community.sap.com/t5/technology-q-a/high-availability-installation/qaq-p/9456354</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have the following server requirement for our customer and go live planned in phases&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SAP SRM,&lt;/P&gt;&lt;P&gt;SAP Netweaver Portal&lt;/P&gt;&lt;P&gt;SAP MDM&lt;/P&gt;&lt;P&gt;SAP PI&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In Phase 1, We are planning to go live with UAT System (considering UAT as PRD), becoz in phase 1 we are going live with limited functions and less number of users.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Later in Phase 2, we are planning to with the following options&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; a. Migrate all Phase1 data to PRD Server&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; b. Install PRD Server with HA Setup&lt;/P&gt;&lt;P&gt;&amp;nbsp; &lt;/P&gt;&lt;P&gt;My Questions&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; a. Will it possible to convert my UAT to PRD (distributed installation to HA)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; a. If (a) is not possible, What will be the best approach to migrate Phase 1 UAT data to PRD&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; b. In HA Setup Can I install SRM, MDM on same Server. Is this the best approach or do we need to go with separate box for each.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Ponnusamy&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Apr 2013 10:17:16 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/high-availability-installation/qaq-p/9456354</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-04-26T10:17:16Z</dc:date>
    </item>
    <item>
      <title>Re: High Availability installation</title>
      <link>https://community.sap.com/t5/technology-q-a/high-availability-installation/qaa-p/9456355#M3367542</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ponnusamy,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P style="font-size: 12px; background-color: #ffffff; color: #333333;"&gt;a. Will it possible to convert my UAT to PRD (distributed installation to HA)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P style="font-size: 12px; background-color: #ffffff; color: #333333;"&gt;&amp;nbsp; Technically YES it is possible. You may perform homogeneous system copy to achieve the same. &lt;/P&gt;&lt;P style="font-size: 12px; background-color: #ffffff; color: #333333;"&gt;&amp;nbsp; But the question here is UAT server will have lot of junk data which normally we may not be ok to put it into Production. Have a thought on this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P style="font-size: 12px; background-color: #ffffff; color: #333333;"&gt;a. If (a) is not possible, What will be the best approach to migrate Phase 1 UAT data to PRD&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P style="font-size: 12px; background-color: #ffffff; color: #333333;"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; IF you are 100% sure&amp;nbsp; there is no junk data in UAT client, you may perform client copy to production client to copy customizing , master data and transaction data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;PRE&gt;&lt;CODE&gt;&lt;P style="font-size: 12px; background-color: #ffffff; color: #333333;"&gt;b. In HA Setup Can I install SRM, MDM on same Server. Is this the best approach or do we need to go with separate box for each.&lt;/P&gt;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;It is advisable to keep production instances on separate box or separate virtualized partitions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Deepak Kori&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 27 Apr 2013 01:20:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/high-availability-installation/qaa-p/9456355#M3367542</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-04-27T01:20:48Z</dc:date>
    </item>
    <item>
      <title>Re: High Availability installation</title>
      <link>https://community.sap.com/t5/technology-q-a/high-availability-installation/qaa-p/9456356#M3367543</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Going live and installing the HA solution afterwards sounds like a bad idea to me (downtime, configuration errors). I would prefer the other way round and thoroughly test things before go live.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers Michael&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Apr 2013 07:02:14 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/high-availability-installation/qaa-p/9456356#M3367543</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-04-30T07:02:14Z</dc:date>
    </item>
    <item>
      <title>Re: High Availability installation</title>
      <link>https://community.sap.com/t5/technology-q-a/high-availability-installation/qaa-p/9456357#M3367544</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;If your customer wants to go for this 2 phase approach no problem:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't recommend to convert an non HA system to an HA system.&lt;/P&gt;&lt;P&gt;As said in the comment above the best approach is to do a homogenous system copy. This is new instalation with HA mode and using the UAT system as source for the copy. &lt;/P&gt;&lt;P&gt;In ABAP only stacks systems (as SRM ?) this is as easy as installing a new system and copying the database.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I do not recommend client copy for migrating production systems as more risks for errors and things missing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Before going live in HA mode you need to do some test (dry run) and check all works OK.&lt;/P&gt;&lt;P&gt;Best approach is separate boxes per system&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Luis&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 11 May 2013 14:12:11 GMT</pubDate>
      <guid>https://community.sap.com/t5/technology-q-a/high-availability-installation/qaa-p/9456357#M3367544</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2013-05-11T14:12:11Z</dc:date>
    </item>
  </channel>
</rss>

