Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata



SAP Cloud Platform: Data Management

Frequently Asked Questions
Version 2.0

 


Data Management   is a process by which data, is acquired, validated, stored, protected, and processed, and by which its accessibility, reliability, and timeliness is ensured to satisfy the needs of the users.  SAP Cloud Platform  provides various capabilities, like Data & Storage or Integration, to implement data management for applications on the cloud.

With the introduction of the Cloud Foundry environment in the SAP Cloud Platform, there is a major addition of services to the Data Management portfolio on the SAP Cloud Platform. This addition brings in, new capabilities like NoSQL, Message Brokers, and Object Storage to the SAP Cloud Platform.

This document aims to address the frequently asked questions (FAQs) about Data Management on the SAP Cloud Platform. The document is divided into two sections based on the two environments and we try to address the relevant questions in each section.

TABLE OF CONTENTS


 

1. OVERVIEW

 

Q: What are the different services currently available on the SAP Cloud Platform for Data & Storage?  

A: SAP Cloud Platform currently provides the following services for data & storage:

  •  SAP Cloud Platform SAP HANA service
  • SAP Cloud Platform Big Data Services
  • PostgreSQL on SAP Cloud Platform
  • MongoDB on SAP Cloud Platform
  • SAP Cloud Platform SAP ASE service
  • Object Store on SAP Cloud Platform
  • SAP Cloud Platform Document service
  • Redis on SAP Cloud Platform

 

Q: Are all these services available on both the Neo and the Cloud Foundry environments?  

A: SAP Cloud Platform currently offers the following options:

     On the Cloud Foundry environment:

  •   SAP Cloud Platform SAP HANA service
  •   PostgreSQL on SAP Cloud Platform
  •   MongoDB on SAP Cloud Platform
  •   Redis on SAP Cloud Platform
  •   Object Store on SAP Cloud Platform

 

    On the Neo environment:

  •   SAP Cloud Platform SAP HANA service
  •   SAP Cloud Platform SAP ASE service
  •   SAP Cloud Platform Document service

  

SAP Cloud Platform SAP HANA service is the only service that is available on both environments.

 

Q: How can I consume the SAP Cloud Platform Big Data Service?

A: The SAP Cloud Platform Big Data Service can be currently consumed as a standalone service. Further integration into the SAP Cloud Platform is on the roadmap.

 

Q: Are all the services available in every SAP Cloud Platform Datacenter?  

A: The Neo environment (and it services) is exclusively offered on SAP’s certified world-class tier-3 and 4 data centers; available in 7 locations (as of now) around the globe. For more details visit  http://www.sapdatacenter.com/  


The Cloud Foundry environment (and it services) is offered on third-party data centers -

  • Amazon AWS: Enterprise & Trial Accounts on EU: Frankfurt and US: Virginia
  • Microsoft Azure: Beta on US: California

The Services page on the Home screen of the SAP Cloud Platform cockpit, lists all the services and the regions where each service is available.


2 CLOUD FOUNDRY ENVIRONMENT

 

2.1 General

 

Q: What are the current versions of the external open source services, made available on the SAP Cloud Platform?

 

A: The current version of the external services are:

  •  PostgreSQL (v9.4),
  •   MongoDB (v3.0),
  •   Redis (v3.0),
  •   RabbitMQ (v3.6)

 

Q: The Cloud Foundry services on the SAP Cloud Platform, provide different plans based on Memory and Disk sizes. What are the ‚dev‘ plans used for?

A: The ‚dev‘ service plans on SAP Cloud Platform provide a sandbox for evaluation of the 4 open source services (PostgreSQL, MongoDB, Redis, RabbitMQ) and can be used for learning and development purposes. These plans should not be used for productive development. These plans can be currently availed free of cost but without any enterprise support and SLAs.

 

Q: Once I develop on the ‚dev‘ service plan, is there a possibility to migrate the service to the managed plans (small, medium, large, etc.)?

A: As these plans are meant for evaluation and learning purposes only, there is no upgrade path from a ‚dev‘ plan to any of the managed plans.

2.2 Data Ingestion

 

Q: Can I migrate data from my existing databases (PostgreSQL, MongoDB, ...) into the corresponding service on the Cloud Platform?

A: The platform currently does not support this migration.

2.3 Data & Storage

 

2.3.1 SAP Cloud Platform SAP HANA service

 

Q: Can I create a HANA MDC system in my Cloud Foundry trial account?

A: It is currently not possible to use an SAP HANA MDC system in a trial account. The trial account has a ‘ hanatrial ’ service in the Service Marketplace with the ‘ hdi-shared’ plan which can be used

 

Q: What is the version of HANA available on the Cloud Foundry environment of SAP Cloud Platform?

A: HANA Version 2.0 will be made available in the Cloud Foundry environment.

2.3.2 PostgreSQL on SAP Cloud Platform

 

Q: Are PostgreSQL extensions like PostGIS, HStore available on the SAP Cloud Platform?

A: Currently, we support ltree and pg_stat_statements Postgres extensions on the SAP Cloud Platform.

 

Q: Can we access PostgreSQL on SAP Cloud Platform using administrative tools like pgAdmin?

A: Connection of pgAdmin to PostgreSQL on SAP Cloud Platform is not currently not supported.


2.3.3 MongoDB on SAP Cloud Platform

 

Q: Does SAP Cloud Platform support OpsManager for MongoDB?

A: Currently, we do not support OpsManager or CloudManager on the platform.

 

Q: Can we setup sharding on MongoDB?

A: Support for setup of sharding with MongoDB on SAP Cloud Platform is in the roadmap.

2.3.4 Redis on SAP Cloud Platform

 

Q: What is the difference between the single-node and the normal service plans?

A: The normal service plans like Small, Medium, Large are available as highly-available 3 node clusters. But the single-node plans are not highly-available and any failure should be handled manually.

2.3.5 Object Store on SAP Cloud Platform 

 

Q: Can I reuse my existing S3 account to store objects?

A: No. The ObjectStore service will create a new bucket in our (SAP) AWS S3 account and provide the corresponding secure credentials to your application.

 

2.4 Integration

 

2.4.1 RabbitMQ on SAP Cloud Platform

 

Q: What protocols does the RabbitMQ on SAP Cloud Platform, currently support?

A: RabbitMQ on SAP Cloud Platform currently supports the Advanced Message Queuing Protocol (AMQP). Support for other standards like MQTT, STOMP, etc., is coming soon.

 

2.5 Data Operations 

 

Q: Is backup available for all Data & Storage Cloud Foundry services on SAP Cloud Platform?

A: Backup and restore is currently available for PostgreSQL, MongoDB and HANA services on the SAP Cloud Platform

 

Q: Is the backup of the database available as self-service?  

A: Not currently. Backup & Restore activities are handled by the SAP Ops teams. User controlled backups are planned to be supported in the future.

 

Q: Can I see the list of backups available for my service instance?  

You can see the list of backups for each service instance via the CF CLI and the SAP Cloud Platform Cockpit. Example: On the cockpit, go to the respective service (PostgreSQL) -> Backups (in the left navigation pane). The backups will be listed by service instance.

 

Q: How often does a backup occur?  

A: For managed plans of PostgreSQL and MongoDB, a full data backup is done once a day. In addition, PostgreSQL on SAP Cloud Platform, also implements incremental backups every 2 hrs. For MongoDB, incremental backups are coming soon.

The backups are preserved for a period of 14 days, after which they will be deleted.

 

Q: Can I increase the backup availability to > 14 days?

A: No. Currently, this option is not configurable.

 

Q: Is backup available for the ‚dev‘ service plans?

A: Backup and restore is only available for the managed service plans like xsmall, small, etc.

 

Q: Can I check if the daily backup was successful or not?  

A:  The status of any given backup can be checked via the CF CLI and the SAP Cloud Platform cockpit.

Example: On the cockpit, go to respective service (PostgreSQL) -> Backups (in the left navigation pane). The backup status (per instance) will be indicated in the column ‚Last Operation‘.

 

Q: How can I restore my database on SAP Cloud Platform?  

A:  Data restore can be triggered via the CF CLI and the SAP Cloud Platform cockpit.

Example: On the cockpit, go to respective service (PostgreSQL) -> Backups (in the left navigation pane). Restore can be triggered via the ‚Actions‘ column -> Restore for any particular backup of the selected service instance.

 

Q: Do I have an option of upgrading the open-source services to the latest market available version, for e.g. upgrade MongoDB to v3.4 or v3.6?

A: Version upgrades triggered by users, for both major (x.x to x.y) and minor (x.x.x to x.x.y) versions are currently not supported on the SAP Cloud Platform.

 

Q: How can I monitor my data & storage services on SAP Cloud Platform?  

A: Monitoring of created service instances is coming soon to the SAP Cloud Platform.

2.6 Data Consumption

Q: Can I consume the Cloud Foundry services as standalone databases; Example: using a database client?

A: The instances of CF services created on SAP Cloud Platform will only be available for use by binding them to applications on the platform.

 


3 NEO ENVIRONMENT

 

3.1 General

 

Q: I have purchased a SAP Cloud Platform package. Which database will be available for me to use?  

A:  Depending on the package you purchase, it may or may not contain database storage. Please refer to the list of packages on  Pricing and Packaging | SAP Cloud Platform  for more details. If it is mentioned that SAP ASE or SAP HANA is included in the package, then you should see the corresponding database attached to your SAP Cloud Platform account.

 

Q:I have purchased a SAP Cloud Platform package which includes database storage. Where can I view, if the storage has been provisioned correctly?  

A:  Login to the SAP Cloud Platform cockpit using the URL: https://account.<landscape host>/cockpit , example  https://account.hana.ondemand.com/cockpit  (for EU) using your credentials (email/password) and get into your SAP Cloud Platform account. Once in your account, navigate to Persistence -> Database Systems. You should find the database provisioned for you.

 

Q: I have purchased a 1TB HANA database storage with the SAP Cloud Platform. Can I access this database from any of my SAP Cloud Platform sub-accounts?  

A: You will be able to share your ASE and HANA databases with other accounts in the Neo environment. For more details check out the link:  Sharing Databases with Accounts  

3.2 Data Ingestion

 

Q: How do I transfer large amounts of data from on premise to cloud?  

A: Data load and replication is supported from on premise databases to HANA databases on the Neo environment, using either on premise replication tools like SLT (SAP Landscape Transformation) in combination with the service channels on SAP Cloud Connector or cloud based replication tools like SDI (Smart Data Integration) using the on-premise DP (data provisioning) agents.

3.3 Data & Storage

 

3.3.1 SAP Cloud Platform SAP HANA service

 

Q: What are the different flavors of HANA database available on SAP Cloud Platform?  

A: The following 3 flavors of HANA persistence is available currently to SAP Cloud Platform users:

  •   HANA Shared  
  •   Dedicated HANA database or HANA XS  
  •   HANA MDC  


Q: What are the differences between the 3 flavors of HANA and for what can I use each of them?

A: HANA Shared - Provides the user with a possibility to consume a shared HANA database. You can create a schema in the shared HANA instance and bind the schema to a Java App on SAP Cloud Platform. You will not be able to connect to this instance via SAP HANA Studio/Web IDE or SAP HANA cockpit and build HANA or XS native applications. You only have ownership of the schema you create. This flavor will only be available on the Trial landscape.

HANA XS  – Provides the user with a possibility to consume a dedicated HANA database. You have more control of the database and it can be used to build HANA/XS applications or bind databases to Java Apps on SAP Cloud Platform. This flavor  will only be available for Enterprise/Productive accounts.

HANA MDC  – Provides the user with a possibility to consume a dedicated tenant of HANA. You will have full ownership of the tenant each tenant database is fully isolated with its own database users, catalog, repository, data/log files and database services. It can be used to build HANA/XS applications or bind the tenant to Java Apps on SAP Cloud Platform.

3.3.2 SAP Cloud Platform SAP ASE service

 

Q: Can I connect a database /SQL tool to my ASE database on SAP Cloud Platform?

A: Yes. You need to open a database tunnel via the Neo environment SDK, to the SAP Cloud Platform account which contains the database.

3.3.3 SAP Cloud Platform Document service

 

Q: Can I connect tools like CMIS workbench with the SAP Cloud Platform Document Service?

A: Yes. Document Service supports consumption of CMIS-enabled document repositories using Apache Chemistry/OpenCMIS libraries.

3.4 Data Operations

 

Q: Is the backup of the database available as Self-Service?

A: No. Backup + Restore activities are handled by the SAP Ops teams. Customers can trigger a restore by raising a Service Request

 

Q: How often does a backup occur? How much data can I lose in the worst case?  

A: For productive HANA and ASE databases on the Neo environment, a full data backup is done once a day. Log backup is triggered at least every 30 minutes. The corresponding data or log backups are replicated to a secondary location every two hours. Backups are kept (complete data and log) on a primary location for the last two backups and on a secondary location for the last 14 days. Backups are deleted afterwards. Recovery is therefore only possible within a time frame of 14 days. Restoring the system from files on a secondary location might take some time depending on the availability.

SAP offers to back up and recover shared and dedicated database systems only as a whole.

For SAP ASE and SAP HANA databases with multitenant database container (MDC) support, you can operate several databases in the same database system and recover them individually. Thus, when binding applications to databases, you can achieve a fine grained control of the backup and recovery.

 

Q: Can I check if the daily backup was successful or not?  

A: Currently this can only be checked from the SAP HANA Studio (for HANA),

 

Q: How can I restore my database on SAP Cloud Platform?  

A: To restore your HANA/ASE database on SAP Cloud Platform, you currently need to raise an SAP Cloud Platform Service Request (via the SAP Cloud Platform cockpit) to the Persistence team with the account, database details and the point-in-time to which the restore is needed.

 

Q: Once a request for restore is raised, how fast will the restore be made available?  

A: The point-in-time restore depends on the size of the backup. The restore process can take between a few minutes and a few hours.

 

Q: Does my database support failover on SAP Cloud Platform?  

A: There is no support for failovers (automatic or manual) for databases in SAP Cloud Platform.

 

Q: How can I update my database on SAP Cloud Platform?  

A: Revision updates on HANA databases are available as self-service using the SAP Cloud Platform Cockpit. A downtime of 15-20 minutes is expected during this update process.

 

Q: In case a Revision Update fails or has unwanted effects, can I revert to an older revision?  

A: No. Downgrading a database to an older revision, is currently not a possibility.

 

Q: Is the HANA content on SAP Cloud Platform encrypted?  

A: Yes. The Data, Log and Backup are hardware encrypted. Additionally the data is also software encrypted. The keys used for encryption are stored in and belong to SAP.

 

Q: How can I restart SAP HANA Database Systems?  

A: If your databases are not working properly, you can try to solve the issues by restarting the corresponding SAP HANA database system. The restart is done for the whole database system.

You can restart a database system in the following ways:

To restart an SAP HANA database system from the SAP Cloud Platform cockpit , proceed as follows:

Log on to the cockpit and select an account for which SAP HANA database systems are available.

Choose Persistence -> Database Systems in the navigation area.

To select the entry for the relevant database system in the list, click the link on its name.

In the overview of the database system, choose Restart.

During the restart, you can monitor the system status using the HANA tools. Connected applications and database users cannot access the system until it is restarted. The restart for the database system is complete when HANA tools like SAP HANA cockpit are available again.

To restart an SAP HANA database system from the console client , use the  restart-hana  command.

To restart a single tenant database instead of the whole database system, use the  stop-db-hana  and  start-db-hana  commands or the SAP Cloud Platform cockpit.

 

Q: Can I change the connection pool size to my database on SAP Cloud Platform?  

A: You can now configure the connection pool size of dedicated SAP HANA and SAP ASE database systems.

 

Q: How can I monitor my database on SAP Cloud Platform?  

A: Monitoring of databases is possible at the database system level using the SAP Cloud Platform cockpit. Choose Persistence -> Database Systems in the navigation menu. To select the entry for the relevant database system in the list, click the link on its name. Click on Monitoring in the navigation side bar to view the statistics of your database system.

3.5 Data Consumption

 

Q: In my Java application, I am using JPA with EclipseLink and have denoted a property of type String with @Lob. Why is a VARCHAR column of limited length created in the database?  

A: Due to the EclipsLink  bug 317597 , the @Lob annotation is ignored when the corresponding table column is created in the database. To enforce the creation of a CLOB column, you have to additionally specify @Column(length=4001) for the property concerned. In fact, any value may be chosen as long as it is at least 4001 for SAP MaxDB or 2001 for the SAP HANA database.

 

Q: I tested my SAP Cloud Platform app locally with the Apache Derby database, so why do I run into SQL exceptions when deploying it in the cloud?  

A: Different database systems use different system tables and reserved words. As an application developer, make sure that the application does not use any of these reserved words for its own table and column names.

JPA does also not shield the application from this. If, for example, your entity class contains an attribute named "date", this will clash with the reserved word DATE on SAP MaxDB and cause schema creation to fail upon deployment. In such a case, the attribute should either be renamed to something else, or be mapped to another column name in the database. This can be done using the @Column annotation like this:

@Column(name="THEDATE")

        private String date;
      

Tips:

·        Check the root cause in the application log. (A link to the log is provided in the application overview in the SAP Cloud Platform cockpit. For more information, see  Using Logs in the Cockpit .)

 

·        For a complete list of reserved words, refer to the relevant database documentation ( SAP MaxDB SQL Reference Manual Apache Derby Documentation ).

5 Comments

  1. Hi Manjunath,

    In blog above you have indicated the restoration time for backup as 1 day, Does this apply to production environments as well? 

    In case of upgrade failures how to we revert the system back to earlier versioni, As you indicated its not possible to restore to previous environment.

    PS:- we have got license for HCP base edition for HANA side car scenario.

    1. Hello Ravi,

      Yes, this is applicable to product environments. The process is outlined below:

      https://help.sap.com/viewer/65de2977205c403bbc107264b8eccf4b/Cloud/en-US/f4ad65ddc06444a3a3641b2da2767a96.html

      Version downgrades are not supported.

      Regards,

      Manju

  2. Hello Manju,

    Thank you for response. When you say version downgrades are not supported, if upgrade fails  or it causes business critical issues we should raise request for restoration of DB ?

    Also DB upgrades for revision versions are self service and version upgrades for example HANA SP12 to HANA 2.0 we should raise request for upgrade?

    1. Hello Ravi,

      In such cases, please open a ticket on the Persistence component. Process is detailed by the link I shared earlier.

      Version upgrades are self service, as long as the version to be upgraded to, is available on the SAP Cloud Platform. HANA 2.0 is not available on SAP CP yet.

      Regards,

      Manju

  3. Hello  Manjunath, can you add some detail on data operations for the document repository?  

    In our scenario, data is managed in the HANA DB with some linked documents in the repository.

    I would like to know the process and options for data recovery of this and a concept for checking / repairing consistency between the two.

    regards

    Steve G