<?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 SAP  Instance on AWS - Down sizing steps in DevOps and System Administration Forum</title>
    <link>https://community.sap.com/t5/devops-and-system-administration-forum/sap-instance-on-aws-down-sizing-steps/m-p/12491199#M1745</link>
    <description>&lt;P&gt;Hello All,&lt;/P&gt;
  &lt;P&gt;We are using EHP8 ECC6.0 &amp;amp; S4HANA 1709 in AWS . We have many demo systems where the size of those instance are R4.Xlarge with 4 VCPU`s and 30.5GB RAM. As part of cost consciousness we want this to be migrated to smaller instance R4.large where it will have only 2 VCPU`s and 16GB RAM. I am trying to find out step by step approach for this and i am not getting enough documentation . Can any one help me on this?&lt;/P&gt;
  &lt;P&gt;We are using SAP ASE16 as ur DB and Linux as our OS. Even for S4HANA we need the same kind of steps.&lt;/P&gt;
  &lt;P&gt;Thanks,&lt;/P&gt;
  &lt;P&gt;Veera&lt;/P&gt;</description>
    <pubDate>Wed, 23 Mar 2022 08:36:43 GMT</pubDate>
    <dc:creator>veeras81</dc:creator>
    <dc:date>2022-03-23T08:36:43Z</dc:date>
    <item>
      <title>SAP  Instance on AWS - Down sizing steps</title>
      <link>https://community.sap.com/t5/devops-and-system-administration-forum/sap-instance-on-aws-down-sizing-steps/m-p/12491199#M1745</link>
      <description>&lt;P&gt;Hello All,&lt;/P&gt;
  &lt;P&gt;We are using EHP8 ECC6.0 &amp;amp; S4HANA 1709 in AWS . We have many demo systems where the size of those instance are R4.Xlarge with 4 VCPU`s and 30.5GB RAM. As part of cost consciousness we want this to be migrated to smaller instance R4.large where it will have only 2 VCPU`s and 16GB RAM. I am trying to find out step by step approach for this and i am not getting enough documentation . Can any one help me on this?&lt;/P&gt;
  &lt;P&gt;We are using SAP ASE16 as ur DB and Linux as our OS. Even for S4HANA we need the same kind of steps.&lt;/P&gt;
  &lt;P&gt;Thanks,&lt;/P&gt;
  &lt;P&gt;Veera&lt;/P&gt;</description>
      <pubDate>Wed, 23 Mar 2022 08:36:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/devops-and-system-administration-forum/sap-instance-on-aws-down-sizing-steps/m-p/12491199#M1745</guid>
      <dc:creator>veeras81</dc:creator>
      <dc:date>2022-03-23T08:36:43Z</dc:date>
    </item>
    <item>
      <title>Re: SAP  Instance on AWS - Down sizing steps</title>
      <link>https://community.sap.com/t5/devops-and-system-administration-forum/sap-instance-on-aws-down-sizing-steps/m-p/12491200#M1746</link>
      <description>&lt;P&gt;Hi Veera&lt;/P&gt;&lt;P&gt;r4 is an old family these days, as soon as you migrate to a new instance type, it will be possible to change the virtualization type, the hypervisor is different in new families&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Take an AMI, and suspend auto scaling if you have it enabled.&lt;/LI&gt;&lt;LI&gt;Stop the instance choose Actions &amp;gt; Instance Settings &amp;gt; Change Instance Type&lt;/LI&gt;&lt;LI&gt;Beware if you use a public IP address, this will change, but private address will remain&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;new r5 instances are based on the Nitro and require EBS-backed AMIs with the Elastic Network Adapter (ENA) drivers installed. So you must install the ENA drivers&lt;/P&gt;&lt;P&gt;Also, on Nitro, EBS volumes are exposed as NVMe block devices so you must first install the NVMe drivers on your instance. Also, to mount file systems at boot time using /etc/fstab, you must use UUID/Label instead of device names on Nitro.&lt;/P&gt;</description>
      <pubDate>Fri, 25 Mar 2022 13:21:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/devops-and-system-administration-forum/sap-instance-on-aws-down-sizing-steps/m-p/12491200#M1746</guid>
      <dc:creator>MarioDeFelipe</dc:creator>
      <dc:date>2022-03-25T13:21:53Z</dc:date>
    </item>
  </channel>
</rss>

