Unveiling the Power of SAP HANA Cloud Migration: Self Service Migration Tool

So, you're the admin, and you're ready to roll with an SAP HANA Cloud database instance. Great call! Let's map out the essentials to make sure you're all set.

Getting Subaccount Access Right

First things first – to deploy the database, you'll need access to a subaccount in your company's SAP Business Technology Platform (SAP BTP) global account. But, not just any access – you'll want the Subaccount Administrator role collection. If you find your user account missing this role, no worries. Just give a shout to your SAP BTP global account admin and ask them to hook you up. It's like getting the backstage pass for the deployment concert.

Unlocking the Toolbox: SAP HANA Cloud Administration Tools

Now, let's talk tools. To craft and manage your database instances, you're going to need the SAP HANA Cloud - tools plan in your subaccount. This magical plan opens the door to a trio of game-changers: SAP HANA Cloud Central, SAP HANA cockpit, and SAP HANA database explorer

To activate the new multi-environment SAP HANA Cloud tools, follow the instructions in the blog

Benefits and features of the multi-environment SAP HANA Cloud tools

The Old VS The NEW

HANA Cloud tools in Cloud Foundry are still hanging around, but here's the scoop – the Cloud Foundry edition of SAP HANA Cloud Central is waving goodbye. It's officially on the way out. SAP's advice? Make the shift to the new multi-environment SAP HANA Cloud tools. That's where the buzz is, and that's where the future is headed.

Implementation Starts here

In SAP BTP Cockpit, navigate to SAP HANA Cloud Central via: Instances and Subscription > Applications > SAP HANA Cloud > Instances for creating and managing database instances

To access the Self-Service Migration for SAP HANA Cloud tool in SAP HANA Cloud Central, no additional configuration is needed for SAP HANA Service scenarios (Neo and Cloud Foundry).

However, for SAP HANA on-premises scenarios, ensure the connectivity_proxy service plan is added to the connectivity service. If not available, contact the SAP BTP global account administrator to add this required service plan for self-service migration as this needs to be connected via cloud connector

To locate the Self-Service Migration Tool in SAP BTP Cockpit:

In the subaccount navigation, select Instances and Subscription.

From the Applications table, choose SAP HANA Cloud.

In the navigation area, click on Migrations to create and manage migrations to SAP HANA Cloud.

Deploy a SAP HANA Cloud Database

Now Step by Step method to provision a database is mentioned here

SAP HANA DB SIZE

MEMORY AND STORAGE SIZE SUPPORTED BY HANA

Creating a Migration user in source database

Migrating from an SAP HANA database to SAP HANA Cloud requires a dedicated user in your SAP HANA source database. The Self-Service Migration tool will check whether the provided user has all needed privileges to perform the migration. Any missing privileges and the objects on which they must be granted will be displayed in the user interface.
On the source database, open a SQL Console in the Database Explorer.
Create a migration user by executing the following statement in the Database Explorer -
1 CREATE USER <username> PASSWORD <password> NO FORCE_FIRST_PASSWORD_CHANGE;
2. Grant the necessary privileges to the migration user by running the following script in the Database Explorer
GRANT SELECT ON _SYS_REPO.DELIVERY_UNITS TO <username>;
GRANT SELECT ON _SYS_REPO.ACTIVE_OBJECT TO <username>;
GRANT CATALOG READ TO <username>;
GRANT INIFILE ADMIN TO <username>;
GRANT TRUST ADMIN TO <username>;
GRANT CERTIFICATE ADMIN TO <username>;
GRANT CREATE REMOTE SOURCE TO <username>;

3. For each schema you need to migrate add this scenario :

GRANT SELECT ON SCHEMA "<SCHEMA_NAME>" TO <username>;

The SQL statement must be executed by the owner of the schema or any user who has the permissions to grant the required privileges.

Install and Configure the Cloud Connector

The Cloud Connector allows you to set up a secure connection between the source SAP HANA on-premise database and the target SAP HANA Cloud database instance on SAP BTP

Installation of Cloud Connector on Linux

Connect to an SAP HANA Platform On-Premise Database

Migrating from SAP HANA On - prem

Note : For this you need require the connectivity_proxy service plan to be added to the connectivity service in your subaccount entitlements.

Fill the details in Self Migration Tools :-

Name	Description	Example
Migration Name	Give a short descriptive migration project name.	Migration OP to HC
Migration Description	Give a good description for the migration project.	Self-Service Migration SAP HANA on-premises to SAP HANA Cloud
Source Instance Host	Virtual host name exposed to SAP BTP through Cloud Connector.	op-source-hana. The real host name wdflbmt7346 isn't exposed to the SAP BTP.
Source Instance Port	Virtual port number exposed to SAP BTP through Cloud Connector.	42015. The real port number 30015 isn't exposed to the SAP BTP.
Cloud Connector Location ID	Location ID defined in the Cloud Connector.	SCC-OP-HANA
Migration Username	Dedicated migration user account created on the source database.	MIGUSER
Migration Username Password	Password specified during the creation of the migration user.	Welcome1 ( This is not a strong password )
Target Database Username	Database administrator user name created during SAP HANA Cloud database deployment.	DBADMIN
Target Username Password	Password specified during the deployment of the SAP HANA Cloud database.	Welcome1 ( This is not a strong password )

Demo link

Migrating from SAP HANA Service for BTP , Neo environment

Note : This scenario only migrates the catalog and data to SAP HANA Cloud. Migration of XS Classic and SAP HANA repository content or other design-time artifacts is not supported.

Field	Description	Example
Migration Name	Descriptive name for the migration project.	Neo to HC Self-Service Migration
SAP BTP Region	Region of the source database within SAP BTP.	Europe (Frankfurt)
Technical Subaccount	Name of the technical subaccount in the Neo environment.	pvwaf4nsum
Source Database ID	DB/Schema ID listed in the Databases & Schemas list.	neosource
Account Username	User name for connecting to the SAP BTP Neo environment.	P1234567890
Account Password	Password for the specified user account (P1234567890).	Welcome1
Database Username	Dedicated migration user account on the source database.	MIGUSER
Database Password	Password specified during the creation of the migration user.	Welcome1
Target Instance	Name of the SAP HANA Cloud target database.	HC_Neo_Target

Demo Link

Migrating from SAP BTP Cloud Foundry

Note : For this scenario , the source and target database need to be located in the same region.

Name	Description	We will use Example
Migration Name	Descriptive name for the migration project.	CF to HC Self-Service Migration
Credentials for SAP BTP Cloud Foundry:
Username	User name for connecting to the SAP BTP Cloud Foundry environment.	P1234567890
Password	Password for the specified user account (P1234567890).	Welcome1
Source Database Information:
SAP BTP Region	Region of the source database within SAP BTP.	EU (Frankfurt)
Cloud Foundry Space	Cloud Foundry space name where the SAP HANA Service is located.	dev
Source Instance Name	SAP HANA Cloud Service instance name shown in the Service Instances list.	CF_Source
Username (Source DB)	Dedicated migration user account created on the source database during preparations.	MIGUSER
Password (Source DB)	Password specified during the creation of the migration user.	Welcome1
Target Database Information:
Migrated Instance Prefix	Prefix for the new migrated instance (SAP HANA Schemas and HDI containers service).	demo_
Target Instance	Name of the SAP HANA Cloud target database.	HC_CF_Target
Target DB Username	Database administrator user name created during deployment.	DBADMIN
Target Username Password	Password specified during the deployment of the target database.	Welcome1

Demo Link

Comments

You might find these interesting

Notes for Build Resilient Applications on SAP BTP with Amazon Web Services [ Week 1]

Welcome back to the next chapter in our ongoing series dedicated to unraveling the dynamic interplay between SAP Business Technology Platform (BTP) and Amazon Web Services (AWS). For those just joining us, this blog serves as an invaluable resource for individuals delving into the world of SAP BTP or seeking a comprehensive reference guide. SAP BTP, or SAP Business Technology Platform, is a comprehensive platform that brings together various essential capabilities for application development, automation, data management, analytics, planning, integration, and AI. These features are all integrated into a unified environment, making it user-friendly for both professional IT developers and citizen developers. Image Credit Key Features of SAP BTP: Application Development: SAP BTP offers a range of tools for development. For instance, SAP Build enables low-code development, while the SAP Business Application Studio caters to core developers, providing services like document management a...

8 Must-Know Questions About Object Store on SAP Business Technology Platform

What is the problem that Object Store solves ? Modern enterprise systems increasingly deal with massive volumes of unstructured data such as documents, logs, media files, and backups. Traditional relational databases are not optimized for such workloads. What is Object Store ? Object storage—commonly referred to as blob storage—addresses this gap by providing scalable, durable, and cost-efficient storage for unstructured data. Object storage is a storage architecture designed to manage unstructured data as discrete units called objects. Each object consists of: Binary data (file content) : Image , File etc Metadata (descriptive attributes) : File size, Content type, Last modified timestamp, Storage class (hot, cool, archive) Unique identifier (key or URL) : unique path-like string used to locate a blob inside a bucket Unlike file systems or relational databases, object storage does not rely on hierarchical file structures or schemas. The SAP BTP Object Store service is a managed, ...

Understanding SAP BTP Global Accounts, Directories, Subaccounts, and Entitlements

In SAP Business Technology Platform (BTP), organizing your resources effectively is crucial for efficient management and scalability. This blog provides a comprehensive overview of global accounts, directories, subaccounts, and entitlements within SAP BTP. What is a Global Account in SAP BTP? A global account in SAP BTP represents the contractual agreement you have with SAP. It serves as the top-level container for managing various resources, including directories, subaccounts, members, entitlements, and quotas. Within a global account, you receive entitlements and quotas for platform resources, which can be allocated to subaccounts for actual consumption. How Do Directories Function in SAP BTP? Directories in SAP BTP allow you to organize and manage your subaccounts based on your technical and business requirements. A directory can contain other directories and subaccounts, enabling you to create a hierarchical structure. This hierarchy can be up to 7 levels deep, with the global ac...

How to properly Start/Stop SAP system through command line ?

Starting/stopping an SAP system is not a critical task, but the method that most of us follow to achieve this is sometimes wrong. A common mistake that most of the SAP admins do is, making use of the 'startsap' and 'stopsap' commands for starting/stopping the system. These commands got deprecated in 2015 because the scripts were not being maintained anymore and SAP recommends not to use them as many people have faced errors while executing those scripts. For more info and the bugs in scripts, you can check the sap note 809477. These scripts are not available in kernel version 7.73 and later. So if these are not the correct commands, then how to start/stop the sap system? In this post, we will see how to do it in the correct way. SAP SYSTEM VS INSTANCE In SAP, an instance is a group of resources such as memory, work processes and so on, usually in support of a single application server or database server with...

KPIs for Recovery in HANA Database Administration

Introduction: In the dynamic landscape of database administration, ensuring the robustness of a system is paramount. One crucial aspect that demands meticulous attention is the recovery process following a system failure. Two key performance indicators (KPIs) stand out in this realm – Recovery Point Objective (RPO) and Recovery Time Objective (RTO) . In this technical blog, we will delve into the significance of these KPIs for HANA database administrators and explore strategies to optimize them. Recovery Point Objective (RPO): RPO is a critical metric that defines the maximum acceptable data loss in the event of a system failure . For HANA database administrators, establishing an RPO involves a careful balance between data consistency and the overhead of continuous data replication. Continuous Data Backups: To meet stringent RPO requirements, implementing continuous data backups is imperative. Utilizing HANA's native backup capabilities and integrating them with a robust backup s...

Huge Multiversion Concurrency Control (MVCC) Versions in HANA

What is MVCC? MVCC is a database concurrency control method that allows multiple transactions to occur concurrently without conflicting with each other. In a nutshell, it ensures that each transaction sees a snapshot of the database at a specific point in time, even if other transactions are making changes concurrently. MVCC in SAP HANA: SAP HANA uses MVCC to manage concurrent access to data. Each transaction in HANA sees a consistent snapshot of the data at the time the transaction began. This is achieved by maintaining multiple versions of a data row, each associated with a specific transaction or point in time. The Issue of Huge MVCC Versions: Now, the term "Huge MVCC Versions" indicates a situation where there is a significant number of these versions for a particular set of data. Here's why this might become a problem: Increased Memory Usage: Each version of a data row consumes memory. As the number of versions increases, the overall memory consumption by the databas...

Execute HANASitter for hang situation analysis

The SAP HANAsitter is configured to perform default checks once every hour to ascertain the online and primary status of SAP HANA. Upon confirmation, it initiates tracking procedures, which involve regular responsiveness assessments (typically every minute). If SAP HANA becomes unresponsive, the HANAsitter commences recording activities, potentially capturing call stacks of active threads, run-time dumps, index server gstacks, and/or kernel profiler traces, although, by default, no recording occurs. When SAP HANA is responsive, the script scrutinizes critical features, including a standard check for more than 30 active threads. If this threshold is exceeded, the script triggers recording. Upon completing the recording process, the script exits, with an option to be configured for restart using the command line. Setup Steps Overview: Begin by creating an SAP HANA user with the desired name (e.g., HANASITTER) and assign the CATALOG READ privilege to it. Establish a user key in the hdbuse...

Deploying SAP on Google Cloud : Part 1

Connect to Google Connection Method To be Used for Speed Explanation Example Uses Cloud VPN Proof of Concept Variable, up to 3 Gbps Connects on-premises network to Google Cloud securely over the internet using IPsec VPN tunnels. Creating a Cloud VPN tunnel between on-premises and Google Cloud. Encrypted IPsec tunnels Dedicated Interconnect For Enterprise level connect 10 Gbps to 100 Gbps Provides a dedicated, private connection between on-premises and Google Cloud through Google's network. Provisioning a dedicated interconnect connection. Direct physical connection between on-premises and Google Cloud network infrastructure Partner Connect If you have a data center which cannot be reached to Dedicated Google facility. Variable, up to 100 Gbps Allows connecting to Google Cloud through supported service providers. Establishing a connection with a supported service provider. Utilizes service provider's network infrastructure. Configure Tunnels with Google Cloud Platform IPsec

Building the Foundation of the PO System: Architecture and some terminologies

1. Loosely Coupled and Tightly Coupled Services : Loosely Coupled Services : These services interact with each other with minimal dependencies. Changes in one service don't significantly impact others. Pros include flexibility, easier updates, and better scalability. A common example in PO is when a shipping service communicates with an inventory service. Changes in the inventory service won't necessarily disrupt shipping. Tightly Coupled Services : These services are interdependent, so changes in one service can affect others. While they might provide faster communication, they can be less flexible and harder to maintain. For example, tightly coupling an order processing service with a payment service means any change in payment could ripple to order processing. 2. SOA - Service-Oriented Architecture : SOA is an architectural approach where everything is treated as a service, encapsulating specific functionality. Service Orchestration Example (Banking Transaction) : Consider ...

Work Process and Memory Management in SAP

Let’s talk about the entire concepts that are related to memory when we talk about SAP Application. Starting with few basic terminologies, Local Memory : Local process memory, the operating system keeps the two allocation steps transparent. The operating system does the other tasks, such as reserving physical memory, loading and unloading virtual memory into and out of the main memory. Shared Memory : If several processes are to access the same memory area, the two allocation steps are not transparent. One object is created that represents the physical memory and can be used by various processes. The processes can map the object fully or partially into the address space. The way this is done varies from platform to platform. Memory mapped files, unnamed mapped files, and shared memory are used. Extended Memory : SAP extended memory is the core of the SAP memory management system. Each SAP work process has a part reserved in its virtual address space for extended memory...

EIENTRA

Search This Blog