Question

Difficulty: Very hardAssess and Select Migration Strategy (7 Rs)

An enterprise is planning to migrate its legacy portfolio management platform to AWS within a strict 6-month timeline. The platform consists of two main components:

1. Core Database: An Oracle Database running on IBM AIX (Power architecture) that utilizes proprietary stored procedures. Schema conversion and database engine migration to an open-source engine (such as Amazon Aurora) is estimated to take 18 months of code refactoring and validation.
2. Document Archiving Service: A legacy archival subsystem running on Windows Server 2008 R2. The vendor has gone out of business, the installation media and source code are lost, and the application requires direct attachment to a physical local SCSI tape library for writing backups.

Which two migration strategies should the solutions architect select for these components to meet the project constraints? (Select two.)

  1. Replatform the Core Database by migrating it to Amazon RDS for Oracle.Answer
  2. Retain the Document Archiving Service on-premises while establishing secure hybrid connectivity to the AWS cloud environment.Answer
  3. C
    Refactor the Core Database by converting the database engine to Amazon Aurora PostgreSQL using the AWS Schema Conversion Tool (SCT).
  4. D
    Rehost the Core Database by using AWS Application Migration Service (MGN) to replicate the IBM AIX physical servers directly to Amazon EC2 instances.
  5. E
    Rehost the Document Archiving Service by using AWS Application Migration Service (MGN) to replicate the Windows Server VM to Amazon EC2 and map the physical tape library over a site-to-site VPN.

Answer

The solutions architect should choose to replatform the core database by migrating to Amazon RDS for Oracle, and retain the document archiving service on-premises.
Replatforming the core database to Amazon RDS for Oracle allows the database engine to remain unchanged, meeting the 6-month migration window while resolving the platform incompatibility of IBM AIX by moving to x86-based RDS. Retaining the document archiving service on-premises is necessary because the physical SCSI tape library dependency cannot be replicated in the cloud, and the loss of installation media and source code prevents any redeployment or refactoring.

Step-by-Step Solution

1
Analyze the database requirements and constraints.
The database runs on IBM AIX, which is not natively supported on AWS. Re-architecting the database engine to an open-source alternative (Refactoring) takes 18 months, exceeding the 6-month migration limit. Replatforming to Amazon RDS for Oracle keeps the database engine but changes the underlying platform from AIX to Linux.
This determines the viable 7 Rs strategy for the database within the timeline constraint.
2
Analyze the document archiving service requirements and constraints.
The archival service relies on local physical tape libraries, and has no installation media or source code for redeployment. It cannot be replicated to the cloud due to physical hardware dependencies, which makes Rehosting or Replatforming impossible. Thus, it must be Retained on-premises.
This determines the viable 7 Rs strategy for the legacy service based on physical dependencies.

Key Concept

Selecting migration strategies (7 Rs) based on platform compatibility, physical hardware dependencies, and project timeline constraints.
Rate this question