Improved SLAs and reduced unplanned outages with AWS DMS
Since the customer had experienced long downtimes in its mission critical ERP platform (Oracle JD Edwards EnterpriseOne) impacting business operations, customer service delivery and business reputation, they realized the need to implement a disaster recovery strategy that allow them to recover from failure in the least possible time assuring business continuity.
Since the on-premises Oracle Database is the source for AWS DMS ongoing replication there was a challenge to rearchitect, deploy and configure the production Oracle Database, due to a lot of issues related to performance and licensing in the current architecture.
To achieve business operations resiliency through a well-defined disaster recovery plan for Oracle JD Edwards EnterpriseOne as their critical enterprise application system for business; IKTINUS proposed AWS DMS (Database Migration Service) that supports full load migration and change data capture (CDC), thus enabling continuous data replication from Oracle on-premise’s database to Oracle Database on AWS RDS in an asynchronous mode.
- Modern cloud Data Warehouse initiative, since the target Oracle Database instance residing in AWS RDS was asynchronously in sync with the primary database.
- Business operation resiliency and ability to resume operations fast and with zero data loss.
- Opportunity to explore the cloud benefits like agility, flexibility, and cost effectiveness.
- Business confidence in the organization’s IT team, IKTINUS and AWS like solid players for bigger business strategies where cloud fits.
- Oracle Database transaction replication from online redo logs instead of archive logs to accomplish minimum data loss with AWS Binary Reader
- AWS DMS replication tasks debugging practices
- Methodologies used for Disaster Recovery Planning
- Runbook procedures to accelerate recovery (Failover) in case of a disaster
- Runbook procedures to return (Failback) to the primary site