A company is running SAP on anyDB at a remote location that has slow and inconsistent internet connectivity. The company wants to migrate its system to AWS and wants to convert its database to SAP HAN

Question

Options

• AMigrate by using SAP HANA system replication over the internet connection. Specify a public IP
• BMigrate by using SAP Software Update Manager (SUM) Database Migration Option (DMO) with
• CMigrate by using SAP HANA system replication with initialization through backup and restore. Use
• DMigrate by using SAP Software Update Manager (SUM) Database Migration Option (DMO) with

• A
  4% (1)
• B
  79% (19)
• C
  4% (1)
• D
  13% (3)

Explanation

SAP Software Update Manager (SUM) with the Database Migration Option (DMO) and System Move combines an SAP upgrade, database migration (from anyDB to SAP HANA), and a physical system move to a new host in a single operation. The 'System Move' variant is specifically designed for scenarios where the source and target are in different locations and there is no persistent network link between them-the migration package is prepared on the source, exported, and can be shipped physically (e.g., via AWS Snowball) or transferred via available bandwidth in batches. Options A and C rely on SAP HANA system replication, which requires a stable, low-latency network connection between source and target-incompatible with slow/inconsistent internet and no VPC connectivity. Option D differs in the transfer mechanism and is less suited for a completely disconnected migration path.

No community discussion yet for this question.