Key highlights of this release include:
- Disaster Recovery Environment Creation: Seamlessly establish a disaster recovery environment in a different region or a different availability domain within the same region.
- Switchover Capabilities: Execute a planned and orderly transition of roles between your primary and disaster recovery environments.
- Failover Functionality: In the event of a primary environment failure, you can swiftly convert the disaster recovery environment into the primary one.
- Reinstate Feature: Following a failover, this allows for the recovery of your original primary environment, reinstating it as the disaster recovery environment.
These new features empower Oracle E-Business Suite users with enhanced business continuity and resilience for their critical systems.
For a comprehensive overview of the release, visit the official Oracle blog: https://blogs.oracle.com/ebsandoraclecloud/post/major-new-ebs-cloud-manager-release-2520-now-available
The upgrade can be conveniently applied using "perl selfUpdate.pl" as described in https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T679341.htm#T681852
New "Create DR" functionality available in Cloud Manager 25.2.0
After the upgrade it is very easy to setup a DR environment in the same or a separate region. This is described in https://docs.oracle.com/cd/E26401_01/doc.122/f35809/T679330T2010880.htm#cmg_lcm_dr_create_drenv and I'll write an additional blog post on how to do it in detail soon.
Be aware
Be aware that the changes with 25.2.0 for DR introduced a critical bug: if creating of the infrastructure for a clone fails (e.g. due to capacity constraints for the shape you selected) do NOT click the cleanup button.
We learned the hard way that this currently would cleanup the source instance of the clone – so probably your production instance. Oracle is working with high priority on this and this should be fixed with 25.2.0.1.
Until then eventually considering postponing the update a little bit. You don't really want to validate your backup and restore/recovery concept for that as I did. :-/ At least I know now that it works well within the RPO and RTO targets we defined.