Making the business flow smoothly and in a fail safe mode

Minfy’s Unclouded Answers

Step 1 – Customer need

Astral Polyteknik began its IT transformation by deploying SAP. With rising and recurring costs of Opex in maintaining databases on prem, Astral decided to migrate its SAP Sybase ASE DR onto AWS cloud with system replication for production system database redundancy. The prevailing situation was the on prem HADR Setup. The primary site was on prem and a standby node was on AWS.

Step 2 - Methodology

Minfy approached the customer situation with its value added expertise and studied the SAP landscape in detail. Using years of similar
expertise, the Minfy team went about the migration journey by adhering to these four critical steps:
a. Assessment of workloads and mapping them to AWS services
b. AWS Infrastructure Architecture Design and Implementation
c. SAP ASE SRS replication for DR Setup on AWS
d. Maintaining performance efficiency similar to the current infrastructure

Step 3 - Checklist

The Minfy team ensured the:
1. SAP System and landscape on AWS was provisioned similar to the primary setup
2. System replication for SAP ASE DB was configured
3. Creation of required users and authorizations in both primary and standby Databases
4. Installation of Sybase Data Movement Agent in both primary and standby databases
5. SAP ASE System Replication was configured to fulfil the RPO SLA.

Step 4 – Execution of solution

Execution of the solution was done.
1. SAP System and landscape on AWS was provisioned similar to primary setup.
2. Preparation and Execution of HADR response files for both primary and standby databases
3. Copy DB from primary to secondary and restore.
4. Initiate Materialize command to sync the logs in Standby with Primary database
5. Monitoring HADR replication
6. Failover testing from primary to standby and fail back from standby to primary
7. DR Drill plan with the proposed and actual completion timelines.