A company has a 48 TB SAP application that runs on premises and uses an IBM Db2 database. The company needs to migrate the application to AWS. The company has strict uptime requirements for the…

Question

Options

• AUse SAP Software Provisioning Manager to create an export of the data. Move this export to AWS
• BSet up database replication from on premises to AWS. On the day of downtime, ensure that the
• CUse an AWS Snowball Edge Storage Optimized device to send an initial backup to AWS. Capture
• DUse AWS Application Migration Service (CloudEndure Migration) to migrate the database to AWS.

• A
  5% (2)
• B
  22% (8)
• C
  62% (23)
• D
  11% (4)

Explanation

The challenge is migrating 48 TB within a 24-hour downtime window using a 1 Gbps Direct Connect connection that can only be used during off-hours. Transferring 48 TB over 1 Gbps would take approximately 107 hours at theoretical maximum speed (realistically much longer), making a direct network migration impossible within the 24-hour window. Option C solves this with a two-phase approach: Phase 1 - use an AWS Snowball Edge Storage Optimized device to physically ship the initial full backup to AWS, bypassing the bandwidth bottleneck entirely (Snowball holds up to 80 TB). Phase 2 - after the Snowball data is loaded into S3, capture and apply incremental database changes over the Direct Connect link during off-hours in the days leading up to cutover. On the maintenance weekend, only the small delta since the last incremental sync needs to be transferred, making the 24-hour window achievable. Option A (Software Provisioning Manager export) is essentially the same bandwidth problem. Option B (database replication) requires continuous bandwidth and complex setup. Option D (CloudEndure/Application Migration Service) replicates at the block level continuously but still requires sufficient bandwidth for the initial sync of 48 TB.

No community discussion yet for this question.