webinar is for the ones who want to stay away from the highly available
clustering software for SAP. If you are at ease with HA software and
webinar is for the ones who want to stay away from the highly available
clustering software for SAP. If you are at ease with HA software and would like
to continue using them, this webinar might not be for you. But if you
think, a little knowledge about an alternate solution wouldn't hurt, please
do we need to talk about it?
our experience so far, the top reasons why customers wish to stay away from
clustering software are:
up a High Availability Cluster is a complicated process
of a High Availability cluster requires specialized skillset.
· Standard operating procedures
alone do not help during the critical situations. The availability of someone
with High Availability cluster knowledge is essential when there is a failure.
failover that is useful in real time failure situations, often poses
to false-alarms that are triggered creating complex situations to handle. Many customers switch off automatic failover and
rely on manual procedures
costs involved in puchase and maintenance of high availabilty software, and in acquiring
you just say, "Our SAP systems are hosted on public cloud, do we still
need to worry about HA software?"
at BCS, we have been brainstorming about a solution which can help customers
stay away from clustering software, yet achieve the availaility % that they are
looking for. As a result, we have come up with an approach using cloud native
functions that can be leveraged to ensure high availability for SAP
applications. If you are interested to know about the solution, please register
yourself for the webinar using this link.
Myths have an immense level of impact on the decisions that are made at an or
Top 5 Myths in Hosting SAP on the Public Cloud
Myths have an immense level of impact on the decisions that are made at an organization level. I have heard many IT executives comment that SAP systems can not be moved into the Public Cloud. This common fear or concern over moving to the public cloud are often based on myths or hearsay. It becomes highly difficult to convince customers that the public cloud is the right choice for them. This blog addresses myths that either stop or discourage customers from moving their SAP systems into the public cloud. The focus is on the most important and most dangerous myths that are impacting the decision process around SAP on the Public Cloud topic within organizations.
#1 – Public Cloud is not as secure as On-Premise / Private Cloud
As per Gartner, through 2020, 95% of cloud security failures will be the customer’s fault. In any cloud, be it private or public, security is not the sole responsibility of the datacenter provider, it is a joint responsibility of the cloud service provider and the customer. For SAP on the public cloud, this is much more relevant as SAP systems can only leverage Infrastructure as a Service model while hosted on the public cloud. Therefore, only the physical infrastructure security would be the sole responsibility of the cloud service provider such as Azure, AWS or GCP. Anything over and above the infrastructure, for example, Virtual Machine Security, Virus Scan, Vulnerability Scan, Log Monitoring, Operating System Patches, Database Security, SAP Security are the responsibility of the customer. We can debunk this myth by implementing robust security controls over all the layers of the SAP application. This is the most important reason why one should focus on the fundamental architecture based on which the SAP systems will be built. Designing and implementing the cloud foundation in a secured manner will debunk myth #1.
#2 – SAP applications are not suitable for Public Cloud
This myth is very specific to SAP applications. Typically we hear this kind of statement from the customers who do not have in-house SAP Architecture knowledge and are dependent on a third party provider for SAP Basis and datacenter management. As we all know, SAP is moving into an SAP HANA Enterprise Cloud (HEC) on Azure / AWS service model. SAP moving in this direction is an important proof point that the public cloud is taking a prime position for SAP workloads. Additional reasons why SAP is suitable for the Public Cloud are as follows:
Architecture – SAP is far from new in the market. SAP’s architecture is known for over 30 years, the fundamental architecture has not gone through drastic changes since the day it was released. Any deployment architecture that you have for on-premise is 100% suitable to the public cloud as well. In fact, it is much more flexible and scalable in the public cloud environment.
Migration Techniques – System Copies and OS/DB Migrations are very common in the SAP world. There are robust tools and techniques available to migrate SAP systems from one hardware to the other, one datacenter to the other, on-premise to the public cloud. These tools are not new in the market; they have been available in the marketplace for over two decades and provide reliable results.
Support Statement – SAP works with public cloud service providers to certify their products, and there is a clear support statement from SAP with public cloud service providers.
Support Levels – You can customize your support level requirements to any level to meet your business requirements. For example, if are you looking for 99.99% availability, it is possible to meet the requirement with AWS and Azure Availability Zones.
Security & Compliance Requirements – Public cloud service providers are investing billions of USD in Security & Compliance related setup. They now have the necessary certifications (specific to industry, region, country) to be able to meet most of the customer’s legal, security & compliance requirements.
3) Performance will be impacted
This is not true only for SAP, this is valid for any similar applications. As indicated above, fundamental architecture and strong cloud foundation will help you to overcome the myth. The only factor that is out of the Public Cloud Service provider’s control and can influence the performance is the network, everything else can be adjusted according to the performance requirement. For example, if the CPU/Memory is not performing enough, you have the ability to switch to a large machine type. Similarly for large IOPS requirements, you have the ability to provision the appropriate storage to meet your IOPS requirement. However, when it comes to network, if you are in South Africa where none of the leading cloud service providers have their datacenter infrastructure, most likely you would be asked to host your applications either in Europe or India. This is certainly going to have an impact on the latency between your users and cloud infrastructure. On the other hand, if you are in Amsterdam and hosting your application in one of the Europe based datacenter, then you are not going to see any difference between your on-premise infrastructure vs. cloud infrastructure. The performance of your SAP systems will be much better than your on-premise datacenter as you have the flexibility to adjust the number of CPUs, number of application servers, storage, etc., based on your performance requirement.
# 4 – Moving SAP into the Cloud can bring all the cloud characteristics
Many customers also think that if they move their SAP systems to the public cloud, by default they will be able to get cost optimized, scalable, flexible and automated infrastructure. Unfortunately, this is not true. Cloud native automation techniques do not provide an orchestration / cloud management platform for SAP, this needs to be either built by customers themselves or via products like Symphony for SAP Netweaver (S4S). Without the implementation of tools like Symphony for SAP Netweaver (S4S) one cannot truly gain the advantages of cloud computing while hosting SAP systems on the public cloud.
#5 – Service Cost is going to be very high although we get pay-per use infrastructure
Service cost should decrease as most of the system integrators have pay-per-use pricing for the services. For example, at BCS, we have a pricing model called “T-shirt pricing for SAP”. This model allows for our customers to take advantage of pay-per-use service model for SAP BASIS and underlying administration tasks. Depending upon the customer size, system service requirements and Service Level Agreements, we provide Small, Medium, Large and Extra Large pricing for our customers. We have the ability to change the service level in real time. An example would be if the support requirement is lower for a particular environment for a specific period, then the customer can request a reduction in service level (e.g. “we do not need support for this particular development and sandbox systems for this month”). This would immediately reduce their support costs. This is unique to BCS. In BCS's service model we are dedicated to provide you the correct level of service at the right time for the right SAP instances. Your cost is based on the number of Virtual machines and the Service Level at which they are requested.
There will be additional caveats and concerns over moving your SAP environments to the Public Cloud. BCS would be honored to be your partner to continue to dissolve your concerns and assist in understanding the great benefits. BCS is positioned to become the specialized leader in SAP BASIS, SAP Cloud Transformation and SAP Cloud management and automation. We can work with you every step of your public cloud journey to make you successful in migrating your SAP applications into the Public Cloud. Once you are in the cloud we can provide you with the most advanced toolset on the market for managing and maintaining your cloud based SAP systems. Please reach out to the team at firstname.lastname@example.org if you need any additional information on this topic and to learn more about our recently SAP recognized cloud management platform, Symphony for SAP Netweaver (S4S). Our SAP specialists in SAP Cloud Transformation will be able to help you to devlop myth-busted solutions that are best for you and your company.