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

In the world of business tech, SAP is making waves with a cool upgrade for handling data – shifting SAP HANA to the cloud. Meet SAP HANA Cloud, a key player in SAP's Business Technology Platform (SAP BTP). We're about to explore the perks and the how-to of this cool SAP HANA Cloud migration, thanks to a nifty self-service migration tool.

Perks of SAP HANA Cloud

1. Flexibility and Scalability Made Easy

Save money by paying only for the computing power and storage you really need.

2. Powering Up with SAP HANA Cloud Data Lake

Take advantage of a super-strong SAP HANA Cloud Data Lake for extra data prowess.

3. Always Available, Anywhere You Want

Choose your favorite cloud provider from the big names: Microsoft Azure, Amazon Web Services, Google Cloud, and Alibaba Cloud.

Self-Service Migration Tool

SAP has your back with a user-friendly self-service migration tool, making it a breeze to move your SAP HANA databases. It doesn't matter if they're hanging out on-premises or cozying up in different corners of SAP BTP.

Types of Migrations It Handles:-

(from learning.sap.com)

On-Premise to SAP HANA Cloud

Moves everything – data, catalog, table data and the secure code store inside the HDI Container is supported

Migration of XS classic and HANA repository content or other design time artifacts is not supported.

From Neo to the Cloud (SAP HANA Neo Environment to SAP HANA Cloud)

Smoothly takes your catalog and data to the cloud.

From Cloud Foundry to the Cloud (SAP HANA Service, Cloud Foundry Environment to SAP HANA Cloud)

A grand migration covering catalog, data, and your secure store.

Bonus: SAP HANA Schemas and HDI Containers Service instance with HDI Shared , schema and secure store plan are migrated as well.

This needs to be provisioned in the same region as the source database instance

Key Features of Self-Service Migration Tool

User-friendly migration wizard.
Thorough compatibility check for potential issues.
Automated migration tasks encompassing catalog, tables, data, and secure store.
SAP-managed secure temporary storage for export and import.
Accessible at no additional cost through SAP HANA Cloud Central on SAP BTP.

Phase	Activities
Plan Phase	- Strategically choose the source database.
	- Execute a compatibility check.
	- Categorize issues by severity (Critical, Error, Warning, Informational). Critical: These objects must be resolved, because you will not be able to proceed the migration without resolving them. Error: These objects will not be migrated due to feature unavailability on SAP HANA Cloud side. Recommend to review these objects carefully and to fix the reported objects at the source HANA side depending on your review result. Warning: These objects will be migrated, but may have different behavior on SAP HANA Cloud side. Recommend to review these objects and you can either ignore or fix the reported objects at the source HANA side. Info: These objects are reported for an informational purpose
	- Ensure meticulous planning based on severity information.
Prepare Phase	- Meticulously select the target SAP HANA Cloud database.
	- Define the migration user account.
	- Set the stage for a seamless migration tool operation.
Execute Phase	- Initiate the migration process.
	- Manage catalog, database data, and secure store elements.
	- Depending on the migration scenario, the SAP HANA Schemas & HDI Containers Service Instances with the HDI-Shared, Schema, and Secure Store Plan are migrated as well.

Validate Phase	- Conduct a rigorous check for consistency in migrated content.
	- Utilize metadata and data validation processes.
Finalize Phase	- Deactivate the migration user.
	- Orchestrate a comprehensive cleanup.
	- Bring the migration process to a conclusion.

(from learning.sap.com)

Reference Blogs to read :-

Migrate your SAP HANA Services for BTP (on Cloud Foundry) to SAP HANA Cloud using Self-Service Migration Tool

SAP Cloud Connector Document

Comments

You might find these interesting

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

sapstartsrv is not started or sapcontrol is not working

What is sapstartsrv ? The SAP start service runs on every computer where an instance of an SAP system is started. It is implemented as a service on Windows, and as a daemon on UNIX. The process is called sapstartsrv.exe on Windows, and sapstartsrv on UNIX platforms. The SAP start service provides the following functions for monitoring SAP systems, instances, and processes. Starting and stopping Monitoring the runtime state Reading logs, traces, and configuration files Technical information, such as network ports, active sessions, thread lists, etc. These services are provided on SAPControl SOAP Web Service, and used by SAP monitoring tools (SAP Management Console, SAP NetWeaver Administrator, etc.). For more understanding use this link : https://help.sap.com/doc/saphelp_nw73ehp1/7.31.19/enUS/b3/903925c34a45e28a2861b59c3c5623/content.htm?no_cache=true How to check if it is working or not ? In case of linux , you can simply ps -ef | grep sapstartsrv In case of windows, you need

HANA System Replication - Prerequisites & Setup

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out operation & replication modes in hana system replication. If you haven't gone though that blog, you can checkout this link In this blog we will be talking about the prerequisites of hana replication and it's setup. So let's get started. When we plan to setup hana system replication, we need to make sure that all prerequisite steps have been followed. Let's have a look at these prerequisites. HANA System Replication Prerequisites: Primary & secondary systems should be up & running HDB version of secondary should be greater than or equal to Primary database sever But, for Active/Active(read enabled config), HDB version should be same on both sites. System configuration/ini files should be identical on both sides Replication happe

ST03N : The chapter for all BASIS Admins

This blog is targeted to BASIS ADMINS Transaction for workload analysis statistical data changed over time are monitored using transaction code ST03 , now ST03N (from SAP R/3 4.6C) . With SAP Web AS 6.4 the transaction ST03 is available again. From time to time ST03 and ST03N has seen many changes but later in SAP NW7.0 ST03N has reworked in detail specially processing time is now shown in separate column. Main Use of ST03N is to get detailed information on performance of any ABAP based SAP system. Workload monitor analyzes the statistical data originally collected by kernel. You can compare or analyze the performance of a single application server or multiple application server. Using this you start checking from the entire system and finding your way to that one application server and narrowing down to exact issue. By Default :- You see data of current day as default view , you can change the default view. Source of the image : sap-perf.ca Let's discuss the WORKLOAD MONITOR By D

HANA hdbuserstore

The hdbuserstore (hana secure user store) is a tool which comes as an executable with the SAP Hana Client package. This secure user store allows you to store SAP HANA connection information, including user passwords, securely on clients. With the help of secure store, the client applications can connect to SAP HANA without the user having to enter host name or logon credentials. You can also use the secure store to configure failover support for application servers in a 3-tier scenario (for example, SAP Business Warehouse) by storing a list of all the hosts that the application server can connect to. To access the system using secure store, there are two connect options: (1)key and (2)virtualHostName. key is the hdbuserstore key that you use to connect to SAP HANA, while virtualHostName specifies the virtual host name. This option allows you to change where the hdbuserstore searches for the data and key files. Note

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. You can set

ABAP Dumps Analysis

Ever now and then have you heard about ABAP Dumps, We also have a joke everything in temporary in life except ABAP dumps for SAP Consultants. Lets try to understand ABAP dumps from perspective of a SAP BASIS Consultant. Dumps happen when an ABAP program runs and something goes wrong that cannot be handled by the program We have two broad categories of Dumps , In custom program Dumps and SAP provided program Dumps. Dumps that happen in the customer namespace ranges (i.e. own-developed code) or known as Custom Program , can usually be fixed by the ABAP programmer of your team. Dumps that happen in SAP standard code probably need a fix from SAP. You do not have to be an "ABAPer" in order to resolve ABAP dump issues. The common way to deal with them is to look up in ST22 How to correct the error ? Hints are given for the keywords that may be used to search on the note system. Gather Information about the issue Go to System > Status and Check the Basis SP level as well as info

How to resolve Common Error : Standard Template "sap_sm.xls" missing

Hey everyone, putting forward a common error we usually face when we have “ Excel inplace” functionality enabled in our SAP system. This error occurs when validity of the signature of SAP standard templates expired or were incorrectly delivered via support packages. We can reproduce the error by doing as below.. Click on “spreadsheet” icon after any SAP ALV grid view of data is on screen to make this data to export into excel directly from SAP.

SUM Tool : An Introduction

Let’s Discuss about the famous tool, that is asked in almost all the Basis and HANA interview and it is very easy to understand but a bit tricky. Tighten your seatbelts and Let’s understand in one go. SAP Technical Upgrade is a periodic project that is implemented across companies to upgrade their SAP system to the latest released version. Most of the upgrade activities are done by the technical team and the role of functional consultants is limited and mostly confined to regression testing What are the maintenance that are performed by help of SUM ? Release upgrade (major release change) System update (EHP installation) applying Support Packages (SPs) / Support Package Stacks applying Java patches correction of installed software information combine update and migration to SAP HANA (DMO: Database Migration Option) System Conversion from SAP ERP to SAP S/4HANA First thing first , never confuse in these two things : Upgrade and Update. Updating SAP products is for applying support pac

SAP application log tables: BALHDR (Application Log: Header Data) and BALDAT (Application Log: Detail Data)

BALHDR (Application Log: Header Data): Usage : The BALHDR table stores the header information for application logs. It serves as a central repository for managing and organizing log entries. Example Data Stored: The table may contain entries for various system activities, such as error messages, warnings, or information logs generated during SAP transactions or custom programs. Columns Involved: LOGNUMBER: Unique log number assigned to each log entry. OBJECT: Identifies the object associated with the log entry (e.g., a program, transaction, or process). SUBOBJECT: Further categorizes the object. USERNAME: User ID of the person who created the log entry. TIME: Date and time when the log entry was created. ADD_OBJECT: Additional information or details related to the log entry. BALDAT (Application Log: Detail Data): Usage : The BALDAT table contains the detailed data for each log entry, linked to the corresponding entry in the BALHDR table. It stores the specific log details and me

Let's Talk SAP

Search This Blog