A company is running an SAP on Oracle system on IBM Power architecture in an on-premises data center. The company wants to migrate the SAP system to AWS. The Oracle database is 15 TB in size. The comp

Question

Options

• ABefore the migration window, build a new installation of the SAP system on AWS by using SAP
• BBefore the migration window, build a new installation of the SAP system on AWS by using SAP
• CBefore the migration window, build a new installation of the SAP system on AWS by using SAP
• DBefore the migration window, launch an appropriately sized Amazon EC2 instance on AWS to

• A
  4% (1)
• B
  8% (2)
• C
  77% (20)
• D
  12% (3)

Explanation

With a 15 TB Oracle database migrating from IBM Power (incompatible architecture for direct snapshot/restore), the fastest approach is to use a pre-migration phase with Oracle Data Guard or a similar Oracle-native replication tool to stream data to AWS before the cutover window. Option C (the correct answer) involves building the SAP system on AWS first, then using Oracle replication over the 100 Gbps Direct Connect to synchronize data continuously before the actual migration window. This way, the downtime window is only the time needed for the final incremental sync and DNS/connection switchover - not the time to transfer 15 TB cold. Options A and B likely involve full offline transfers, and Option D launching a plain EC2 instance without pre-migration replication would require full downtime to transfer all 15 TB, which is slower even on 100 Gbps.

No community discussion yet for this question.