Migrating SAP Workloads to Azure

By Ashwin Venugopal -

 



Classic vs. SAP Database Migration Option (DMO)

Classical Migration

With the help of this option, SAP's Software Provisioning Manager (SWPM) can be exclusively used as a Software Logistics (SL) tool for database migrations and can easily exports data from a source system while importing it to a target system where the target can be anyDB. This method especially uses a file-based approach.

SAP Database Migration Option (DMO)

It allows both the SAP upgrade as well as a database migration to the SAP HANA database through one tool only. Due to this functionality, the DMO process is labelled as a one-step migration while Classical Migration is called a two-step migration.

Classical Migration vs. DMO

Parameter

Classical Migration

DMO

Purpose/Use Case

Migration only

Upgrade + Migration New DMO version available for migration-only option

Downtime Optimization Flexibility

High

Medium

Migration

Manual

Automated

Migration Expertise

OS/DB certification is mandatory

OS/DB is not mandatory, but highly recommended

Data Consistency

Manual

Automatic

Options for Data Transfer

Socket mode option, Net exchange mode option, FTP mode option to transfer data

Memory pipes Filesystem dump

Migration Check Service

It is required for classical approach on productive systems

It is not required for DMO on productive systems

Monitoring Progress

Distribution monitor and migration monitor tools available

Built-in SAPUI application for monitoring process

Post-migration Consistency Check

Process is manual and requires MIGCHECK tool and the time analyzer tool generate reports

Built-in feature in DMO

Table Splitting

Dedicated table splitting and package splitting tools available- R3TA, R3ZCHECK

It is built-in and tuned

Import & Export Table Splitting

It can be changed on the fly

It requires adjustment as part of uptime (not on the fly)

DDL Statements

Manual process to generate all DDL statements prior to migration

Built-in process for DDL statement calculations and deployment

SWPM, MIGMON, DISMON

They can be started and stopped manually. Not recommended to run from remote desktops for MIGMON tools

No such option available in DMO

No such restrictions in DMO

Export/Import

Ability to add multiple application servers to run the export/import

Only one application server can be used

R3 Load Process Limit

No limits

Limit of 999 R3 load processes

Table Splits Limit

No limit on number of table splits

Limit of 200 table splits

Target DB

anyDB (e.g. SAP HANA, SQL server, Oracle, DB2, etc.)

Only SAP HANA, AS (other databases are available on request)

SAP Recommendation

Apply for no software change

Apply if SAP can be upgraded

   






Comments

Post a Comment

Popular posts from this blog

How AMI Store & Restore Works?

By Ashwin Venugopal -
Image
  CreateStoreImageTask The CreateStoreImageTask API stores an AMI as a single object in an S3 bucket. The API initiates a task that collects all the data from the AMI and its associated snapshots, subsequently using an S3 multipart upload to store this data in an S3 object. It gathers all elements of the AMI, including most of the non-Region-specific metadata and all EBS snapshots included in the AMI, and consolidates them into a single object in S3. During the upload process, the data is compressed to minimize the space utilized in S3, which means that the S3 object could be smaller than the total sizes of the snapshots in the AMI. If the account making this API call has access to AMI and snapshot tags, they will be retained. The S3 object shares the same ID as the AMI, except it has a .bin extension. Additionally, the S3 metadata tags for the object include the AMI name, AMI description, AMI registration date, AMI owner account, and a timestamp indicating when the store operation...
Read more

Create A Store Image Task

By Ashwin Venugopal -
Image
  Introduction When you save an AMI in an S3 bucket, a task for storing the image is initiated. This store image task allows you to track the progress and result of the procedure. Securing your AMIs It is crucial to verify that the S3 bucket is set up with adequate security to protect the content of the AMI and that this security is upheld for the entire duration that the AMI objects are stored in the bucket. If this cannot be achieved, it is advisable to refrain from using these APIs. Make sure that public access to the S3 bucket is prohibited. It is suggested to activate Server-side encryption for the S3 buckets where you keep the AMIs, even though it’s not mandatory. When AMI snapshots are transferred to the S3 object, they are sent over TLS connections. It is possible to save AMIs that contain encrypted snapshots; however, the snapshots will be decrypted during the storing process. Identify the source AMI used to create a new Amazon EC2 AMI You can determine the AMI that was us...
Read more

Information Protection Scanner: Resolve Issues with Information Protection Scanner Deployment

By Ashwin Venugopal -
Image
  About If you are experiencing problems with the Microsoft Purview Information Protection scanner, check the health of your deployment by utilizing the Start-ScannerDiagnosticsPowerShell cmdlet to start the scanner diagnostic tool. The diagnostics tool checks the following details and then creates a log files with the results: Whether the database is up to date. Whether network URLs are accessible. Whether there's a valid authentication token and policy can be acquired. Whether the profile is defined in the Azure portal. Whether offline/online configuration exists and can be acquired. Whether the rules configured are valid.  The Start-ScannerDiagnostics command does not perform a comprehensive check of prerequisites. If you encounter problems with the scanner, you need to verify that your system meets the scanner's requirements, and that your scanner's configuration and installation are finished.  Verify Scanning Details Per Scanner Node and Repository Run the Get-ScanSt...
Read more