Guidance for Oracle's JD Edwards EnterpriseOne with AWS Elastic Disaster Recovery
Overview
This Guidance demonstrates how you can use AWS Elastic Disaster Recovery with Oracle's JD Edwards EnterpriseOne applications so you can quickly recover operations after unexpected events. Elastic Disaster Recovery minimizes your downtime and data loss with fast, reliable recovery of on-premises and cloud-based applications by using affordable storage, minimal compute, and point-in-time recovery. While AWS provides four core disaster recovery options in the cloud, this Guidance focuses on the setup, configuration, and optimization of disaster recovery by using the pilot light approach. This approach helps you create a lower-cost disaster recovery environment where you provision a replication server for replicating data from the source database. You provision the actual database server only when you start a disaster drill and recovery, removing the expense of maintaining a database server in the disaster recovery Region.
How it works
These technical details feature an architecture diagram to illustrate how to effectively use this solution. The architecture diagram shows the key components and their interactions, providing an overview of the architecture's structure and functionality step-by-step.
Additional considerations
Related content
Set up disaster recovery for Oracle's JD Edwards EnterpriseOne with AWS Elastic Disaster Recovery
This prescriptive guidance outlines how you can use AWS Elastic Disaster Recovery as a disaster recovery option for your JD Edwards EnterpriseOne applications.
Disclaimer
The sample code; software libraries; command line tools; proofs of concept; templates; or other related technology (including any of the foregoing that are provided by our personnel) is provided to you as AWS Content under the AWS Customer Agreement, or the relevant written agreement between you and AWS (whichever applies). You should not use this AWS Content in your production accounts, or on production or other critical data. You are responsible for testing, securing, and optimizing the AWS Content, such as sample code, as appropriate for production grade use based on your specific quality control practices and standards. Deploying AWS Content may incur AWS charges for creating or using AWS chargeable resources, such as running Amazon EC2 instances or using Amazon S3 storage.
Did you find what you were looking for today?
Let us know so we can improve the quality of the content on our pages