Cloud Migration Options

By Ashwin Venugopal -

 




One-step Migration - DMO with System Move Option

Steps for DMO with System Move to Microsoft Azure:
  • Firstly, you should confirm that the connectivity to Azure is available via ExpressRoute (which is highly recommended as well as with greater speed connectivity) or Virtual Private Network (VPN) into Azure.

  • You have to provision the target infrastructure in Azure including the SAP NetWeaver and SAP HANA database servers while the Azure infrastructure can be deployed fast by simply using the predefined templates.

  • SUM is started on the on-premises source SAP application server.

  • Uptime activities can be performed from the on-premises SAP application server while the shadow repository is created.

  • In the downtime phase, export files are generated on the source system and then transferred to Azure through ExpressRoute or VPN.

  • File transfer can usually occur in "Sequential Data Transfer" or "Parallel Data Transfer" mode.

Sequential Data Transfer Mode:

  • In this mode, all the tables are exported to the file system of the on-premises server.
  • After finalizing the export, the compute SUM directory can be transferred to the target application server in Azure.
  • The SUM directory is then re-synchronized during the HOSTCHANGE phase of DMO.
  • SUM is initiated on the target Azure application server and then the import will start.
  • Post-processing is completed.

Parallel Data Transfer Mode:

  • In this mode, the data is instantly transferred to the Azure target after the export is completed for each file through the domotocloud.sh script.
  • This mode can also be used to minimize the migration downtime.  

Two-step Migration - Lift & Shift Followed by DMO

Perform the following steps for the two-step migration:
  • First of all, you have to ensure that the connectivity to Azure via ExpressRoute or VPN is available or not. 

  • After that you have to provision the infrastructure on Azure which also includes the cloned system, target SAP NetWeaver, and SAP HANA database servers, whereas the Azure infrastructure can be easily deployed with the help of predefined ARM templates.

  • The cloned system can be built with the help of homogeneous system copy or via DBMS Replication tools.

  • Now the business and technical testing can be initiated ensuring the successful move of data.

  • After that, you can perform the traditional the traditional DMO process to migrate and upgrade to SAP HANA.

  • DMO can also leveraged through memory pipe method which means that export/import can take place within the same application server and memory segment for accelerated migrations.

  • Now you have to again initiate the business and technical validation.

  • In this type of mode, you will need two downtimes as well as two testing cycles. 

DMO Optimization Option

The following areas helps in determining the potential for performance optimizations:

  1. Export 
  2. File transfer
  3. Import 

Infrastructure/hardware

It consists of the following:

  • on-premises

  1. Deploy a dedicated migration server (PAS/AAS) with extensive compute capability to execute SUM.
  2. Deploy Solid State Disks (SSD) on the source database and migration servers.
  3. (PAS/AAS)   

  • Microsoft Azure

  • ExpressRoute connectivity is recommended with the maximum bandwidth available (currently available up to 10 Gbps)
  • Leverage the domocloud.sh script (RSYNC) to move files from an on-premise source to an Azure target for the DMO System Move Option with Parallel Transfer. 

  • Implement storage snapshots for time-efficient backups during the cutover period.

  • DMO Benchmarking is generally used to capture export and import phases for a subset data and can be configured to run on specific tables.

Downtime Optimized DMO

It is a migrating option in which large tables are migrated as a part of the uptime phase and the changes will be captured by triggers that can be replayed back as part of the downtime process. 

Note- This scenarios is based on service-based project only and SAP support should be involved in the migration execution as of June 2019.

Near-Zero Downtime (NZDT)

It generally uses a clone-based technology and DMO executes on the clone while following the cloning of the production system. Transaction activities are captured from the production system and replayed back to the clone system.

Note- Cloud migrations still does not support the NZDT and Downtime Optimized DMO yet. 




Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Deployment (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 3, please click  here Microsoft Sentinel Content Hub Content in Microsoft Sentinel includes any of the following types: Data connectors offer log ingestion from different sources into Microsoft Sentinel. Parsers give log formatting/transformation into ASIM formats, supporting usage across various Microsoft Sentinel content types and scenarios. Workbooks provide monitoring, visualization, and interactively with data in Microsoft Sentinel, highlighting meaningful insights for users.  Analytics rules give alerts that point to relevant SOC actions via incidents.  Hunting Queries are used by SOC teams to proactively hunt for threats in Microsoft Sentinel. Notebooks help SOC teams in using advanced hunting features in Jupyter and Azure Notebooks. Watchlists support the ingestion of specific data for enhanced threat detection and reduced alert fatigue.  Playbooks and Azure Logic Apps Custom Connectors provide featu...
Read more