Autosys DR approach
Article ID: 214023
Updated On:
Products
Issue/Introduction
We ae planning to have a DR setup with single server mode in a different location. We would like to explore the options to have the setup replicated from HA in production to Single server(DR site) with minimum downtime
Autosys is not installed on DR servers. Please let us know the possible approach to achieve the requirement
Environment
Release : 11.3.6
Component : CA Workload Automation AE (AutoSys)
Resolution
The recommended solution is to install exactly the same version of the product on the DR node.
The instance code needs to be the same between your production instances and DR instances. For example if $AUTOSERV is PRD in your production environment, it needs to be set to PRD when you install AutoSys in the Disaster Recovery environment.
The AutoSys database will have to be replicated regularly from the live production to the Disaster Recovery database.
Please make sure to keep the AE Services stopped on the DR node while the Production is up.
When you run a DR Test, or in case of real need, make sure to stop AE Services on Production instances before starting AE Services on the DR.
You can use Dataguard to replicate the existing production database to your DR database for the AutoSys and WCC databases. The standalone scheduler and application server in the DR system would simply point to the DR RAC and be started when DR was invoked.
To switch to DR the production AutoSys processes will need to be shut down and processes started on the DR hardware. This can be automated. Automation of the database requirements will be driven by the DBA team. The order will be to shut down AutoSys in production, perform the necessary database actions and then start AutoSys in DR.
Feedback
