SAP HANA Database Server Migration on GCP: From m2-megamem-416 to x4-megamem-960-metal(bare metal)

This blog post outlines key considerations and steps for migrating your SAP HANA database server from Google Cloud Platform's (GCP) m2-megamem-416 machine type to the more powerful x4-megamem-960-metal.
Requirement of Migration:
- Performance Boost: x4-megamem-960-metal offers significantly higher CPU cores and memory capacity, leading to substantial performance improvements for demanding SAP HANA workloads.
- Enhanced Scalability: The increased resources provide greater headroom for future growth and accommodate expanding data volumes and user demands.
- Cost Optimization: While initially more expensive, the x4-megamem-960-metal can potentially lead to cost savings in the long run due to improved performance and resource utilization.
- Latest Technology: Migrating to the x4-megamem-960-metal allows you to leverage the latest Intel Xeon Scalable processors and optimized hardware for SAP HANA.
- My scenario : In our case HANA Database was using 70-80% available CPU on m2-megamem-416 with AARE config and there is no next machine type available to support high cpu demand on same family
Migration Planning & Execution:
- Assessment:
- Workload Analysis: Analyze your current SAP HANA workload on m2-megamem-416 to understand resource utilization patterns Specically memory utilization and future growth of HANA Database,CPU bottleneck , performance bottlenecks, and future growth projections
- Sizing: Determine the optimal x4-megamem-960-metal instance size based on your workload analysis and future requirements. Consider factors like CPU, memory, and storage needs.(Do sizing exercise before making decision on server size)
- Backup & Recovery: Ensure you have a robust backup and recovery strategy in place before initiating the migration.
- Preparation:
- System Check: Perform thorough system checks on both the source (m2-megamem-416) and target (x4-megamem-960-metal) instances.
- Check and validate HANA Supported version,Supported Disk type ,Supported OS version.
- Perform check SAP HANA Hardware and Cloud Measurement Tools on new server and go through all the listed KPI
M2 Machine Type (m2-megamem-416😞

M2 machine type storage limits

X4 machine types (x4-megamem-960-metal)

- Software Updates: Update SAP HANA and related software components on both instances to the latest stable versions.
Migration Methods:
- SAP HANA system replication
- SAP HANA backup and recovery
- Machine type change
Comparing these methods
- Post-Migration:
- Performance Monitoring: Closely monitor the performance of SAP HANA on the x4-megamem-960-metal instance after the migration.
- Testing: Conduct thorough testing of all SAP HANA functionalities and applications to ensure proper operation.
- Fine-tuning: Fine-tune SAP HANA parameters and system configurations on the new instance to optimize performance and resource utilization.
Key Considerations:
- Licensing: Ensure you have the appropriate SAP HANA licenses for the increased resources of the x4-megamem-960-metal instance.
- Networking: Plan for network connectivity and bandwidth requirements for data transfer and ongoing operations.
- Storage: Select the appropriate storage solution for the x4-megamem-960-metal instance, considering factors like performance, capacity, and cost.
- Support: Leverage GCP support resources and SAP support for assistance throughout the migration process.
X4 Limitations :
The X4 machine series is only available as predefined machine types. Custom machine shapes are not available. The following additional restrictions apply:
- You can't attach Persistent Disk volumes to an X4 instance, only Hyperdisk volumes.
- The X4 machine series is available in only select zones and regions.
- X4 instances aren't supported with all operating system images. The operating system details page shows which operating system versions can be used with X4 instances.
- If using a custom image, when you create the image, you must enable the UEFI-compatible OS feature.
- You can't use GPUs with X4 instances.
- Shielded VM isn't supported with bare metal instances.
- Live migration is not supported with X4 instances.
- There's no hypervisor provided with X4 bare metal instances and nested virtualization isn't enabled.
- X4 machine series instances can take up to 30 mins to boot due to large hardware and the Power-On Self-Test (POST).
- The interactive serial console is not available for the X4 machine series. For more information, see Troubleshooting using the serial console.
Manage host maintenance events for X4 instances running SAP HANA :
- X4 is a specialized series of bare metal Compute Engine machine types specifically designed to handle multi-terabyte SAP HANA workloads. To ensure optimal performance, security, and reliability, X4 instances require regular software and firmware updates. These updates are delivered through planned host maintenance events.
Crucially, unlike other Compute Engine machine types, X4 instances do not support live migration during maintenance. This means that Google must temporarily stop and update your X4 instances, which can have an impact on your SAP HANA workloads
There are two ways maintenance event can be trigger
1.Maintenance event manually triggered by you

2. Maintenance event automatically triggered by Google

Reference :
SAP HANA Hardware and Cloud Measurement Tools
https://help.sap.com/docs/HANA_HW_CLOUD_TOOLS/02bb1e64c2ae4de7a11369f4e70a6394/7e878f6e16394f2990f12...
SAP Note 1943937
https://cloud.google.com/solutions/sap/docs/manage-maintenance-events-for-bare-metal-instances
- Migrate SAP HANA to a Compute Engine bare metal instance
https://cloud.google.com/solutions/sap/docs/migrate-hana-to-bare-metal-instance
- SAP HANA on Bare Metal Solution deployment guide
https://cloud.google.com/solutions/sap/docs/sap-hana-on-bms-deployment